Namespace: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
(→‎Set namespace data: Tweak description)
(lifetime)
Line 39: Line 39:


[[missionNamespace]] is the default global namespace, so just "variableName = any;" will store data to [[missionNamespace]].
[[missionNamespace]] is the default global namespace, so just "variableName = any;" will store data to [[missionNamespace]].
== Namespace lifetime ==
=== missionNamespace ===
Mission namespace is the main default partition that exists for the duration of a mission. All variables defined in mission namespace will cease to exist when mission ends. To make variables lasting longer than a mission, use different namespaces.
=== uiNamespace and parsingNamespace ===
These are 2 different namespaces, which have similar scope. Variables defined in these namespaces exist for the duration of the game .exe running and are lost when the game is shut down.
=== profileNamespace ===
This namespace will hold variables for a very long time and are attached to the user profile. Different profiles will have own set of variables stored with them. The saving of the profile namespace is forced with [[saveProfileNamespace]] command, but in Arma 3 this command is executed by vanilla game scripts already, so saving is done automatically.


[[Category: Data Types]]
[[Category: Data Types]]

Revision as of 12:06, 9 July 2020

Template:quote

Namespace - set of variables. Introduced with Arma 2.


Get namespace

These commands return the "Namespace" type:

Game Command Description
Logo A2.png1.00 missionNamespace returns the global namespace attached to the mission
Logo A2.png1.00 parsingNamespace returns the global namespace attached to the Config Parser
Logo A2.png1.00 uiNamespace returns the global namespace attached to the user interface
tkoh logo small.png1.00 profileNamespace returns the global namespace attached to the user profile
Arma 3 logo black.png1.48 currentNamespace returns the current namespace. Can be compared with isEqualTo.

You can save values in this different Namespaces without overwriting the variables with the same name.


Get namespace data

You can use the above with getVariable to get data.


Set namespace data

To set data to a namespace, there're two methods to do: namespace setVariable ["variableName",any];

with namespace do { variableName = any; };

missionNamespace is the default global namespace, so just "variableName = any;" will store data to missionNamespace.

Namespace lifetime

missionNamespace

Mission namespace is the main default partition that exists for the duration of a mission. All variables defined in mission namespace will cease to exist when mission ends. To make variables lasting longer than a mission, use different namespaces.

uiNamespace and parsingNamespace

These are 2 different namespaces, which have similar scope. Variables defined in these namespaces exist for the duration of the game .exe running and are lost when the game is shut down.

profileNamespace

This namespace will hold variables for a very long time and are attached to the user profile. Different profiles will have own set of variables stored with them. The saving of the profile namespace is forced with saveProfileNamespace command, but in Arma 3 this command is executed by vanilla game scripts already, so saving is done automatically.