Mission.sqm: Difference between revisions
Jump to navigation
Jump to search
m (Redirected page to Mission Editor: External#Mission.sqm) |
Lou Montana (talk | contribs) (Page (re)creation) Tag: Removed redirect |
||
Line 1: | Line 1: | ||
{{unsupported-doc}} | |||
{{SideTOC}} | |||
[[Mission.sqm]] is the file generated by the in-game [[Mission Editor]]. | |||
== Versions == | |||
SQM version can be found by opening the file with a basic text editor: it is the very first line of the file, to format {{Inline code|version{{=}}''version'';}} - correspondence below: | |||
{| class="wikitable" | |||
! Version | |||
! Game | |||
! Format | |||
|- | |||
| 11 || | |||
* {{ofp}} | |||
* {{ofpr}} | |||
* {{arma}} | |||
* {{arma2}} | |||
* {{arma2oa}} | |||
* {{tkoh}} | |||
| rowspan="2" | 2D | |||
|- | |||
| 12 || | |||
* {{arma3}} ([[2D Editor]]) | |||
|- | |||
| 53 || | |||
* {{arma3}} ([[Eden Editor]]) | |||
| 3D | |||
|} | |||
== File Format == | |||
=== [[Eden Editor]] format === | |||
As seen above, the first line is <tt>version</tt>, then come: | |||
* <tt>class EditorData</tt> - [[Eden Editor]] settings, like camera position, entity id | |||
* <tt>binarizationWanted</tt> - 0 to output the mission in plain (non-binary) text | |||
* <tt>addons</tt> - list of required addons | |||
* <tt>AddonsMetaData</tt> - user-friendly required addons' information | |||
* <tt>randomSeed</tt> - seed for randomisation, most likely used by [[random]] | |||
* <tt>class ScenarioData</tt> - scenario's meta data (author name) as well as respawn settings (respawn type, etc) | |||
* <tt>class CustomAttributes</tt> - advanced scenario attributes (such as respawn templates, [[Arma 3 Revive|revive]], etc) | |||
* <tt>class Mission</tt> - contains the following classes: | |||
** <tt>class Intel</tt> - date/time and weather settings | |||
** <tt>class Entities</tt> - the various entities present in the <tt>Mission</tt> | |||
==== class EditorData ==== | |||
{{wip}} | |||
===== class Entities ===== | |||
====== Flags ====== | |||
* KeepHorizontal = 1 | |||
* IsGroupLeader = 2 | |||
* IsSnappedToSurface = 4 | |||
* ContainsArea = 8 | |||
=== [[2D Editor]] format === | |||
First line is <tt>version</tt>, then four classes of data, all of the same structure - they are: | |||
* class Mission | |||
* class Intro | |||
* class OutroWin | |||
* class {{sic|OutroLoose}} | |||
It is filled as such: | |||
<syntaxhighlight lang="cpp"> | |||
// addons required to run the mission | |||
// Once you are done creating/updating your mission, it is always good practice | |||
// to check the mission.sqm for presence of unwanted addons in "addOns" and "addOnsAuto"" arrays. | |||
// They contain "CfgPatches" classes of used addons. | |||
// Apart from "class Mission", list of addons is present also in "Intro", "OutroWin" and "OutroLoose" classes. | |||
addOns[]= | |||
{ | |||
"cacharacters", | |||
"desert" | |||
}; | |||
addOnsAuto[]= | |||
{ | |||
"cacharacters", | |||
"desert" | |||
}; | |||
randomSeed=9361411; // the random seed, most probably used to generate random numbers | |||
class Intel // pretty self-explanatory | |||
{ | |||
startWeather=0.100000; | |||
forecastWeather=0.300000; | |||
year=2007; | |||
month=6; | |||
day=7; | |||
hour=8; | |||
}; | |||
</syntaxhighlight> | |||
then comes the <tt>class Groups</tt>: | |||
<syntaxhighlight lang="cpp"> | |||
class Groups | |||
{ | |||
items=1; | |||
class Item0 | |||
{ | |||
side="WEST"; | |||
class Vehicles | |||
{ | |||
items=1; | |||
class Item0 | |||
{ | |||
position[]={2606.808838,14.685581,2408.266602}; // X, Z, Y | |||
id=0; | |||
side="WEST"; | |||
vehicle="SoldierWB"; | |||
player="PLAYER COMMANDER"; | |||
leader=1; // group leader | |||
skill=0.600000; | |||
}; | |||
}; | |||
}; | |||
}; | |||
</syntaxhighlight> | |||
[[Category: Operation Flashpoint: Editing]] | |||
[[Category: ArmA: Mission Editing]] | |||
[[Category: Arma 2: Editing]] | |||
[[Category: Arma 3: Editing]] | |||
[[Category: Take On Helicopters: Editing]] | |||
[[Category: Mission Editor]] |
Revision as of 18:37, 21 June 2020
Template:unsupported-doc Template:SideTOC
Mission.sqm is the file generated by the in-game Mission Editor.
Versions
SQM version can be found by opening the file with a basic text editor: it is the very first line of the file, to format version=version;
- correspondence below:
Version | Game | Format |
---|---|---|
11 |
|
2D |
12 |
| |
53 |
|
3D |
File Format
Eden Editor format
As seen above, the first line is version, then come:
- class EditorData - Eden Editor settings, like camera position, entity id
- binarizationWanted - 0 to output the mission in plain (non-binary) text
- addons - list of required addons
- AddonsMetaData - user-friendly required addons' information
- randomSeed - seed for randomisation, most likely used by random
- class ScenarioData - scenario's meta data (author name) as well as respawn settings (respawn type, etc)
- class CustomAttributes - advanced scenario attributes (such as respawn templates, revive, etc)
- class Mission - contains the following classes:
- class Intel - date/time and weather settings
- class Entities - the various entities present in the Mission
class EditorData
class Entities
Flags
- KeepHorizontal = 1
- IsGroupLeader = 2
- IsSnappedToSurface = 4
- ContainsArea = 8
2D Editor format
First line is version, then four classes of data, all of the same structure - they are:
- class Mission
- class Intro
- class OutroWin
- class OutroLoosesic
It is filled as such:
// addons required to run the mission
// Once you are done creating/updating your mission, it is always good practice
// to check the mission.sqm for presence of unwanted addons in "addOns" and "addOnsAuto"" arrays.
// They contain "CfgPatches" classes of used addons.
// Apart from "class Mission", list of addons is present also in "Intro", "OutroWin" and "OutroLoose" classes.
addOns[]=
{
"cacharacters",
"desert"
};
addOnsAuto[]=
{
"cacharacters",
"desert"
};
randomSeed=9361411; // the random seed, most probably used to generate random numbers
class Intel // pretty self-explanatory
{
startWeather=0.100000;
forecastWeather=0.300000;
year=2007;
month=6;
day=7;
hour=8;
};
then comes the class Groups:
class Groups
{
items=1;
class Item0
{
side="WEST";
class Vehicles
{
items=1;
class Item0
{
position[]={2606.808838,14.685581,2408.266602}; // X, Z, Y
id=0;
side="WEST";
vehicle="SoldierWB";
player="PLAYER COMMANDER";
leader=1; // group leader
skill=0.600000;
};
};
};
};