2D Editor: Difference between revisions
Lou Montana (talk | contribs) m (Text replacement - "Arma[ _]3[ _]Debug[ _]Console" to "Arma 3: Debug Console") |
Lou Montana (talk | contribs) m (Text replacement - "Category:Eden Editor" to "Eden Editor") |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Feature | arma3 | The 2D-Editor is now permanently replaced by [[Eden Editor]] (3D-Editor), but can still be invoked from the editor map selection screen with {{ | {{Feature|arma3|The 2D-Editor is now permanently replaced by [[:Category:Eden Editor|Eden Editor]] (3D-Editor), but can still be invoked from the editor map selection screen with {{Controls|Ctrl|O}} shortcut for legacy purposes!}} | ||
{{TOC|side}} | {{TOC|side}} | ||
{| | The '''2D Mission Editor''' is the primary tool for creating both singleplayer and multiplayer scenarios in majority of [[{{Name|bi}}]]'s [[:Category:Projects|products]]. | ||
! colspan=" | |||
The focus of this article is explaining the function and effect of each option, rather than recommending which option should be used to create a desired outcome. | |||
Many options create different effects depending on different circumstances. | |||
The sheer amount of information presented may seem daunting at first, but remember games based on [[Real Virtuality]] engine are more complex than many other games, and there is always more than one way to create the desired effect. | |||
{{Feature|informative| | |||
As the editor evolved through time, some features are marked by icons on the right, indicating games introducing the functionality. | |||
If no icon is present, it means the feature was always available. | |||
}} | |||
== Starting the Editor == | |||
Editor is accessible from the main menu through the button labelled "Mission Editor" or just "Editor". In {{arma2}} and {{tkoh}}, this button can be found in the Singleplayer subcategory. | |||
<gallery mode="packed-hover" class="center"> | |||
File:ofp_editor_menu.jpg|{{GameCategory|ofp|link= y}} | |||
File:arma_editor_menu.jpg|{{GameCategory|arma1|link= y}} | |||
File:arma2_editor_menu.jpg|{{GameCategory|arma2|link= y}} | |||
File:tkoh_editor_menu.jpg|{{GameCategory|tkoh|link= y}} | |||
File:arma3_editor_menu.jpg|{{GameCategory|arma3|link= y}} | |||
</gallery> | |||
== Controls == | |||
{| class="wikitable mw-collapsible align-center" | |||
! colspan="6" | Keyboard Shortcuts | |||
|- | |- | ||
! Function | ! Function | ||
! [[ | ! style="min-width: 6em" | [[:Category:Operation Flashpoint|{{Name|ofp|short}}]] | ||
! [[:Category:ArmA: Armed Assault|{{Name|arma1|short}}]] | ! style="min-width: 6em" | [[:Category:ArmA: Armed Assault|{{Name|arma1|short}}]] | ||
! | ! style="min-width: 6em" | {{GameCategory|arma2|link= y}} | ||
! [[Take On Helicopters| | ! style="min-width: 6em" | [[:Category:Take On Helicopters|{{Name|tkoh|short}}]] | ||
! style="min-width: 6em" | {{GameCategory|arma3|link= y}} | |||
|- | |- | ||
| [[#Units|Units]] | | [[#Units|Units]] | ||
| colspan=" | | colspan="5" | {{Controls|F1}} | ||
|- | |- | ||
| [[#Groups|Groups]] | | [[#Groups|Groups]] | ||
| colspan=" | | colspan="5" | {{Controls|F2}} | ||
|- | |- | ||
| [[#Triggers|Triggers]] | | [[#Triggers|Triggers]] | ||
| colspan=" | | colspan="5" | {{Controls|F3}} | ||
|- | |- | ||
| [[#Waypoints|Waypoints]] | | [[#Waypoints|Waypoints]] | ||
| colspan=" | | colspan="5" | {{Controls|F4}} | ||
|- | |- | ||
| [[#Synchronization|Synchronization]] | | [[#Synchronization|Synchronization]] | ||
| colspan=" | | colspan="5" | {{Controls|F5}} | ||
|- | |- | ||
| [[#Markers|Markers]] | | [[#Markers|Markers]] | ||
| colspan=" | | colspan="5" | {{Controls|F6}} | ||
|- | |- | ||
| [[#Modules|Modules]] | | [[#Modules|Modules]] | ||
| colspan="2" | | colspan="2" {{n/a}} | ||
| colspan=" | | colspan="3" | {{Controls|F7}} | ||
|- | |- | ||
| [[#New|New]] | | [[#New|New]] | ||
| colspan="2" | | | colspan="2" | | ||
| R | | {{Controls|R}} | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|N}} | ||
|- | |- | ||
| [[#Load|Load]] | | [[#Load|Load]] | ||
| colspan="3" | | | colspan="3" | | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|O}} | ||
|- | |- | ||
| [[#Save|Save]] | | [[#Save|Save]] | ||
| colspan="3" | | | colspan="3" | | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|S}} | ||
|- | |- | ||
| [[#Save As|Save As]] | | [[#Save As|Save As]] | ||
| colspan="2" | | | colspan="2" | | ||
| S | | {{Controls|S}} | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|Shift|S}} | ||
|- | |- | ||
| [[# | | [[#Merge|Merge]] | ||
| colspan="2" | | | colspan="2" | | ||
| M | | {{Controls|M}} | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|M}} | ||
|- | |- | ||
| [[#Show IDs|Show IDs]] | | [[#Show IDs|Show IDs]] | ||
| colspan="3" | | | colspan="3" | | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|I}} | ||
|- | |- | ||
| [[#Show Textures|Show Textures]] | | [[#Show Textures|Show Textures]] | ||
| colspan="2" | | | colspan="2" | | ||
| T | | {{Controls|T}} | ||
| Ctrl | | colspan="2" | {{Controls|Ctrl|T}} | ||
|- | |- | ||
| [[#Preview|Preview]] | | [[#Preview|Preview]] | ||
| colspan=" | | colspan="5" | {{Controls|Enter}} | ||
|- | |- | ||
| [[#Continue|Continue]] | | [[#Continue|Continue]] | ||
| colspan=" | | colspan="5" | | ||
|- | |- | ||
| [[#Intel|Intel]] | | [[#Intel|Intel]] | ||
| colspan=" | | colspan="5" | | ||
|- | |- | ||
| [[#Exit|Exit]] | | [[#Exit|Exit]] | ||
| colspan=" | | colspan="5" | {{Controls|Esc}} | ||
|- | |- | ||
| [[Arma 3: Debug Console|Debug Console]] | | [[Arma 3: Debug Console|Debug Console]] | ||
| colspan=" | | colspan="2" {{n/a}} | ||
| Ctrl | | | ||
| colspan="2" | {{Controls|Ctrl|D}} | |||
|- | |- | ||
| [[#Functions|Functions]] | | [[#Functions|Functions]] | ||
| colspan=" | | colspan="2" {{n/a}} | ||
| Ctrl | | | ||
| colspan="2" | {{Controls|Ctrl|F}} | |||
|- | |- | ||
| [[#Config Viewer|Config Viewer]] | | [[#Config Viewer|Config Viewer]] | ||
| colspan=" | | colspan="2" {{n/a}} | ||
| Ctrl | | | ||
| colspan="2" | {{Controls|Ctrl|G}} | |||
|} | |} | ||
== Map Controls == | == Map Controls == | ||
* '''Clicking and holding | * '''Clicking and holding {{Controls|RMB}} anywhere on the map''' allows the user to pan around the map by moving the mouse. | ||
* The '''mouse wheel''' and '''numpad +/-''' keys control the map zoom level. | * The '''mouse wheel''' and '''numpad +/-''' keys control the map zoom level. | ||
* '''LMB on an entity''' selects it. Selected entities are opaque, non selected entities are slightly transparent. | * '''{{Controls|LMB}} on an entity''' selects it. Selected entities are opaque, non selected entities are slightly transparent. | ||
* ''' | * '''{{Controls|LMB2}} on an entity''' generally opens the entity's editing menu. In Waypoint mode, double left clicking on a object will create a waypoint for the selected group that is attached to the clicked object. | ||
* ''' | * '''{{Controls|LMB2}} on empty space''' will create a new entity, if it is possible in the current editing mode. | ||
* '''Clicking and holding LMB on an entity''' allows it to be dragged around the map. It is not possible to move units in group mode or move waypoints in synchronize mode. | * '''Clicking and holding {{Controls|LMB}} on an entity''' allows it to be dragged around the map. It is not possible to move units in group mode or move waypoints in synchronize mode. | ||
* '''Clicking and holding LMB on empty space''' allows a drag box to be created for selecting multiple entities. | * '''Clicking and holding {{Controls|LMB}} on empty space''' allows a drag box to be created for selecting multiple entities. | ||
* '''Holding Ctrl''' allows the user to select more than one entity using the '''drag box''' or individually by '''left clicking on them'''. | * '''Holding {{Controls|Ctrl}}''' allows the user to select more than one entity using the '''drag box''' or individually by '''left clicking on them'''. | ||
* '''Shift | * '''{{Controls|Shift|LMB}} on an unit or waypoint''' will select all entities associated with that unit's group. | ||
* '''Shift | * '''{{Controls|Shift|LMB}} holding {{Controls|LMB}} on a selected entity''' rotates the selected entities. | ||
* '''Shift | * '''{{Controls|Shift|LMB}} on an object with a waypoint attached to it''' selects the underlaying object. | ||
* '''Shift | * '''{{Controls|Shift|LMB2}} entity with a waypoint''' on it opens the appropriate entity's menu (rather than the waypoints). | ||
* | * {{Controls|Del}} will erase the entity under the mouse cursor. | ||
* | * {{Controls|Shift|Del}} will erase all selected entities. | ||
* | * {{Controls|Ctrl|X}} will cut the selected entities to the clipboard. | ||
* | * {{Controls|Ctrl|C}} will copy the selected entities to the clipboard. | ||
* | * {{Controls|Ctrl|V}} will paste a copy of entities from the clipboard. Copy and pasted named entities automatically have a number appended to their names to avoid conflicts. | ||
* | * {{Controls|Ctrl|Shift|V}} will paste a copy of entities on their original position (useful when copying units between missions). | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_advanced.jpg| | File:OFP_editor_advanced.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor.jpg | File:ArmA_editor.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma_2_Mission_Editor.jpg | File:Arma_2_Mission_Editor.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor map.jpg| | File:tkoh editor map.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma_3_Mission_Editor.jpg | File:Arma_3_Mission_Editor.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 173: | Line 178: | ||
== Mission Modes == | == Mission Modes == | ||
This drop down list allows you to choose which component of a mission you are currently editing. A single mission stores all objects and mission parameters for the intro and outro cutscenes completely separately from the gameplay component of a mission. It is not essential to use any of these other than the mission component. While each component requires a player unit if it is to be used, the player will only have control of the unit in the ''Mission'' component. In the ''Intro'' and ''Outros'', AI will control the player's unit. The ''Intro'' and ''Outros'' will not end when the player unit dies, but must be ended using a trigger. | This drop down list allows you to choose which component of a mission you are currently editing. | ||
A single mission stores all objects and mission parameters for the intro and outro cutscenes completely separately from the gameplay component of a mission. | |||
It is not essential to use any of these other than the mission component. While each component requires a player unit if it is to be used, the player will only have control of the unit in the ''Mission'' component. | |||
In the ''Intro'' and ''Outros'', AI will control the player's unit. The ''Intro'' and ''Outros'' will not end when the player unit dies, but must be ended using a trigger. | |||
* '''Mission''' is the default. This defines the interactive component of a mission. It is the only essential part of a mission. | * '''Mission''' is the default. This defines the interactive component of a mission. It is the only essential part of a mission. | ||
* '''Intro''' plays before the briefing screen. | * '''Intro''' plays before the briefing screen. | ||
Line 190: | Line 198: | ||
''Main article: [[Mission Editor: Units]]'' | ''Main article: [[Mission Editor: Units]]'' | ||
Unit mode is used to add individual units, vehicles and objects on the map. To do so, double click on the empty space where you would like to add a unit. This will open the ''Unit Menu''. You can also open the unit menu of an existing unit while in any editing mode other than waypoints by double clicking on the unit. Note that if there is no player unit on the map, the unit menu will only allow valid player units may be placed. | Unit mode is used to add individual units, vehicles and objects on the map. To do so, double click on the empty space where you would like to add a unit. | ||
This will open the ''Unit Menu''. You can also open the unit menu of an existing unit while in any editing mode other than waypoints by double clicking on the unit. | |||
Note that if there is no player unit on the map, the unit menu will only allow valid player units may be placed. | |||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_units.jpg| | File:OFP_editor_units.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor_unit.jpg | File:ArmA_editor_unit.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma2 editor unit.jpg | File:Arma2 editor unit.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor units.jpg| | File:tkoh editor units.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma3 editor unit.jpg | File:Arma3 editor unit.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 204: | Line 214: | ||
''Main article: [[Mission Editor: Groups]]'' | ''Main article: [[Mission Editor: Groups]]'' | ||
Group editing mode can be used in several ways. The primary use is to join previously placed individual entities together into groups. Joining individual units together into groups can greatly improve their combat abilities. A group will move together, share information about enemy units and can bring greater firepower to bare on a target. Each individual unit on the map that has no visible group links is actually in a group of it is own. When a unit is created near another unit of the same side, it will automatically be placed in the other unit's group. To join a unit into an existing group, simply left click and hold on the unit, then drag a line to any unit of the group you wish to add it too. Release the button to join the unit into that group. Group links are displayed by light blue line drawn from the leader to each other unit in the group. Removing a unit from a group is done by left clicking and holding on the unit and dragging the group link line into empty space, then releasing. The highest ranking unit in a group will generally be the leader. While it is possible to create extremely large groups, huge formations of AI units create path finding issues and can be very hard to manage for a human leader. | Group editing mode can be used in several ways. The primary use is to join previously placed individual entities together into groups. | ||
Joining individual units together into groups can greatly improve their combat abilities. A group will move together, share information about enemy units and can bring greater firepower to bare on a target. | |||
Each individual unit on the map that has no visible group links is actually in a group of it is own. When a unit is created near another unit of the same side, it will automatically be placed in the other unit's group. | |||
To join a unit into an existing group, simply left click and hold on the unit, then drag a line to any unit of the group you wish to add it too. Release the button to join the unit into that group. | |||
Group links are displayed by light blue line drawn from the leader to each other unit in the group. | |||
Removing a unit from a group is done by left clicking and holding on the unit and dragging the group link line into empty space, then releasing. The highest ranking unit in a group will generally be the leader. | |||
While it is possible to create extremely large groups, huge formations of AI units create path finding issues and can be very hard to manage for a human leader. | |||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_group.jpg| | File:OFP_editor_group.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor_group.jpg | File:ArmA_editor_group.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma2 editor group.jpg | File:Arma2 editor group.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor groups.jpg| | File:tkoh editor groups.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma3 editor group.jpg | File:Arma3 editor group.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 218: | Line 234: | ||
''Main article: [[Mission Editor: Triggers]]'' | ''Main article: [[Mission Editor: Triggers]]'' | ||
A trigger is an abstract game entity that will wait until it is [[#Condition|condition]] block returns true, then carry out the ''On Activation'' string. When used effectively, they can make your mission seem much more dynamic and realistic. For example, you can use a trigger to set off a siren and call reinforcements when the player is spotted near an enemy base, or to start a convoy moving when the player gives a radio command. | A trigger is an abstract game entity that will wait until it is [[#Condition|condition]] block returns true, then carry out the ''On Activation'' string. | ||
When used effectively, they can make your mission seem much more dynamic and realistic. | |||
For example, you can use a trigger to set off a siren and call reinforcements when the player is spotted near an enemy base, or to start a convoy moving when the player gives a radio command. | |||
Triggers are represented in the mission editor by a dark blue ellipse or rectangle with a small blue flag in the centre. Triggers may be linked to an object in [[#Groups|Groups Mode (F2)]], which generally means that only that object or group can activate the trigger. Triggers can be used in various ways, for example the location and dimensions of a trigger are not always used as part of it is conditions, and triggers do not necessarily require an ''On Activation'' block, instead being used to return a [[list]] of objects that satisfy it is conditions. Each trigger's ''Condition'' block will be checked approximately twice every second for the duration of the mission. To add a new trigger to your mission, double left click in some empty map space. The ''Trigger Menu'' will open. | Triggers are represented in the mission editor by a dark blue ellipse or rectangle with a small blue flag in the centre. | ||
Triggers may be linked to an object in [[#Groups|Groups Mode (F2)]], which generally means that only that object or group can activate the trigger. | |||
Triggers can be used in various ways, for example the location and dimensions of a trigger are not always used as part of it is conditions, | |||
and triggers do not necessarily require an ''On Activation'' block, instead being used to return a [[list]] of objects that satisfy it is conditions. | |||
Each trigger's ''Condition'' block will be checked approximately twice every second for the duration of the mission. | |||
To add a new trigger to your mission, double left click in some empty map space. The ''Trigger Menu'' will open. | |||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_triggers.jpg| | File:OFP_editor_triggers.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor_trigger.jpg | File:ArmA_editor_trigger.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma2 editor trigger.jpg | File:Arma2 editor trigger.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor triggers.jpg| | File:tkoh editor triggers.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma3 editor trigger.jpg | File:Arma3 editor trigger.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 237: | Line 260: | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_waypoints.jpg| | File:OFP_editor_waypoints.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor_waypoint.jpg | File:ArmA_editor_waypoint.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma2 editor waypoint.jpg | File:Arma2 editor waypoint.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor waypoints.jpg| | File:tkoh editor waypoints.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma3 editor waypoint.jpg | File:Arma3 editor waypoint.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 259: | Line 282: | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_markers.jpg| | File:OFP_editor_markers.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor_marker.jpg | File:ArmA_editor_marker.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma2 editor marker.jpg | File:Arma2 editor marker.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor markers.jpg| | File:tkoh editor markers.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma3 editor marker.jpg | File:Arma3 editor marker.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 277: | Line 300: | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:Arma2 editor modules.jpg | File:Arma2 editor modules.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor modules.jpg| | File:tkoh editor modules.jpg|{{GameCategory|tkoh|link= y}} | ||
File:Arma3 editor modules.jpg | File:Arma3 editor modules.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 287: | Line 310: | ||
=== [[File:icon editor clear.png|30px]] New === | === [[File:icon editor clear.png|30px]] New === | ||
Remove all map entities such as units, waypoints, markers and triggers. Settings such as those defined in the Intel are retained. Be warned that there is no undo function in the mission editor. | Remove all map entities such as units, waypoints, markers and triggers. Settings such as those defined in the Intel are retained. Be warned that there is no undo function in the mission editor. | ||
=== [[File:icon editor load.png|30px]] Load === | === [[File:icon editor load.png|30px]] Load === | ||
Line 295: | Line 318: | ||
=== [[File:icon editor saveas.png|30px]] Save As === | === [[File:icon editor saveas.png|30px]] Save As === | ||
You can save your current mission with this menu. | You can save your current mission with this menu. | ||
* '''User missions''' - These missions are only available through the mission editor while using the current user profile. ''Note that if you save your mission under a new name, '''only''' the [[Mission.sqm]] file will be written in the new folder''. Saving a already named ''User mission'' also reloads any mission support files that are in the chosen mission folder, such as [[Description.ext]] and [[Init.sqs]]. | * '''User missions''' - These missions are only available through the mission editor while using the current user profile. ''Note that if you save your mission under a new name, '''only''' the [[Mission.sqm]] file will be written in the new folder''. Saving a already named ''User mission'' also reloads any mission support files that are in the chosen mission folder, such as [[Description.ext]] and [[Init.sqs]]. | ||
* '''Export to single missions/multiplayer missions''' - You can also choose to export your mission to either the single mission or multiplayer mission folders. This process creates a [[PBO File Format|pbo]] file of the current mission folder (includes all files) in "Mission" or "MPMissions" folder in game's root. | * '''Export to single missions/multiplayer missions''' - You can also choose to export your mission to either the single mission or multiplayer mission folders. This process creates a [[PBO File Format|pbo]] file of the current mission folder (includes all files) in "Mission" or "MPMissions" folder in game's root. | ||
** Note: You have to manually create the folders, otherwise mission won't be exported. | ** Note: You have to manually create the folders, otherwise mission won't be exported. | ||
Line 307: | Line 330: | ||
=== [[File:icon editor merge.png|30px]] Merge === | === [[File:icon editor merge.png|30px]] Merge === | ||
Merge will import all map data (units, groups, waypoints, triggers, etc) from one mission into the currently loaded mission. Other settings such as those set in the [[#Intel|Intel Display]] are not imported. | Merge will import all map data (units, groups, waypoints, triggers, etc) from one mission into the currently loaded mission. | ||
Other settings such as those set in the [[#Intel|Intel Display]] are not imported. | |||
=== [[File:icon editor id.png|30px]] Show IDs === | === [[File:icon editor id.png|30px]] Show IDs === | ||
Every object defined in the terrain you are using has an assigned ID number that can be used to refer to the object in script code. These IDs are normally hidden for clarity, and this button toggles them on or off. IDs are only visible at high zoom levels. | Every object defined in the terrain you are using has an assigned ID number that can be used to refer to the object in script code. | ||
These IDs are normally hidden for clarity, and this button toggles them on or off. IDs are only visible at high zoom levels. | |||
=== [[File:icon editor textures.png|30px]] Show Textures === | === [[File:icon editor textures.png|30px]] Show Textures === | ||
Clicking on this option will backfill the map with the satellite map texture rather than the default white. This gives the user an idea of the type of terrain found in an area, although the satellite map does not always correspond exactly with the ground detail textures as seen at close range. | Clicking on this option will backfill the map with the satellite map texture rather than the default white. | ||
This gives the user an idea of the type of terrain found in an area, although the satellite map does not always correspond exactly with the ground detail textures as seen at close range. | |||
=== [[File:icon editor preview.png|30px]] Preview === | === [[File:icon editor preview.png|30px]] Preview === | ||
Preview will start the mission from within the editor so that you can test the results of your labour. A player unit must be on the map for the preview button to be visible. If shift is held down while clicking on the preview button, the mission preview will include the mission briefing and debriefing. Note that in preview mode, some aspects of a mission may not always behave in the same way as they would if the mission was played as a single mission. It is wise to check your mission in "single mission mode" (outside of the mission editor) before considering release. | Preview will start the mission from within the editor so that you can test the results of your labour. A player unit must be on the map for the preview button to be visible. | ||
If shift is held down while clicking on the preview button, the mission preview will include the mission briefing and debriefing. | |||
Note that in preview mode, some aspects of a mission may not always behave in the same way as they would if the mission was played as a single mission. | |||
It is wise to check your mission in "single mission mode" (outside of the mission editor) before considering release. | |||
=== [[File:icon editor continue.png|30px]] Continue === | === [[File:icon editor continue.png|30px]] Continue === | ||
After you have exited from the preview mode, clicking 'Continue' will allow you resume the mission from the point you left it. Note that any changes made in the editor since you exited the preview will not be shown. You must click 'Preview' again to restart with the updated version of your mission. | After you have exited from the preview mode, clicking 'Continue' will allow you resume the mission from the point you left it. | ||
Note that any changes made in the editor since you exited the preview will not be shown. You must click 'Preview' again to restart with the updated version of your mission. | |||
=== Intel === | === Intel === | ||
Line 329: | Line 359: | ||
''Main article: [[Mission Editor: Intel]]'' | ''Main article: [[Mission Editor: Intel]]'' | ||
Intel display allows you to name your mission, give it a brief description, set the mission starting date and time, the current and forecast weather and which sides resistance forces are friendly to. Clicking on the Intel box will bring up the Intel menu. | Intel display allows you to name your mission, give it a brief description, set the mission starting date and time, the current and forecast weather and which sides resistance forces are friendly to. | ||
Clicking on the Intel box will bring up the Intel menu. | |||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:OFP_editor_intel.jpg| | File:OFP_editor_intel.jpg|{{GameCategory|ofp|link= y}} | ||
File:ArmA_editor_intel.jpg | File:ArmA_editor_intel.jpg|{{GameCategory|arma1|link= y}} | ||
File:Arma2 editor intel.jpg | File:Arma2 editor intel.jpg|{{GameCategory|arma2|link= y}} | ||
File:tkoh editor intel.jpg| | File:tkoh editor intel.jpg|{{GameCategory|tkoh|link= y}} | ||
File:arma 3 editor intel.jpg | File:arma 3 editor intel.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 362: | Line 393: | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:tkoh editor functions.jpg| | File:tkoh editor functions.jpg|{{GameCategory|tkoh|link= y}} | ||
File:A3_functionwViewer.png | File:A3_functionwViewer.png|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 371: | Line 402: | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:tkoh editor config.jpg| | File:tkoh editor config.jpg|{{GameCategory|tkoh|link= y}} | ||
File:arma 3 editor config.jpg | File:arma 3 editor config.jpg |{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 382: | Line 413: | ||
<gallery mode="packed-hover" class="center"> | <gallery mode="packed-hover" class="center"> | ||
File:tkoh editor debug.jpg| | File:tkoh editor debug.jpg|{{GameCategory|tkoh|link= y}} | ||
File:arma 3 editor config.jpg | File:arma 3 editor config.jpg|{{GameCategory|arma3|link= y}} | ||
</gallery> | </gallery> | ||
Line 413: | Line 444: | ||
{| | {| | ||
| {{Youtube|W2Af6e0n7fQ|{{GVI|arma2oa|1.50}} YouTube - {{arma2}} Mission Editor Tutorial 1/2|position|size}} || {{Youtube|bynzzMt7Fg4 |{{GVI|arma2oa|1.50}} YouTube - {{arma2}} Mission Editor Tutorial 2/2|position|size}} | |||
| {{Youtube|W2Af6e0n7fQ|{{GVI|arma2oa|1.50}} YouTube - | |||
|} | |} | ||
[[Category: 2D Editor]] | [[Category: 2D Editor]] |
Latest revision as of 13:27, 9 July 2023
The 2D Mission Editor is the primary tool for creating both singleplayer and multiplayer scenarios in majority of Bohemia Interactive's products.
The focus of this article is explaining the function and effect of each option, rather than recommending which option should be used to create a desired outcome. Many options create different effects depending on different circumstances. The sheer amount of information presented may seem daunting at first, but remember games based on Real Virtuality engine are more complex than many other games, and there is always more than one way to create the desired effect.
Starting the Editor
Editor is accessible from the main menu through the button labelled "Mission Editor" or just "Editor". In Arma 2 and Take On Helicopters, this button can be found in the Singleplayer subcategory.
Controls
Keyboard Shortcuts | |||||
---|---|---|---|---|---|
Function | OFP | ArmA | Arma 2 | TKOH | Arma 3 |
Units | F1 | ||||
Groups | F2 | ||||
Triggers | F3 | ||||
Waypoints | F4 | ||||
Synchronization | F5 | ||||
Markers | F6 | ||||
Modules | N/A | F7 | |||
New | R | Ctrl + N | |||
Load | Ctrl + O | ||||
Save | Ctrl + S | ||||
Save As | S | Ctrl + ⇧ Shift + S | |||
Merge | M | Ctrl + M | |||
Show IDs | Ctrl + I | ||||
Show Textures | T | Ctrl + T | |||
Preview | Enter ↵ | ||||
Continue | |||||
Intel | |||||
Exit | Esc | ||||
Debug Console | N/A | Ctrl + D | |||
Functions | N/A | Ctrl + F | |||
Config Viewer | N/A | Ctrl + G |
Map Controls
- Clicking and holding anywhere on the map allows the user to pan around the map by moving the mouse.
- The mouse wheel and numpad +/- keys control the map zoom level.
- on an entity selects it. Selected entities are opaque, non selected entities are slightly transparent.
- on an entity generally opens the entity's editing menu. In Waypoint mode, double left clicking on a object will create a waypoint for the selected group that is attached to the clicked object.
- on empty space will create a new entity, if it is possible in the current editing mode.
- Clicking and holding on an entity allows it to be dragged around the map. It is not possible to move units in group mode or move waypoints in synchronize mode.
- Clicking and holding on empty space allows a drag box to be created for selecting multiple entities.
- Holding Ctrl allows the user to select more than one entity using the drag box or individually by left clicking on them.
- ⇧ Shift + on an unit or waypoint will select all entities associated with that unit's group.
- ⇧ Shift + holding on a selected entity rotates the selected entities.
- ⇧ Shift + on an object with a waypoint attached to it selects the underlaying object.
- ⇧ Shift + entity with a waypoint on it opens the appropriate entity's menu (rather than the waypoints).
- Del will erase the entity under the mouse cursor.
- ⇧ Shift + Del will erase all selected entities.
- Ctrl + X will cut the selected entities to the clipboard.
- Ctrl + C will copy the selected entities to the clipboard.
- Ctrl + V will paste a copy of entities from the clipboard. Copy and pasted named entities automatically have a number appended to their names to avoid conflicts.
- Ctrl + ⇧ Shift + V will paste a copy of entities on their original position (useful when copying units between missions).
Status Bar
Status bar on the bottom of a screen displays current map grid and cursor's XYZ coordinates.
Mission Modes
This drop down list allows you to choose which component of a mission you are currently editing. A single mission stores all objects and mission parameters for the intro and outro cutscenes completely separately from the gameplay component of a mission. It is not essential to use any of these other than the mission component. While each component requires a player unit if it is to be used, the player will only have control of the unit in the Mission component. In the Intro and Outros, AI will control the player's unit. The Intro and Outros will not end when the player unit dies, but must be ended using a trigger.
- Mission is the default. This defines the interactive component of a mission. It is the only essential part of a mission.
- Intro plays before the briefing screen.
- Outro - Win will play after the debriefing screen in the case of a Win 1-6 trigger being activated.
- Outro - Loose will play after the debriefing screen in the case of a Lose trigger being activated.
Editing Modes
The mission editor is always in one of these seven modes. Each different mode allows the creation and manipulation of different types of map entities. The required mode can be set by either clicking on the modes name/icon or pressing the associated function key. The modes are set out in the basic order they would be used while creating a mission.
Units
Main article: Mission Editor: Units
Unit mode is used to add individual units, vehicles and objects on the map. To do so, double click on the empty space where you would like to add a unit. This will open the Unit Menu. You can also open the unit menu of an existing unit while in any editing mode other than waypoints by double clicking on the unit. Note that if there is no player unit on the map, the unit menu will only allow valid player units may be placed.
Groups
Main article: Mission Editor: Groups
Group editing mode can be used in several ways. The primary use is to join previously placed individual entities together into groups. Joining individual units together into groups can greatly improve their combat abilities. A group will move together, share information about enemy units and can bring greater firepower to bare on a target. Each individual unit on the map that has no visible group links is actually in a group of it is own. When a unit is created near another unit of the same side, it will automatically be placed in the other unit's group. To join a unit into an existing group, simply left click and hold on the unit, then drag a line to any unit of the group you wish to add it too. Release the button to join the unit into that group. Group links are displayed by light blue line drawn from the leader to each other unit in the group. Removing a unit from a group is done by left clicking and holding on the unit and dragging the group link line into empty space, then releasing. The highest ranking unit in a group will generally be the leader. While it is possible to create extremely large groups, huge formations of AI units create path finding issues and can be very hard to manage for a human leader.
Triggers
Main article: Mission Editor: Triggers
A trigger is an abstract game entity that will wait until it is condition block returns true, then carry out the On Activation string. When used effectively, they can make your mission seem much more dynamic and realistic. For example, you can use a trigger to set off a siren and call reinforcements when the player is spotted near an enemy base, or to start a convoy moving when the player gives a radio command.
Triggers are represented in the mission editor by a dark blue ellipse or rectangle with a small blue flag in the centre. Triggers may be linked to an object in Groups Mode (F2), which generally means that only that object or group can activate the trigger. Triggers can be used in various ways, for example the location and dimensions of a trigger are not always used as part of it is conditions, and triggers do not necessarily require an On Activation block, instead being used to return a list of objects that satisfy it is conditions. Each trigger's Condition block will be checked approximately twice every second for the duration of the mission. To add a new trigger to your mission, double left click in some empty map space. The Trigger Menu will open.
Waypoints
Main article: Mission Editor: Waypoints
Waypoints are used to define the route and behaviour of a group during the mission. At any point in time a group will have one active waypoint (generally the waypoint they are to move towards). Once a waypoint's conditions have been met, it will become complete and the group's next waypoint automatically becomes active. Some of a waypoint's settings will take place as the waypoint becomes active, others when the waypoint is complete.
Synchronization
Main article: Mission Editor: Synchronization
Synchronization mode is used to make different groups carry out their waypoint orders at the same time, and optionally only under specific circumstances. Synchronization can seem a hard concept to understand at first, but it is a very powerful and easy to use tool. For example, synchronization can be used to organize friendly forces to wait until everyone is in position before launching a mass attack, or wait in ambush until an enemy convoy is in the perfect location before opening fire. Synchronizing links can be made between any of a group's waypoints and any number of other group's waypoints, and any number of triggers. A synchronized waypoint will not complete until all waypoints it is linked with are ready to complete, and all synchronized triggers are activated. Synchronizing links are displayed by a dark blue line connecting the entities.
To create a synchronized link between a waypoint and another group's waypoint or a trigger, simply left click and hold on the waypoint, move the mouse to the desired waypoint/trigger then release. To remove synchronization lines from a waypoint or trigger, left click on it, hold and drag a line into empty space. Note this will remove all synchronizing lines from that entity, so be careful.
Markers
Main article: Mission Editor: Markers
Marker mode is primarily used to place visual map icons and zones on the mission map. Markers are only visible while the mission editor is in marker mode, but can still be manipulated while in other modes. To do so, hover the mouse cursor over a marker's position to display it is name. The second use of markers is to define a possible starting position for any number of objects. To do this, create a group link between the marker and the object. The object will begin the mission at any one of the markers it is grouped with or at it is original position, chosen at random. This offers another way to create some randomness in a mission, with more precise control compared to using the object's Placement radius option. Note that any marker used in this way will still be drawn on the mission map (although setting the axis sizes to 0 can be used to hide a marker). Markers can not be attached to objects. To create a map marker, double left click in empty space.
Main article: Mission Editor: Modules
Modules offers complex scripted solutions
Basic Operations
New
Remove all map entities such as units, waypoints, markers and triggers. Settings such as those defined in the Intel are retained. Be warned that there is no undo function in the mission editor.
Load
Allows you to load a previously saved mission. Only uncompressed mission folders in your current profiles missions folder can be loaded.
Save As
You can save your current mission with this menu.
- User missions - These missions are only available through the mission editor while using the current user profile. Note that if you save your mission under a new name, only the Mission.sqm file will be written in the new folder. Saving a already named User mission also reloads any mission support files that are in the chosen mission folder, such as Description.ext and Init.sqs.
- Export to single missions/multiplayer missions - You can also choose to export your mission to either the single mission or multiplayer mission folders. This process creates a pbo file of the current mission folder (includes all files) in "Mission" or "MPMissions" folder in game's root.
- Note: You have to manually create the folders, otherwise mission won't be exported.
- Send by e-mail - This option will create a pbo file of the mission folder and load your default email program using it as an attachment.
Saves a currently edited mission without opening any menu, unless mission was not saved previously.
Merge
Merge will import all map data (units, groups, waypoints, triggers, etc) from one mission into the currently loaded mission. Other settings such as those set in the Intel Display are not imported.
Show IDs
Every object defined in the terrain you are using has an assigned ID number that can be used to refer to the object in script code. These IDs are normally hidden for clarity, and this button toggles them on or off. IDs are only visible at high zoom levels.
Show Textures
Clicking on this option will backfill the map with the satellite map texture rather than the default white. This gives the user an idea of the type of terrain found in an area, although the satellite map does not always correspond exactly with the ground detail textures as seen at close range.
Preview
Preview will start the mission from within the editor so that you can test the results of your labour. A player unit must be on the map for the preview button to be visible. If shift is held down while clicking on the preview button, the mission preview will include the mission briefing and debriefing. Note that in preview mode, some aspects of a mission may not always behave in the same way as they would if the mission was played as a single mission. It is wise to check your mission in "single mission mode" (outside of the mission editor) before considering release.
Continue
After you have exited from the preview mode, clicking 'Continue' will allow you resume the mission from the point you left it. Note that any changes made in the editor since you exited the preview will not be shown. You must click 'Preview' again to restart with the updated version of your mission.
Intel
Main article: Mission Editor: Intel
Intel display allows you to name your mission, give it a brief description, set the mission starting date and time, the current and forecast weather and which sides resistance forces are friendly to. Clicking on the Intel box will bring up the Intel menu.
Easy / Advanced
The mission editor has two modes, easy and advanced. The easy mode simply hides aspects of the mission editor and takes away a lot of the control you have as a skilled designer, but could distract you when new to the editing.
Exit
Will exit the mission editor and return to the main menu. Any unsaved work will be lost. A confirmation menu is shown.
Advanced Operations
Main article: Functions
Functions Viewer show list of scripting functions, both official and community made.
Config Viewer allows to explore games' config files, including list of vehicles, weapons, displays etc.
Main article: Arma 3: Debug Console
Debug Console allows designer to watch desired values and execute custom codes.
External Editing
Main article: Mission Editor: External
Mission editor provides majority of tools required for designing a mission, but finishing touches are usually made outside of it. Briefings, custom scripts, multiplayer settings or final packing are only handled by separate files programs.
Mission Export
Main article: Mission Export
When the mission is finished, you can export it to PBO format and release it, so anybody can play it.