Description
Returns Config entry for the given scenario attribute from the 1st tier. The attribute can be config class or config property. If it is defined in multiple places, the command checks them in the following order:
- External Description.ext file
- Eden Editor scenario attribute So if attribute exists in both places, attribute from description.ext is used. Previously, scenario attributes were extracted from Description.ext using missionConfigFile. That still works, but it ignores attributes set directly in the editor and it should not be used anymore.
Syntax
getMissionConfig attribute
Parameters:
attribute: String - attribute name
Returns: Config
Examples
Example 1
_header = getMissionConfig "Header";
Returns scenario header config. Replaces the previous approach which would scan only the external Description.ext file, but ignore the value set in the Eden Editor:
_header = missionConfigFile >> "Header"; // Old approach
See also
getMissionConfigValue · missionConfigFile · BIS_fnc_getParamValue · Mission Parameters