missionConfigFile

Description

Return root of mission Description.ext entries hierarchy.

Important
Since the introduction of the Eden Editor, scenario attributes can be configured in the editor itself, not only in the external Description.ext file. To access desired value independently on where it is stored, use the following commands:

getMissionConfigValue

getMissionConfig

Syntax

missionConfigFile

Returns: 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");

Community notes

Killzone_Kid2015-02-17

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)

Dedmen2018-04-27

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.

To get file path with description.ext to play sound via playSound3D (before getMissionPath):

private _missionRootPath = str missionConfigFile select [0, count str missionConfigFile - 15];