Created Mission Moose Patcher.

DCS_Kola/Operation_Polar_Shield/Moose_OperationPolarShield.lua

@@ -6,14 +6,14 @@
 -- These set max units, not groups. For example, the manpad group in the mission editor is 2 units. So if MAX_RU_MANPADS = 10, then 5 groups of manpads will spawn.
 -- So you have to know how many units are in each group to set these limits effectively.
 
-MAX_RU_MANPADS = 10         -- Each group has 2 units, so 10 = 5 groups of 2.
-MAX_RU_AAA = 25             -- Each group has 1 units, so 25 = 25 groups of 1. 
+MAX_RU_MANPADS = 20         -- Each group has 2 units, so 10 = 5 groups of 2.
+MAX_RU_AAA = 20             -- Each group has 1 units, so 25 = 25 groups of 1. 
 MAX_RU_TANK_T90 = 10        -- The rest of these groups have 1 unit each.
 MAX_RU_TANK_T55 = 10
-MAX_RU_IFV = 35
-MAX_RU_IFV_Technicals = 45
-MAX_RU_SA08 = 15
-MAX_RU_SA19 = 15
+MAX_RU_IFV = 15
+MAX_RU_IFV_Technicals = 25
+MAX_RU_SA08 = 10
+MAX_RU_SA19 = 12
 MAX_RU_SA15 = 30            -- This is a group of 3 . Sa15 + Shilka + Ammo truck.
 MAX_RU_SA2 = 120            -- Each group has 15 units, so 120 = 8 groups of 15.
 MAX_RU_SA6 = 88             -- Each group has 11 units, so 88 = 8 groups of 11.

Moose_DualCoalitionZoneCapture/Example_Mission_Description.txt

@@ -0,0 +1,48 @@
+MOOSE Dual Coalition Zone Capture - Example Mission
+===================================================
+
+MISSION OVERVIEW:
+This is a demonstration mission showcasing the MOOSE Dual Coalition Zone Capture system's 
+dynamic behavior and visual feedback mechanisms.
+
+SCENARIO:
+Four strategic zones have been marked across the battlefield:
+• Zone 1: Initially controlled by RED forces
+• Zone 2: Initially controlled by BLUE forces  
+• Zone 3 & 4: Neutral territory, awaiting capture
+
+DEMONSTRATION FEATURES:
+Ground units from both coalitions patrol the battlefield in a continuous cycle, moving between 
+zones to demonstrate the system's real-time response to territorial changes. Units are configured 
+in a non-combat mode to clearly showcase zone state transitions without interference from combat.
+
+WHAT YOU'LL SEE:
+✓ Color-coded zone boundaries changing as units enter/exit (Red/Blue/Green/Orange)
+✓ Tactical information markers updating with force compositions
+✓ Smoke signals marking zone status changes
+✓ Automatic messaging system announcing captures and attacks
+✓ F10 radio menu commands for zone status queries
+✓ Victory condition tracking as zones are captured
+
+OBSERVING THE DEMONSTRATION:
+• Use F10 Map to view zone boundaries and tactical markers
+• Monitor chat messages for zone status updates
+• Access F10 → Zone Control → "Get Zone Status Report" for detailed information
+• Watch as zones transition between Empty → Captured → Attacked → Guarded states
+• Victory condition triggers when one coalition controls all four zones
+
+PURPOSE:
+This mission serves as both a tutorial and testing environment for mission makers looking to 
+implement the zone capture system in their own scenarios. It demonstrates proper configuration, 
+visual feedback, and system behavior without the chaos of active combat.
+
+MISSION MAKER NOTES:
+Examine the mission file to see:
+- Proper trigger zone naming conventions
+- BLUEHQ and REDHQ group placement
+- Script loading order in triggers
+- Zone configuration in the Lua file
+- Unit waypoint setup for continuous patrol demonstration
+
+This is a reference implementation - feel free to modify, expand, or use as a template for your 
+own mission designs!