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-22 07:07:22 -07:00
parent 5fe57c0d74
commit c627fe7bcb
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
RotorOps:-Mission-Creator-Guide.md

@@ -33,13 +33,13 @@ A scenario .miz file MUST have:
2) At least one trigger zone with a name that starts with "STAGING".
3) A blue airport (recommend somewhere near/on-side your staging zone).
4) A red airport (recommend somewhere near/on-side your last conflict zone).
5) At least one Russian unit or static object. Anything will work, even a cow. You can set "HIDDEN ON MAP".
6) At least one USA unit or static object. See previous point.
5) At least one CJTF Red unit or static object. Anything will work, even a cow.
6) At least one CJTF Blue unit or static object. See previous point.
Optional:
7) CJTF Blue FARP called "HELO_FARP" for automatic player placement. (Strongly suggest using immortal and invisible options for support vehicles, and add "static" to the group name to keep them from moving)
7) CJTF Blue FARP called "HELO_FARP" for automatic player placement. (Strongly suggest using immortal and invisible options for support vehicles, and add "static" to the group name to keep them from moving if within the Staging zone)
8) CJTF Carrier called "HELO_CARRIER" for automatic player placement.
9) Infantry spawn zones inside conflict zones. Add near buildings to simulate infantry hiding within. Name trigger zones like "ALPHA_SPAWN", "ALPHA_SPAWN_2, etc.