allVariables: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - " {{GameCategory|arma3|New Scripting Commands}} {{GameCategory|arma3|Scripting Commands}} {{uc:{{PAGENAME}}}} " to "") |
Lou Montana (talk | contribs) m (Text replacement - "\| *((\[\[.*\]\],? ?)+) * \}\}" to "|seealso= $1 }}") |
||
| Line 28: | Line 28: | ||
| x2= <code>_allVarsTrigger = [[allVariables]] trigger1;</code> | | x2= <code>_allVarsTrigger = [[allVariables]] trigger1;</code> | ||
| [[allControls]], [[allDisplays]], [[allCurators]], [[allGroups]], [[allDead]], [[allDeadMen]] | |seealso= [[allControls]], [[allDisplays]], [[allCurators]], [[allGroups]], [[allDead]], [[allDeadMen]] | ||
}} | }} | ||
Revision as of 23:19, 16 February 2021
Description
- Description:
- Description needed
- Multiplayer:
- Using profileNamespace and uiNamespace with this command has been disabled in multiplayer. Changelog
- Groups:
- Variables
Syntax
- Syntax:
- Syntax needed
- Parameters:
- namespace: Control (Since Arma 3 v2.01), Display (Since Arma 3 v2.01) Team Member, Namespace, Object, Group, Task, Location
- Return Value:
- Return value needed
Examples
- Example 1:
_allVarsUINamespace = allVariables uiNamespace;- Example 2:
_allVarsTrigger = allVariables trigger1;
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 October 1, 2016 - 23:54 (UTC)
- longbow
- One still can use allVariables in Multiplayer against profileNamespace and uiNamespace using config parser. In Description.ext
_EXEC(somevar = allVariables profileNamespace)in code_allprofilevars = parsingNamespace getVariable "somevar"but list will be valid only at the moment of parsing config.