setVariable: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
m (Text replacement - "Category:Scripting Commands ArmA2" to "Category:Scripting Commands Arma 2")
(33 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Command|= Comments
{{Command|Comments=
____________________________________________________________________________________________
____________________________________________________________________________________________


| arma |= Game name
| arma |Game name=


|1.00|= Game version
|1.00|Game version=


|arg= local |= Arguments in MP
|arg= global|Arguments in MP=
|eff= local |Effects in MP=
____________________________________________________________________________________________
 
| 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=
____________________________________________________________________________________________
____________________________________________________________________________________________


| Set variable to given value in the variable space of given element.
| varspace [[setVariable]] [name, value] |Syntax 1=
<br>
 
To remove a variable, set it to [[nil]] (e.g. {{Inline code|[[player]] [[setVariable]] ["varname", [[nil]]<nowiki>]</nowiki>;}}).
|p1= varspace: [[Namespace]], [[Object]], [[Group]], [[Team_Member]], [[Task]], [[Location]], [[Control]], [[Display]] - variable space in which variable can be set |Parameter 1=
<br>
|p2= [name, value]: [[Array]] |Parameter 2=
<br>
|p3= name: [[String]] - variable name |Parameter 3=
All available data type combinations:
|p4= value: [[Anything]] - variable value |Parameter 4=
* [[Namespace]] setVariable [[Array]]
* [[Control]] setVariable [[Array]] (static map editor control only)
* [[Object]] setVariable [[Array]]
* [[Group]] setVariable [[Array]]
* [[Team_Member]] setVariable [[Array]]
* [[Task]] setVariable [[Array]]
* [[Location]] setVariable [[Array]]


{{Feature arma3|In Arma 3 it is possible to broadcast [[nil]] value}}|= Description
| [[Nothing]] |Return value=
____________________________________________________________________________________________


| objectName '''setVariable''' [name, value, public] |= Syntax
| s2 = varspace [[setVariable]] [name, value, public] |Syntax 2=


|p1= objectName: [[Object]] or [[Location]]. Arma 2 also supports: [[Namespace]], [[Group]], [[Control]], [[Task]] |= Parameter 1
|p21= varspace: [[missionNamespace]], [[Object]] or [[Group]] - variable space in which variable can be set |Parameter 21=
|p2= [name, value]: [[Array]] |= Parameter 2
|p22= [name, value, public]: [[Array]] |Parameter 22=
|p3= name: [[String]] |= Parameter 3
|p23= name: [[String]] - variable name |Parameter 23=
|p4= value: [[Any_Value]] |= Parameter 4
|p24= value: [[Anything]] - variable value (if public is [[true]], check [[publicVariable]] for what types are supported for broadcast) |Parameter 24=
|p5= public (optional): [[Boolean]] - Only available for [[Object]] types. If public is true then the value is broadcast to all computers. |= Parameter 5
|p25= public: [[Boolean]], [[Number]] or [[Array]] of [[Number]]s
* [[Boolean]] - when [[true]], the variable broadcast is global and persistent {{EffArg|cmd|eff|glob}}
* [[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 [[Number]]s - array of [[owner]] ([[clientOwner]]) ids |Parameter 25=


| [[Nothing]] |= Return value
|r2= [[Nothing]] |Return value 2=
____________________________________________________________________________________________
____________________________________________________________________________________________


|x1= <code>_myTruck [[setVariable]] ["myPublicVariable", 123, [[true]]<nowiki>]</nowiki>;</code> |= Example 1
|x1= <code>_myTruck [[setVariable]] ["myPublicVariable", 123, [[true]]];</code> |Example 1=


|x2= <code>_myTruck [[setVariable]] ["myLocalVariable", ["321", _var], [[false]]<nowiki>]</nowiki>;</code> |= Example 2
|x2= <code>_myTruck [[setVariable]] ["myLocalVariable", ["321", _var], [[false]]];</code> |Example 2=


|x3= <code>[[missionNamespace]] [[setVariable]] ["myName", "KK"];
|x3= <code>[[missionNamespace]] [[setVariable]] ["myName", "KK"];
[[hint]] myName; //KK</code> |= Example 3
[[hint]] myName; //KK</code> |Example 3=


|mp= The variable space of the object is '''local to each client''' and '''by default''' changes are not broadcast.
|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";
<br>
[[if]] ([[isNil]] "_var") [[then]]
Since Arma 2: '''If''' the '''public''' parameter for supported types is ''<tt>true</tt>'', the value will be '''synchronized''' also for a [[Join In Progress|JIP]] player. |= Multiplayer
{
[[missionNamespace]] [[setVariable]] ["varName", 123];
_var = 123;
};
// _var here will contain current value of the variable varName</code> |Example 4=


| [[getVariable]], [[allVariables]],  [[6thSense.eu:EG|MP editing guide]]|= See also
|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 [[Join In Progress|JIP]] player. |Multiplayer=


| [[getVariable]], [[allVariables]], [[setFSMVariable]], [[Multiplayer Scripting#Join In Progress|Multiplayer Scripting]]|See also=
}}
}}


<h3 style="display:none">Notes</h3>
<h3 style="display:none">Notes</h3>
<dl class="command_description">
<dl class="command_description">
<!-- Note Section BEGIN -->
<dd class="notedate">Posted on 18 August, 2007 - 09:51
<dt class="note">[[User:Killswitch|Killswitch]]
<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]
<dd class="notedate">Posted on 3 November, 2009 - 19:40 (CEST)
<dt class="note">[[User:WGL.Q|.kju]]
<dd class="note">Public variable parameter works also for groups in ArmA II. [http://dev-heaven.net/issues/show/5542 Ref: A2 CIT].


<dd class="notedate">Posted on January 18, 2010 - 17:27 (CEST)
<dt class="note">'''[[User:Lou Montana|Lou Montana]]'''
<dd class="note">this command doesn't work with [[createSimpleTask|tasks]] in '''Arma 2 1.05'''
<dd class="notedate">Posted on February 8, 2010 - 18:42 (CEST)
<dt class="note">'''[[User:LaKing|LaKing]]'''
<dd class="note">In '''Arma 2 1.05''' the [[missionNamespace]] object allows only the two main Arguments by syntax. Publishing the Variable afterwards works fine.
<dd class="notedate">Posted on January 25, 2011 - 02:48 (CEST)
<dt class="note">'''[[User:Lou Montana|Lou Montana]]'''
<dd class="note">this command '''does''' work with [[createSimpleTask|tasks]] in '''Arma 2 OA 1.57'''
<dd class="notedate">Posted on 19 July, 2011
<dt class="note">[[User:kju|kju]]
<dd class="note">My finds with 1.59 are:
* not working for [[Task]] (example anyone?)
* public is JIP synced for [[Object]] and [[Group]]
* public parameter is not available for [[Namespace]], [[Location]] (, [[Task]])
<dd class="notedate">Posted on 8 May, 2012
<dt class="note">[[User:Krause|Krause]]
<dd class="note">IMPORTANT: This will not work on groups if you do it from the init line (you'll experience locality issues). Do something like this instead:
Put this on init line:
<code>b_GroupSetup = [ [[group]] this, "3/B", "Tank", "Platoon"] [[execVM]] "grouptest.sqf";</code>
grouptest.sqf:
<code>[[if]] ([[isServer]]) [[then]] {
[[private]] ["_GroupSelect", "_GroupDesig", "_GroupType", "_GroupSize"];
_GroupSelect = _this [[select]] 0;
_GroupDesig = _this [[select]] 1;
_GroupType = _this [[select]] 2;
_GroupSize = _this [[select]] 3;
_GroupSelect [[setVariable]] ["groupDetails", [_GroupDesig, _GroupType, _GroupSize, 0, [], ""], [[true]] ];
};</code>
<!-- Note Section END -->
</dl>
</dl>


Line 113: Line 88:
[[Category:Command_Group:_Object_Information|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Object_Information|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Variables|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Variables|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]


<!-- CONTINUE Notes -->
<!-- CONTINUE Notes -->
<dl class="command_description">
<dl class="command_description">
<dd class="notedate">Posted on June 13, 2014 - 19:19 (UTC)</dd>
<dd class="notedate">Posted on December 9, 2015 - 20:18 (UTC)</dd>
<dt class="note">'''[[User:Astus Darkblossom|Astus Darkblossom]]'''</dt>
<dt class="note">[[User:Commy2|Commy2]]</dt>
<dd class="note">
<dd class="note">
(A3) Disable randomization and set a color to randomized vehicles by using ‘this [[setVariable]] ["color",X]’ in the init of the vehicle where X is a number ranging from 0 to the number of skins (minus 1). If the number is out of range, the skin is still randomized.
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>
</dd>
</dl>
</dl>
<!-- DISCONTINUE Notes -->
<!-- DISCONTINUE Notes -->

Revision as of 17:42, 10 January 2020

-wrong parameter ("Arma") defined!-1.00
Hover & click on the images for description

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.
All supported variable types: Template:Feature arma3
missionNamespace, uiNamespace, parsingNamespace and profileNamespace variable names could be any string, except for the reserved names, which are normally script command names. For example: missionNamespace setVariable ["west", 123]; 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 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.
Groups:
Uncategorised

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, value]: Array
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, value, public]: Array
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
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

See also:
getVariableallVariablessetFSMVariableMultiplayer Scripting

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

Notes

Bottom Section

Posted on December 9, 2015 - 20:18 (UTC)
Commy2
This command does not work with CfgAmmo or CfgNonAIVehicles objects, like bullets, mines or butterflies (probably because they are local objects Killzone Kid (talk) 11:25, 9 July 2017 (CEST)).