From b36995496b8905ff36ac360f7ab919e71f6e5eb4 Mon Sep 17 00:00:00 2001 From: spencershepard Date: Sun, 1 May 2022 16:39:57 -0700 Subject: [PATCH] Updated RotorOps: Mission Creator Guide (markdown) --- RotorOps:-Mission-Creator-Guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/RotorOps:-Mission-Creator-Guide.md b/RotorOps:-Mission-Creator-Guide.md index 1a517dd..7ac6475 100644 --- a/RotorOps:-Mission-Creator-Guide.md +++ b/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: