{{Warning | [[missionNamespace]], [[uiNamespace]], [[parsingNamespace]] and [[profileNamespace]] variable names could be any string, except for the reserved names, which are normally script command names. For example: <tt>[[missionNamespace]] setVariable ["west", 123];</tt> will result in error:

+

Error in expression <missionNamespace setVariable ["west", 123];>

+

Error position: <setVariable ["west", 123];>

+

Error Reserved variable in expression

+

as [[west]] is a script command. Other varspaces do not have such limitation. You can always check for all available script commands by running [[Arma_3_Utilities#Script_Commands | utility number 5]]}} |Description=

Revision as of 13:10, 19 March 2020

1.00

Hover & click on the images for descriptions

Description

Description:

Set variable to given value in the variable space of given element.
To remove a variable, set it to nil (e.g. playersetVariable ["varname", nil];).
When variable is set on Task, it is not actually set on task itself, but on FSM attached to the task. So if there is no FSM setVariable will not work.
When variable is set on Location, it works only with locations created with createLocation.
All supported variable types:

as west is a script command. Other varspaces do not have such limitation. You can always check for all available script commands by running utility number 5

Multiplayer:

The variable space of the object is local to each client and by default changes are not broadcast.
Since Arma 2: If the public parameter for supported types is true, the value will be synchronized also for a JIP player.