Skip to content
Medusa IADS Medusa IADS

Quick Start

Minimal setup

Section titled “Minimal setup”
  1. Set your prefix and coalition (the default prefix is iads but most mission makers use their coalition name): 
    MEDUSA_CONFIG = {
        Networks = {
            {
                name = "RED IADS",
                coalition = "red",
                prefix = "RED",
            },
        },
    }
  2. Name your SAM groups in the Mission Editor starting with the prefix: 
    RED SA-10 Damascus
    RED SA-6 Homs-1
    RED SA-11 Aleppo-2
    RED SA-15 Mezzeh
    RED EWR Damascus-1
    That’s all you need. Optionally, use Dot-Echelon notation to add command hierarchy (RED.1bde.1bn.sa10).
  3. Load the script (see Installation)
  4. Start the mission

Medusa will automatically:

  • Discover all groups matching the prefix on the configured coalition
  • Classify batteries by DCS unit attributes (LR_SAM, MR_SAM, SR_SAM, AAA)
  • Probe sensor and weapon ranges from DCS unit data
  • Auto-assign SHORAD as point defense for nearby LR/MR SAMs
  • Apply EMCON policies per battery role
  • Detect HARM threats via kinematic analysis
  • Assign targets based on Pk scoring and engagement envelopes

Blue coalition example

Section titled “Blue coalition example”
MEDUSA_CONFIG = {
    Networks = {
        {
            name = "BLUE IADS",
            coalition = "blue",
            prefix = "blue",
        },
    },
}

Name your groups blue.patriot.1bn, blue.ewr.west, etc.

Adding doctrine

Section titled “Adding doctrine”

Override tactical behavior by setting Medusa_MM_Doctrine before loading Medusa:

Medusa_MM_Doctrine = {
    Name = "Aggressive",
    ROE = "FREE",
    HARMResponse = "AUTO_DEFENSE",
    SAMAsEWR = "WHEN_NO_EWR",
    EMCON = {
        EWR    = "PERIODIC_SCAN",
        LR_SAM = "PERIODIC_SCAN",
        MR_SAM = "ALWAYS_ON",
        SR_SAM = "MINIMIZE",
    },
    ScanSec = 20,
    QuietPeriodSec = 40,
}

See the Doctrine Guide for all available options.

Next steps

Section titled “Next steps”