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-03-30 14:31:53 -07:00
parent 51c3ac097f
commit f1c6bd6fcb
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
RotorOps:-Mission-Creator-Guide.md

@@ -92,6 +92,13 @@ To create a new import template:
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
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'.
- If creating a new template, moving the ANCHOR object to a key location (corner, a free space where you want a road to match, etc.) can be helpful.
- Choose a relatively flat area of the map for importing your objects, or verify the imported objects in-game afterward.
- Some templates found in the Imports folder are used for mission generation in any scenario. For example, the logistics area and the staging zone FARPs use these templates. You can change them if you wish...just understand the significance of the changes you are making. For example, you may end up changing how the FARPs fit in zones, or the functionality of the logistics zone.
- After a mission is generated, the static ANCHOR and IMPORT markers can be safely deleted, if you wish.
# Forces Templates
The friendly/enemy forces templates available in the generator are simply .miz files in the Generator/Forces folder.