getMissionConfig: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\{\{GameCategory\|(arma[0123])\|New[ _]Scripting[ _]Commands[ _]List\}\}" to "{{GameCategory|$1|New Scripting Commands}}") |
Lou Montana (talk | contribs) m (Text replacement - "_{10,} " to "") |
||
| Line 1: | Line 1: | ||
{{Command|Comments= | {{Command|Comments= | ||
|arma3|Game name= | |arma3|Game name= | ||
| Line 9: | Line 8: | ||
|gr2= Mission Information |GROUP2= | |gr2= Mission Information |GROUP2= | ||
| 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: | | 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: | ||
| Line 16: | Line 14: | ||
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. | ||
|DESCRIPTION= | |DESCRIPTION= | ||
| '''getMissionConfig''' attribute |SYNTAX= | | '''getMissionConfig''' attribute |SYNTAX= | ||
| Line 26: | Line 23: | ||
<code>_header = [[missionConfigFile]] >> "Header"; // Old approach</code> | <code>_header = [[missionConfigFile]] >> "Header"; // Old approach</code> | ||
|EXAMPLE1= | |EXAMPLE1= | ||
| [[getMissionConfigValue]], [[missionConfigFile]] |SEEALSO= | | [[getMissionConfigValue]], [[missionConfigFile]] |SEEALSO= | ||
| |MPBEHAVIOUR= | | |MPBEHAVIOUR= | ||
}} | }} | ||
Revision as of 02:17, 17 January 2021
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:
- External Description.ext file
- Eden Editor scenario attribute
- 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
Notes