From 71e65dcb2551932471ac32bed2def6cb868fb488 Mon Sep 17 00:00:00 2001 From: spencershepard Date: Wed, 22 Jun 2022 20:36:46 -0700 Subject: [PATCH] Updated RotorOps: Mission Creator Guide (markdown) --- RotorOps:-Mission-Creator-Guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RotorOps:-Mission-Creator-Guide.md b/RotorOps:-Mission-Creator-Guide.md index 0593989..e1c8bdc 100644 --- a/RotorOps:-Mission-Creator-Guide.md +++ b/RotorOps:-Mission-Creator-Guide.md @@ -180,9 +180,9 @@ You can find the names of the UI elements in this source file: https://github.co ***Special options*** - script: text here will be inserted as a do script immediately after RotorOps.lua and CTLD.lua loads. This can be useful for changing options in these scripts. -- startTrigger: set to false to disable inserting the RotorOps.startConflict trigger action +- start_trigger: set to false to disable inserting the RotorOps.startConflict trigger action -- endTrigger: set to false to disable inserting the mission win/lose trigger actions +- end_trigger: set to false to disable inserting the mission win/lose trigger actions ***Override Imported FARP objects*** You can use alternative import templates to populate the various FARPs and bases used in mission generation. For example, if you wanted your mission template to use a FOB instead of the standard logistics zone, you could include the line: ```staging_logistics_file: FOB_16_SPWN_WIDE_LIGHTED```