add CBA_fnc_(de)serializeNamespace #609
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When merged this pull request will:
I already use this idea for the settings stuff, but this is put inside functions. The one downside of the pseudo namespaces is, that LOCATION's and OBJECT's don't survive the missions end. CBA hashes are just arrays, so they do. By "serializing" you can essentially store a copy of the pseudo namespace in the
profileNamespace
or even in the mission (usings
/get3DENMissionAttributes
) by converting them to a CBA hash first.