missionConfigFile: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " <nowiki>[</nowiki>" to " [<nowiki/>") |
m (Text replacement - "\[\[Category\: ?Command[ _]Group\:.*\|\{\{uc\:\{\{PAGENAME\}\}\}\}\]\] " to "") |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:Scripting Commands|MISSIONCONFIGFILE]] | [[Category:Scripting Commands|MISSIONCONFIGFILE]] | ||
[[Category:Scripting Commands | [[Category:Scripting Commands Armed Assault|MISSIONCONFIGFILE]] | ||
{{Command|Comments= | {{Command|Comments= | ||
Line 9: | Line 7: | ||
| arma |Game name= | | arma |Game name= | ||
|gr1= Config |GROUP1= | |||
|1.00|Game version= | |1.00|Game version= | ||
Line 15: | Line 17: | ||
| Return root of mission [[Description.ext]] entries hierarchy. | | Return root of mission [[Description.ext]] entries hierarchy. | ||
<br><br> | <br><br> | ||
{{Important|Since 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 | {{Important|Since 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 instead: | ||
* [[getMissionConfigValue]] | * [[getMissionConfigValue]] | ||
* [[getMissionConfig]]}}<br> | * [[getMissionConfig]]}}<br> | ||
Line 66: | Line 68: | ||
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | ||
[[Category: | [[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]] | ||
<!-- CONTINUE Notes --> | <!-- CONTINUE Notes --> |
Revision as of 11:18, 25 September 2020
Description
- Description:
- Return root of mission Description.ext entries hierarchy.
Template:warning - Groups:
- Config
Syntax
- Syntax:
- missionConfigFile
- Return Value:
- 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");
- Example 3:
- To get file path with description.ext to play sound via playSound3D:
MISSION_ROOT = str missionConfigFile select [0, count str missionConfigFile - 15];
Additional Information
- See also:
- configClassesconfigPropertiesconfigFilecampaignConfigFileconfig/nameconfig >> nameconfigNamecountgetArraygetTextgetNumberinheritsFromisArrayisClassisNumberisTextselectconfigHierarchygetMissionConfigValuegetMissionPath
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
Bottom Section
- Posted on February 17, 2015 - 16:46 (UTC)
- Killzone Kid
-
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)