missionConfigFile: Difference between revisions
| Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dt></dt>" to "<dl class="command_description">  <dt></dt>") | Lou Montana (talk | contribs)  m (Text replacement - " \| *s([0-9]) *= ([^ ]+)? ?'''([a-zA-Z0-9_]+)''' ?([^ ]+)? " to " |s$1= $2 $3 $4 ") | ||
| Line 24: | Line 24: | ||
| {{Feature|Warning|If your [[Description.ext]] file is empty, [[str]] [[missionConfigFile]] may report an empty string instead of the path to the file. You have to put at least one entry into your config.}} | {{Feature|Warning|If your [[Description.ext]] file is empty, [[str]] [[missionConfigFile]] may report an empty string instead of the path to the file. You have to put at least one entry into your config.}} | ||
| |s1=  | |s1=  [[missionConfigFile]]  | ||
| |r1= [[Config]] | |r1= [[Config]] | ||
Revision as of 16:42, 12 June 2021
Description
- Description:
- Return root of mission Description.ext entries hierarchy.
- Groups:
- Config
Syntax
- Syntax:
- missionConfigFile
- Return Value:
- Config
Examples
- Example 1:
- for "_i" from 0 to (count paramsArray - 1) do { missionNamespace setVariable [configName ((missionConfigFile/"Params") select _i), paramsArray select _i]; };
- Example 2:
- To define custom values in description.ext:
class myMissionConfig { class mySetup { myNumber = 3; myArray[] = { 1, 2, 3 }; myText = "LOL"; }; }; To read defined custom values from a script: _myNumber = getNumber (missionConfigFile >> "myMissionConfig" >> "mySetup" >> "myNumber");
 _myArray = getArray (missionConfigFile >> "myMissionConfig" >> "mySetup" >> "myArray");
 _myText = getText (missionConfigFile >> "myMissionConfig" >> "mySetup" >> "myText");
- Example 3:
- To get file path with description.ext to play sound via playSound3D:
MISSION_ROOT = str missionConfigFile select [0, count str missionConfigFile - 15];
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 February 17, 2015 - 16:46 (UTC)
- Killzone Kid
- 
missionConfigFile can be used to parse mission.sqm file data as well if it is included into description.ext:
class MissionSQM { #include "mission.sqm" }; Then mission.sqm data can be accessed like this: getNumber (missionConfigFile >> "MissionSQM" >> "version"); //12 - version param in mission.sqm(courtesy of Master85)
Categories: 
- Scripting Commands
- Introduced with Armed Assault version 1.00
- ArmA: Armed Assault: New Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Config
 
	



