allVariables: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\| *((\[\[.*\]\],? ?)+) * \}\}" to "|seealso= $1 }}") |
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
||
| Line 32: | Line 32: | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<dt></dt> | |||
<dd class="notedate">Posted on October 1, 2016 - 23:54 (UTC)</dd> | <dd class="notedate">Posted on October 1, 2016 - 23:54 (UTC)</dd> | ||
<dt class="note">[[User:longbow|longbow]]</dt> | <dt class="note">[[User:longbow|longbow]]</dt> | ||
Revision as of 14:28, 5 April 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.