mirror of
https://github.com/spencershepard/RotorOps.git
synced 2025-11-10 15:45:30 +00:00
bdf5d95f48
-UH-60L troop capacity set to 11 -bugfix: AI enemy planes/helicopters attacked invisible FARPS -generator now produces an error log -Syria scenario FARP support units invulnerable -all red/blue coalition objects now swap sides for defense mode, including carriers and FARPs -forces templates can include air units with customization for loadout, livery, and skill -carrier and FARP parking for enemy helicopters -parking now supports multiple airports per side -improved AI flight orbits (now onside and perpendicular to closest enemy airport) -enemy transport helicopters! Random troop drops in enemy-occupied zones -'APCs spawn infantry' now disables conflict zones as infinite troop pickup zones -bug fix: add zone triggers can be added in wrong order -Combined Joint Task Forces now supported -disable pickup zone smoke option added -Scenario briefing now viewable in generator -defending vehicles disperse on attack (script option) -AWACs escorts now weapons-free and engage enemy air threats -briefing images added -new Persian Gulf scenario
42 lines
3.5 KiB
Plaintext
42 lines
3.5 KiB
Plaintext
You can add your own scenarios in this directory and they will appear in the mission generator. See the other scenario .miz files for examples of what to include in your template.
|
|
|
|
|
|
A scenario .miz file MUST have:
|
|
|
|
1) Between 1-4 circular trigger zones called "ALPHA", "BRAVO", "CHARLIE", "DELTA"
|
|
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.
|
|
|
|
|
|
|
|
Optional:
|
|
7) USA 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)
|
|
8) USA 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.
|
|
|
|
Testing:
|
|
You should test your scenarios to ensure that vehicals 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.
|
|
|
|
|
|
Tips:
|
|
-Position the center of conflict zones over an open area, as this position will be used to spawn units and FARPs.
|
|
-Position the center of staging zones over an open area of at least 1000 x 1000ft to provide space for logistics zones.
|
|
-For very scenery dense areas like forests or urban areas, smaller conflict zone sizes are highly recommended (eg 4000ft radius). A zone center near a roadway may also help keep units moving smoothly.
|
|
-The conflict game type can be played with blue forces on defense. In this mode the last conflict zone is the only troop pickup zone.
|
|
-Design your template so that it can be played in normal 'attacking' mode or 'defending' the conflict zone from enemy ground units starting from the staging zone.
|
|
-Keep the zones fairly close together, both for helicopter and ground unit travel times.
|
|
-You can place static objects and units in a scenario template.
|
|
-You can change mission briefing and other mission options in the template.
|
|
-Drop your templates in the RotorOps Discord if you'd like to have them added in a release for everyone. Maintain a similar naming convention and be sure to credit yourself in the .miz name.
|
|
-Airfields can be captured with ground units. You might consider placing conflict zones over neutral airfields for a rearming area, or perhaps unarmed client slots.
|
|
-Player/client slots are placed in this priority order: Carrier named "HELO_CARRIER", FARP named "HELO_FARP", and the blue airfield.
|
|
-Friendly AWACs and tankers will be placed at the blue airport if parking is available, otherwise they will start in the air.
|
|
-Enemy helicopters and planes will spawn at the red airport.
|
|
-Late activation FARPs might be useful for rearming far from the player spawn point.
|
|
-In "Defense" or with "Swap sides" option, USA and Russia ships, helicopters, planes, and ground units will swap countries. Static objects may not. Test it out.
|
|
-Turn off or limit civilian road traffic.
|
|
-Pay attention to rivers and bridges, as a far away bridge crossing may break routing if it's the only way across. See the testing notes above.
|