getMissionConfig: Difference between revisions
Jump to navigation
Jump to search
m (1.56) |
Killzone Kid (talk | contribs) (clarified that it also works with property not just class) |
||
| Line 7: | Line 7: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| Returns [[Config]] | | 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 commands checks them in the following order: | ||
# External ''[[Description.ext]]'' file | # External ''[[Description.ext]]'' file | ||
# [[Eden_Editor:_Scenario_Atttributes|Eden Editor]] scenario attribute | # [[Eden_Editor:_Scenario_Atttributes|Eden Editor]] scenario attribute | ||
| Line 14: | Line 14: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| '''getMissionConfig''' | | '''getMissionConfig''' attribute |= Syntax | ||
|p1= attribute: [[String]] - | |p1= attribute: [[String]] - attribute name |= PARAMETER1 | ||
| [[Config]] |= RETURNVALUE | | [[Config]] |= RETURNVALUE | ||
| Line 24: | Line 24: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| | | [[getMissionConfigValue]], [[missionConfigFile]] |= SEEALSO | ||
|= SEEALSO | |||
| |= MPBEHAVIOUR | | |= MPBEHAVIOUR | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 23:53, 12 July 2016
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 commands checks them in the following order:
- External Description.ext file
- Eden Editor scenario attribute
- Groups:
- Uncategorised
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