allVariables: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\[\[[Cc]ategory:[ _]?Arma[ _]3:[ _]([^|]*)[ _]?\|.*\]\]" to "{{GameCategory|arma3|$1}}")
m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]3(\|.*)]]" to "{{GameCategory|arma3|Scripting Commands}}")
Line 50: Line 50:
<h3 style='display:none'>Bottom Section</h3>
<h3 style='display:none'>Bottom Section</h3>
{{GameCategory|arma3|New_Scripting_Commands_List}}
{{GameCategory|arma3|New_Scripting_Commands_List}}
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
{{GameCategory|arma3|Scripting Commands}}
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]



Revision as of 15:16, 7 January 2021

Hover & click on the images for description

Description

Description:
Returns a list of all variables from desired namespace. Namespaces supported:
Multiplayer:
Using profileNamespace and uiNamespace with this command has been disabled in multiplayer. Changelog
Groups:
Variables

Syntax

Syntax:
allVariables namespace
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

Notes

Bottom Section

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.