setVariable: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "{{Inline code|" to "{{ic|") |
m (formatting) |
||
Line 1: | Line 1: | ||
{{RV|type=command | {{RV|type=command | ||
| arma1 | |game1= arma1 | ||
|1.00 | |version1= 1.00 | ||
|game2= arma2 | |||
|version2= 1.00 | |||
|game3= arma2oa | |||
|version3= 1.51 | |||
|game4= tkoh | |||
|version4= 1.00 | |||
|game5= arma3 | |||
|version5= 0.50 | |||
|arg= global | |arg= global | ||
|eff= local | |eff= local | ||
Line 12: | Line 29: | ||
|gr2= Variables | |gr2= Variables | ||
| Set variable to given value in the variable space of given element. | |descr= Set variable to given value in the variable space of given element. | ||
* To remove a variable, set it to [[nil]] (e.g. {{ic|[[player]] [[setVariable]] ["varname", [[nil]]<nowiki>]</nowiki>;}}). | * To remove a variable, set it to [[nil]] (e.g. {{ic|[[player]] [[setVariable]] ["varname", [[nil]]<nowiki>]</nowiki>;}}). | ||
* 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 [[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]]. | * When variable is set on [[Location]], it works only with locations created with [[createLocation]]. | ||
{{Feature|arma3|In Arma 3 it is possible to broadcast [[nil]] value!}} | {{Feature|arma3|In Arma 3 it is possible to broadcast [[nil]] value!}} | ||
|mp= The variable space of the object is '''local to each client''' and '''by default''' changes are not broadcast.<br> | |||
Since Arma 2: '''If''' the '''public''' parameter for supported types is ''<tt>true</tt>'', the value will be '''synchronized''' also for a [[Multiplayer Scripting#Join In Progress|JIP]] player. | |||
|pr= {{Feature | 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: | |pr= {{Feature | 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: | ||
Line 28: | Line 45: | ||
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]]}} | 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]]}} | ||
| varspace [[setVariable]] [name, value] | |s1= varspace [[setVariable]] [name, value] | ||
|p1= varspace: [[Namespace]], [[Object]], [[Group]], [[Team Member]], [[Task]], [[Location]], [[Control]], [[Display]] - Variable space in which variable can be set | |||
{{Feature|arma3|Since Arma 3 also [[Control]] and [[Display]] are supported types.}} | |||
|p2= name: [[String]] - Variable name | |||
|p3= value: [[Anything]] - Variable value | |||
|r1= [[Nothing]] | |||
| | |s2 = varspace [[setVariable]] [name, value, public] | ||
| [[ | |p21= varspace: [[missionNamespace]], [[Object]] or [[Group]] - Variable space in which variable can be set | ||
| | |p22= name: [[String]] - Variable name | ||
|p23= value: [[Anything]] - Variable value (if public is [[true]], check [[publicVariable]] for what types are supported for broadcast) | |||
|p23 | |p24= public: [[Boolean]], [[Number]] or [[Array]] of [[Number]]s | ||
* [[Boolean]] - When [[true]], the variable broadcast is global and persistent {{Icon|globalEffect|32}} | |||
| | |||
* [[Boolean]] - | * [[Number]] - The variable is set only on the client of given [[owner]] ([[clientOwner]]) id, or if id is negative, the variable is set on every client except the given one | ||
* [[Number]] - | |||
* [[Array]] of [[Number]]s - | * [[Array]] of [[Number]]s - Array of [[owner]] ([[clientOwner]]) ids | ||
|r2= [[Nothing]] | |r2= [[Nothing]] | ||
Line 55: | Line 77: | ||
|x3= <code>[[missionNamespace]] [[setVariable]] ["myName", "KK"]; | |x3= <code>[[missionNamespace]] [[setVariable]] ["myName", "KK"]; | ||
[[hint]] myName; | [[hint]] myName; {{cc|KK}}</code> | ||
|x4= Get current value of a variable and if it is undefined, define it and get the defined value:<code>[[private]] _var = [[missionNamespace]] [[getVariable]] "varName"; | |x4= Get current value of a variable and if it is undefined, define it and get the defined value:<code>[[private]] _var = [[missionNamespace]] [[getVariable]] "varName"; | ||
Line 63: | Line 85: | ||
_var = 123; | _var = 123; | ||
}; | }; | ||
{{cc|_var here will contain current value of the variable varName}}</code> | |||
| | |seealso= [[getVariable]], [[allVariables]], [[setFSMVariable]], [[Multiplayer Scripting#Join In Progress|Multiplayer Scripting]] | ||
}} | }} | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<dd class="notedate">Posted on December 9, 2015 - 20:18 (UTC)</dd> | <dd class="notedate">Posted on December 9, 2015 - 20:18 (UTC)</dd> | ||
Line 86: | Line 97: | ||
</dd> | </dd> | ||
</dl> | </dl> | ||
Revision as of 09:28, 2 April 2021
Description
- Description:
- Set variable to given value in the variable space of given element.
- To remove a variable, set it to nil (e.g.
player setVariable ["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.
- To remove a variable, set it to nil (e.g.
- 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. - Problems:
- Groups:
- MultiplayerVariables
Syntax
- Syntax:
- varspace setVariable [name, value]
- Parameters:
- varspace: Namespace, Object, Group, Team Member, Task, Location, Control, Display - Variable space in which variable can be set
- name: String - Variable name
- value: Anything - Variable value
- Return Value:
- Nothing
Alternative Syntax
- Syntax:
- varspace setVariable [name, value, public]
- Parameters:
- varspace: missionNamespace, Object or Group - Variable space in which variable can be set
- name: String - Variable name
- value: Anything - Variable value (if public is true, check publicVariable for what types are supported for broadcast)
- public: Boolean, Number or Array of Numbers
- Number - The variable is set only on the client of given owner (clientOwner) id, or if id is negative, the variable is set on every client except the given one
- Array of Numbers - Array of owner (clientOwner) ids
- Return Value:
- Nothing
Examples
- Example 1:
_myTruck setVariable ["myPublicVariable", 123, true];
- Example 2:
_myTruck setVariable ["myLocalVariable", ["321", _var], false];
- Example 3:
missionNamespace setVariable ["myName", "KK"]; hint myName; // KK
- Example 4:
- Get current value of a variable and if it is undefined, define it and get the defined value:
private _var = missionNamespace getVariable "varName"; if (isNil "_var") then { missionNamespace setVariable ["varName", 123]; _var = 123; }; // _var here will contain current value of the variable varName
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
- Posted on December 9, 2015 - 20:18 (UTC)
- Commy2
- This command does not work with CfgAmmo or CfgNonAIVehicles objects, like bullets, mines or butterflies.
Categories:
- Scripting Commands
- Introduced with Armed Assault version 1.00
- ArmA: Armed Assault: New Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Multiplayer
- Command Group: Variables
- Scripting Commands: Local Effect