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

..

Browse Source
This commit is contained in:
spencer-ki 2022-02-06 09:42:26 -08:00
parent 3299d937d4
commit c2dcb2fcbf
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Generator/Scenarios/_How to create your own scenarios.txt
View File

@ -22,6 +22,8 @@ Optional:
Tips:
-Position the center of conflict zones over an open area, as this position may be used to spawn units.
-Position the center of staging zones over an open area of at least 1000 x 1000ft to provide space for logistics units.
Position the center of staging zones over an open area of at least 1000 x 1000ft to provide space for logistics units.
-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.

3
RotorOps.lua
View File

@ -1032,8 +1032,9 @@ function RotorOps.assessUnitsInZone(var)
ctld.spawnGroupAtTrigger("blue", 5, zone, 1000)
else
ctld.spawnGroupAtTrigger("red", 5, zone, 1000)
RotorOps.gameMsg(RotorOps.gameMsgs.infantry_spawned, math.random(1, #RotorOps.gameMsgs.infantry_spawned))
end
RotorOps.gameMsg(RotorOps.gameMsgs.infantry_spawned, math.random(1, #RotorOps.gameMsgs.infantry_spawned))
RotorOps.inf_spawns_avail = RotorOps.inf_spawns_avail - 1
env.info("ROTOR OPS: Spawned infantry. "..RotorOps.inf_spawns_avail.." spawns remaining in "..zone)
end