| Set variable to given value in the variable space of given element.<br />

+

To remove a variable, set it to [[nil]] (e.g. {{Inline code|[[player]] [[setVariable]] ["varname", [[nil]]<nowiki>]</nowiki>;}}).<br />

+

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.<br>

+

When variable is set on [[Location]], it works only with locations created with [[createLocation]].<br>

+

All supported variable types:

+

* [[Namespace]]

+

* [[Object]]

+

* [[Group]]

+

* [[Team Member]]

+

* [[Task]] (FSM Task)

+

* [[Location]] (only [[createLocation | scripted]] locations)

+

* [[Control]] (since Arma 3 v1.55.133553)

+

* [[Display]] (since Arma 3 v1.55.133553)

−

|eff= local |= Effects in MP

+

{{Feature arma3|In Arma 3 it is possible to broadcast [[nil]] value}}

+

{{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=

<dd class="note">According to Suma, beginning with ArmA version 1.08, "setVariable now should work on any entity which can be targeted by AI, including soldier and game logic units. This includes most buildings, but not other static objects.

−

−

Using it with buildings one should be aware the building may be discarded because of streaming. In such case the variable space is lost. When used for buildings, the storage should therefore be considered non-reliable." Reference: [http://bugs.armed-assault.net/view.php?id=2444 Make setVariable work on other things than just vehicles]

This command does not work with CfgAmmo or CfgNonAIVehicles objects, like bullets, mines or butterflies (probably because they are [[local]] objects [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 11:25, 9 July 2017 (CEST)).

+

</dd>

+

</dl>

+

<!-- DISCONTINUE Notes -->

Revision as of 17:42, 10 January 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.