missionConfigFile: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<syntaxhighlight lang=cpp>" to "<syntaxhighlight lang="cpp">") |
Lou Montana (talk | contribs) m (Some wiki formatting) |
||
Line 19: | Line 19: | ||
|descr= Return root of mission [[Description.ext]] entries hierarchy. | |descr= Return root of mission [[Description.ext]] entries hierarchy. | ||
{{Feature|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 | {{Feature|important|Since the 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: | |||
* [[getMissionConfigValue]] | * [[getMissionConfigValue]] | ||
* [[getMissionConfig]] | * [[getMissionConfig]] | ||
}} | |||
|s1= | |s1= [[missionConfigFile]] | ||
|r1= [[Config]] | |r1= [[Config]] | ||
|x1= <code>[[for]] "_i" [[from]] 0 [[to]] ([[count]] [[paramsArray]] - 1) [[do]] { | |x1= <code>[[for]] "_i" [[from]] 0 [[to]] ([[count]] [[paramsArray]] - 1) [[do]] | ||
{ | |||
[[missionNamespace]] [[setVariable]] [<nowiki/>[[configName]] (([[missionConfigFile]]/"Params") [[select]] _i), [[paramsArray]] [[select]] _i]; | [[missionNamespace]] [[setVariable]] [<nowiki/>[[configName]] (([[missionConfigFile]]/"Params") [[select]] _i), [[paramsArray]] [[select]] _i]; | ||
};</code> | };</code> | ||
|x2= To define custom values in [[description.ext]]: | |x2= To define custom values in [[description.ext]]: | ||
<syntaxhighlight lang="cpp">class myMissionConfig | <syntaxhighlight lang="cpp"> | ||
class myMissionConfig | |||
{ | { | ||
class mySetup | class mySetup | ||
Line 48: | Line 51: | ||
-->_myArray = [[getArray]] ([[missionConfigFile]] [[gtgt|>>]] "myMissionConfig" [[gtgt|>>]] "mySetup" [[gtgt|>>]] "myArray");<br><!-- | -->_myArray = [[getArray]] ([[missionConfigFile]] [[gtgt|>>]] "myMissionConfig" [[gtgt|>>]] "mySetup" [[gtgt|>>]] "myArray");<br><!-- | ||
-->_myText = [[getText]] ([[missionConfigFile]] [[gtgt|>>]] "myMissionConfig" [[gtgt|>>]] "mySetup" [[gtgt|>>]] "myText");</code> | -->_myText = [[getText]] ([[missionConfigFile]] [[gtgt|>>]] "myMissionConfig" [[gtgt|>>]] "mySetup" [[gtgt|>>]] "myText");</code> | ||
|seealso=[[configFile]] [[campaignConfigFile]] [[getMissionConfigValue]] [[getMissionConfig]] [[getMissionPath]] | |seealso=[[configFile]] [[campaignConfigFile]] [[getMissionConfigValue]] [[getMissionConfig]] [[getMissionPath]] | ||
Line 70: | Line 70: | ||
<code>[[getNumber]] ([[missionConfigFile]] >> "MissionSQM" >> "version"); //12 - version param in ''mission.sqm''</code> | <code>[[getNumber]] ([[missionConfigFile]] >> "MissionSQM" >> "version"); //12 - version param in ''mission.sqm''</code> | ||
(courtesy of [[Special:Contributions/Master85|Master85]]) | (courtesy of [[Special:Contributions/Master85|Master85]]) | ||
</dd> | |||
<dt></dt> | |||
<dd class="notedate">Posted on April 27, 2018 - 20:39 (UTC)</dd> | |||
<dt class="note">[[User:Dedmen|Dedmen]]</dt> | |||
<dd class="note"> | |||
If your [[Description.ext]] file is empty, [[str]] [[missionConfigFile]] may report an empty string instead of the path to the file. You have to put at least one entry into your config.<br> | |||
To get file path with [[description.ext]] to play sound via [[playSound3D]] (before [[getMissionPath]]): | |||
<code>MISSION_ROOT = [[str]] [[missionConfigFile]] [[select]] [0, [[count]] [[str]] [[missionConfigFile]] - 15];</code> | |||
</dd> | </dd> | ||
</dl> | </dl> |
Revision as of 15:30, 19 June 2021
Description
- Description:
- Return root of mission Description.ext entries hierarchy.
- 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");
Additional Information
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
- 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) - Posted on April 27, 2018 - 20:39 (UTC)
- Dedmen
-
If your Description.ext file is empty, str missionConfigFile may report an empty string instead of the path to the file. You have to put at least one entry into your config.
To get file path with description.ext to play sound via playSound3D (before getMissionPath):MISSION_ROOT = str missionConfigFile select [0, count str missionConfigFile - 15];
Categories:
- Scripting Commands
- Introduced with Armed Assault version 1.00
- ArmA: Armed Assault: New Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Config