weyne/RotorOps
1
0
Fork 0
mirror of https://github.com/spencershepard/RotorOps.git synced 2025-11-10 15:45:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated RotorOps: Mission Creator Guide (markdown)

spencershepard
2022-05-10 11:55:08 -07:00
parent d752863771
commit 25e0bbc65a
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
RotorOps:-Mission-Creator-Guide.md

@@ -4,7 +4,7 @@ The RotorOps mission generator can load custom templates that define the base mi
A Scenario is a mission template for the generator. At its most basic, it defines the map, the conflict zones, and the friendly/enemy start points. But it doesn't have to stop there for mission designers.
A RotorOps Scenario is simply a .miz file in the Generator/Scenarios folder. If you add a .miz file here, it will show up in the generator.
A RotorOps Scenario is simply a .miz file in templates/Scenarios/user/[your_folder_name]. If you add a .miz file here, it will show up in the generator.
_**Starting in version 1.1.1, user scenarios should now go in templates/scenarios/user, and you will need to create a new folder there for each scenario template.**_
@@ -80,7 +80,7 @@ A selection of FOBs, FARPs, and other objects are available in the Imports folde
To use an import template:
1) Place a static mark flag in the scenario template mission.
2) Change the group name to 'IMPORT-filename', where the filename is a .miz file in the Generator/Imports folder.
2) Change the group name to 'IMPORT-filename', where the filename is a .miz file in templates/Imports/user/[your_folder_name]
3) Change the flag coalition to CJTF Blue/Red or UN Peacekeepers.
4) Change the flag heading and position as desired.
5) Change the flag UNIT NAME to something relevant (ie. 'North Base')
@@ -90,7 +90,7 @@ To create a new import template:
1) Make an empty mission on Caucasus.
2) Place units/objects on the map.
3) Make one unit group name: 'ANCHOR' This will represent the point of insertion/rotation in the target mission.
4) Save the template .miz file in Generator/Imports
4) Save the template .miz file in templates/Imports/user/[your_folder_name]
Tips:
- Double-check to make sure that the import UNIT names are correct. If the import static object is changed, this unit name will change to match the group name. This won't work, and when you generate the mission it will produce an error. The unit must not start with 'IMPORT'.
@@ -101,7 +101,7 @@ Tips:
# Forces Templates
The friendly/enemy forces templates available in the generator are simply .miz files in the Generator/Forces folder.
The friendly/enemy forces templates available in the generator are simply .miz files in the templates/Forces/user/[your_folder_name]
A Forces template defines the groups of ground units available, AI aircraft, liveries, and loadouts.