saveMissionProfileNamespace: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) No edit summary |
Killzone Kid (talk | contribs) No edit summary |
||
| Line 14: | Line 14: | ||
|descr= [[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 <tt><[[missionName]]>.vars</tt> 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. | |descr= [[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 <tt><[[missionName]]>.vars</tt> 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. | ||
<br><br> | <br><br> | ||
It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching | It is also possible to share the same mission profile variables between several missions. To override default behaviour one needs to create an entry <tt>missionGroup = "MyMissionCollectionName";</tt> in the [[description.ext]]. This will create <tt>MyMissionCollectionName.vars</tt> file for example, instead of default one, which would be loaded into every mission with matching <tt>missionGroup</tt> entry. | ||
|gr1= Variables | |gr1= Variables | ||
Revision as of 14:57, 18 March 2022
Description
- Description:
- 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 = "MyMissionCollectionName"; in the description.ext. This will create MyMissionCollectionName.vars file for example, instead of default one, which would be loaded into every mission with matching missionGroup entry. - Groups:
- Variables
Syntax
- Syntax:
- saveMissionProfileNamespace
- Return Value:
- Nothing
Examples
- Example 1:
- saveMissionProfileNamespace;
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note