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-01 16:39:57 -07:00
parent 9cfb6336da
commit b36995496b
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

@@ -41,12 +41,12 @@ A scenario .miz file MUST have:
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 if within the Staging zone)
8) CJTF Carrier called "HELO_CARRIER" for automatic player placement.
7) CJTF Blue FARP called "HELO_FARP" for automatic player placement. (4 slots only. Consider using FOB import templates for more slots)
8) CJTF Carrier called "HELO_CARRIER" for automatic player placement. (4 slots only)
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.
Testing:
You should test your scenarios to ensure that vehicles move between zones as you expect. In some circumstances, vehicles may not be able to calculate a valid route to the next zone, and they will stop. Make sure they can route correctly by testing your scenario in fast forward, with few defending units. You can also get a good idea as to how long your scenario will take to complete.
You should test your scenarios to ensure that vehicles move between zones as you expect. In some circumstances, vehicles may not be able to calculate a valid route to the next zone, and they will stop. Make sure they can route correctly by testing your scenario in fast forward, with few defending units. You can also get a good idea of how long your scenario will take to complete.
Tips: