missionConfigFile

-wrong parameter ("Arma") defined!-1.00

Hover & click on the images for description

Description

Description:

Return root of mission description.ext entries hierarchy.

Groups:

Uncategorised

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: _filePath = [(str missionConfigFile), 0, -15] call BIS_fnc_trimString;

Example 4:

Obtaining mission root using A3 substring functionality MISSION_ROOT = str missionConfigFile select [0, count str missionConfigFile - 15];

Additional Information

See also:

configClassesconfigPropertiesconfigFilecampaignConfigFileconfig/nameconfig >> nameconfigNamecountgetArraygetTextgetNumberinheritsFromisArrayisClassisNumberisTextselect

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

Bottom Section

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)