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-01-14 17:09:22 -08:00
parent 3aab3bf1e3
commit c4dcfa75e2
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
RotorOps:-Mission-Creator-Guide.md

@ -64,4 +64,11 @@ Here's an example of triggering an action with the 'defender status' flags we se
![](https://github.com/spencershepard/RotorOps/blob/develop/documentation/images/zone%20status%20trigger.PNG?raw=true)
Here, we're reading the flag for the 'ALPHA' zone and checking if it's between 0 and 90. So if the defending units in the zone are less that 90%, it will trigger our action. Here we are using it to activate a convoy that will ultimately drop more troops into the conflict zone.
Here, we're reading the flag for the 'ALPHA' zone and checking if it's between 0 and 90. So if the defending units in the zone are less that 90%, it will trigger our action. Here we are using it to activate a convoy that will ultimately drop more troops into the conflict zone.
# Options
At the beginning of the script file you will find the available dynamic and static options. The dynamic options can be changed at any time from a DO SCRIPT in the mission editor. The static options must be changed after the RotorOps.lua script has loaded, and BEFORE the startConflict() function. For example, if you want to override the default setting and turn on CTLD crates, you would type add the following line to a DO SCRIPT before startConflict()
```RotorOps.CTLD_crates = true```