DCS Trigger Flags Reference

Comprehensive reference of all DCS trigger flags used by standalone scripts and mission files (.miz) in this repository.

Standalone Script Flags

Flags used by the Lua scripts maintained in this repository.

⚠️ RTB Script Flag Consistency

The standalone RTB/Kills_RTB_points.lua uses flags 21 (Axis) and 11 (Allies), but the embedded copies inside the .miz files use different numbers depending on the mission:

All missions have a working, embedded copy of the RTB script. The standalone RTB/Kills_RTB_points.lua should not be blindly copied into missions using 55/65 — they will fail to find the expected trigger flags.

Flag Initialization

The RTB script reads the current flag value via trigger.misc.getUserFlag() and adds bonus points to it. The flag is not initialized to any baseline value by the mission triggers in most cases; DCS returns 0 for an uninitialized flag, which is usually the correct starting point for a fresh mission. If a mission designer starts the flag at a non-zero value, ensure the corresponding a_set_flag_value trigger is present before the RTB evaluation fires.

RTB Script Per-Mission Analysis

• Initialized? = whether the mission contains explicit a_set_flag or a_set_flag_value trigger actions for that flag before RTB evaluation. DCS defaults to 0 regardless.
• Inc Ops = number of trigger actions that increment the flag during the mission.

Standalone Script Details

4YA_HQ.lua (v2.0)

Reads trigger.misc.getUserFlag("Mission") at line 68. No flags are written by this script.

Kills_RTB_points.lua (v1.2)

Configurable tunables at top of file:

local Countingtime     = 16030   -- mission duration - 170 seconds
local AxisPointsFlag   = 21      -- DCS trigger flag for Axis total points
local AlliesPointsFlag = 11      -- DCS trigger flag for Allied total points

Mission File (.miz) Flags

Flags extracted from trigger definitions and embedded scripts inside each .miz file.

Embedded Scripts per Mission: - All missions embed ZoneAttackAlert and Kills_RTB scripts. - EWRS and 4YA_HQ are loaded externally; they are not embedded in the .miz files analyzed here. - Some missions use different Kills_RTB variants with different point flag assignments.

01. 3 June 1944 (v5.9.1)

02. 10 June 1944 — Normandy 1 (v5.8.2)

02. 10 June 1944 — Normandy 1 (v5.9.1)

Same flags as the v5.8.2 variant above ( Normandy 1 theatre ).

03. 18 June 1944 — Normandy 2 (v5.9.1)

04. 24 June 1944 — Normandy 2 (v5.9.1)

05. 6 July 1944 — Normandy 2 (v5.9.1)

Note: This mission is the first (and only) to use 11/21 for RTB instead of 55/65.

06. 25 July 1944 (v5.9.1)

11. 8 August 1944 — Normandy 2 (v5.9.1)

12. 14 August 1944 — Normandy 2 (v5.9.1)

Flag Purpose Patterns

Based on cross-mission analysis, the following flag number ranges appear to have consistent purposes:

Summary Matrix

Notes for Editors

• When updating RTB point flags, update both the standalone script (RTB/Kills_RTB_points.lua) and the embedded script inside the .miz file.
• The 12 and 13 flags are used across all missions and may be hardwired into mission logic — verify before changing.
• 510, 511, 512 are used to broadcast end-state results. If the scoring flags change, the condition checks on these broadcast flags may also need adjustment.
• 999 is used as a general mission-end / reset flag in several missions.
• The "Mission" flag must be set manually per mission to the correct rotation day (1–8). It is not written by any script.

Last updated: 2026-04-28