Difference between revisions of "setVariable"
Jump to navigation
Jump to search
Fred Gandt (talk | contribs) (Added example + general tidy including rewording of nonsense statement - should be checked for truth.) |
|||
| Line 110: | Line 110: | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | ||
| + | |||
| + | <!-- CONTINUE Notes --> | ||
| + | <dl class="command_description"> | ||
| + | <dd class="notedate">Posted on June 13, 2014 - 19:19 (UTC)</dd> | ||
| + | <dt class="note">'''[[User:Astus Darkblossom|Astus Darkblossom]]'''</dt> | ||
| + | <dd class="note"> | ||
| + | Arma 3 SPOTREP #00024 | ||
| + | |||
| + | Added: Possibility to 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. | ||
| + | </dd> | ||
| + | </dl> | ||
| + | <!-- DISCONTINUE Notes --> | ||
Revision as of 20:19, 13 June 2014
Notes
- Unknown
- 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: Make setVariable work on other things than just vehicles
- Posted on 3 November, 2009 - 19:40 (CEST)
- .kju
- Public variable parameter works also for groups in ArmA II. Ref: A2 CIT.
- Posted on January 18, 2010 - 17:27 (CEST)
- Lou Montana
- this command doesn't work with tasks in Arma 2 1.05
- Posted on February 8, 2010 - 18:42 (CEST)
- LaKing
- In Arma 2 1.05 the missionNamespace object allows only the two main Arguments by syntax. Publishing the Variable afterwards works fine.
- Posted on January 25, 2011 - 02:48 (CEST)
- Lou Montana
- this command does work with tasks in Arma 2 OA 1.57
- Posted on 19 July, 2011
- kju
- My finds with 1.59 are:
- Posted on 8 May, 2012
- Krause
- 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:
b_GroupSetup = [group this, "3/B", "Tank", "Platoon"]execvm "grouptest.sqf";grouptest.sqf: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]; };
Bottom Section
- Posted on June 13, 2014 - 19:19 (UTC)
- Astus Darkblossom
- Arma 3 SPOTREP #00024 Added: Possibility to 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.
