getMissionConfig: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "(\| * )+\}\}" to "}}")
m (Text replacement - " {3,}\|" to " |")
Line 13: Line 13:
# [[Eden_Editor:_Scenario_Atttributes|Eden Editor]] scenario attribute
# [[Eden_Editor:_Scenario_Atttributes|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.
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.


| '''getMissionConfig''' attribute
| '''getMissionConfig''' attribute
Line 22: Line 21:
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:
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:
<code>_header = [[missionConfigFile]] >> "Header"; // Old approach</code>
<code>_header = [[missionConfigFile]] >> "Header"; // Old approach</code>


| [[getMissionConfigValue]], [[missionConfigFile]]
| [[getMissionConfigValue]], [[missionConfigFile]]

Revision as of 18:18, 18 January 2021

Hover & click on the images for description

Description

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:
  1. External Description.ext file
  2. 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.
Groups:
ConfigMission Information

Syntax

Syntax:
getMissionConfig attribute
Parameters:
attribute: String - attribute name
Return Value:
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

Additional Information

See also:
getMissionConfigValuemissionConfigFile

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