Jump to navigation Jump to search
- missionProfileNamespace provides long term storage solution for mission variables. When this namespace has variables set with setVariable and is saved, the variables are saved into missionName.vars file into current soldier profileName folder. Next time when the same mission is loaded by the client with the same soldier profile, the saved variables can be read normally with getVariable command. This way each mission maker can create persistent data that is both mission and soldier profile specific. This is default behaviour. The file is only created when save operation is invoked with this command.
It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry missionGroup in Description.ext, for example missionGroup = "MyMissionCollectionName";. This will create MyMissionCollectionName.vars file instead of default one, which would be loaded into every mission with matching missionGroup entry.
- Example 1:
- See also:
- missionProfileNamespace isMissionProfileNamespaceLoaded saveProfileNamespace save3DENPreferences