From 1cadbd1b1a0dfcb944b474ed5a87ea0e673958ac Mon Sep 17 00:00:00 2001 From: spencershepard Date: Sun, 8 May 2022 09:52:46 -0700 Subject: [PATCH] Updated RotorOps: Mission Creator Guide (markdown) --- RotorOps:-Mission-Creator-Guide.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/RotorOps:-Mission-Creator-Guide.md b/RotorOps:-Mission-Creator-Guide.md index d3f6f3a..fdc5dbd 100644 --- a/RotorOps:-Mission-Creator-Guide.md +++ b/RotorOps:-Mission-Creator-Guide.md @@ -135,7 +135,8 @@ For scenario missions, this can control mission options and set or disable missi An example scenario config file shown below: -```author: GRIMM +``` +author: GRIMM version: 2 type: Scenario name: 'Persian Gulf - Nighthawks (AH-64D)' @@ -169,14 +170,14 @@ radiobuttons: farp_never, disable_radiobuttons: farp_always, farp_gunits red_forces: "RED Default Trucks & Infantry (EASY)" -blue_forces: "BLUE Default US Armor"``` +blue_forces: "BLUE Default US Armor" +``` The red_forces / blue_forces value is the filename of the desired template, without the .miz extension. You can find the names of the UI elements in this source file: https://github.com/spencershepard/RotorOps/blob/develop/Generator/MissionGeneratorUI.ui - # How the script works In a generated mission, you will find a DO SCRIPT trigger action similar to this: ```