allVariables: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - " \| *(\[\[[a-zA-Z0-9]+\]\][^ ]+) *\|x1=" to " |r1= $1 |x1=")
m (Text replacement - "<dl class="command_description"> <dt></dt>" to "<dl class="command_description"> <dt></dt>")
Line 32: Line 32:


<dl class="command_description">
<dl class="command_description">
<dt></dt>
<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>

Revision as of 14:25, 12 June 2021

Hover & click on the images for description

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:
Array of Strings - array of variable names. All names are in lower case (see toLower)

Examples

Example 1:
_allVarsUINamespace = allVariables uiNamespace;
Example 2:
_allVarsTrigger = allVariables trigger1;

Additional Information

See also:
allControlsallDisplaysallCuratorsallGroupsallDeadallDeadMen

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.