Configuration — DM.Config¶

The full DM.Config table, including internal fields not exposed in the mission-maker configuration template (templates/DynamicMission_Config.lua, see the mission-maker guide for the 13 fields meant for the mission maker).

Full table (verified defaults)¶

Field	Default	Role
`REGION_TICK_INTERVAL`	`30`	Fallback frequency if segment 4 is invalid
`IDLE_LIMIT`	`300`	Seconds without an enemy before auto-return to IDLE
`MAX_CYCLES_DEFAULT`	`10`	Fallback if segment 7 (MAX_C) is invalid
`AIRBASE_SPAWN_SLOT_DISTANCE`	`100 m`	Distance of the 6 defense slots from the runway edge
`AIRBASE_SPAWN_DEFENSE_PROXIMITY_RANGE`	`20 000 m`	Detection radius for proximity-triggered spawns
`PROXIMITY_CHECK_INTERVAL`	`30 s`	Proximity scheduler frequency
`AIRBASE_ANCRE_SLOT_OFFSET`	`50 m`	Distance of the 2 Jerrycan slots from the runway edge
`defenseSpawnGroupCount`	`min=1, max=3`	Random range of defense groups spawned per trigger
`SPAWN_DISPERSION_RADIUS`	`200 m`	Dispersion radius of units cloned into an `SZ_` zone
`LANDED_UNIT_SPEED_THRESHOLD`	`1 m/s`	Speed below which an air unit is considered "landed"
`LANDED_UNIT_PROXIMITY_RANGE`	`100 m`	Radius around a base excluded from cleanup
`BEEP_MESSAGE`	`true`	Automatic sound beep on F10 messages shown via `displayMessage()`
`BEEP_FILENAME`	`"message radio.ogg"`	Sound file for the beep above
`THREAT_ALERT_ENABLED`	`true`	Master switch for F10 "enemy contact" threat alerts
`THREAT_ALERT_INTERVAL`	`300 s`	Spacing between recurring alerts
`THREAT_ALERT_DURATION`	`20 s`	On-screen display duration of a threat alert
`THREAT_ALERT_ON_SPAWN`	`true`	One-off alert at the moment a group spawns (WP0 text)
`TYPE_CONTROL`	`"TERRAIN"`	Region activation mode (see Regions)
`AUTO_ACTIVATION_CHECK_INTERVAL`	`60 s`	Auto-activation scheduler frequency in `TERRAIN` mode
`MSG_QUEUE_INTERVAL`	`3 s`	Spacing between queued F10 messages (anti-spam)
`DEBUG_MODE`	`false`	Debug visualization of spawn slots on F10; bypasses the menu restriction (Manager & Events)
`DEBUG_REGION_FILTER`	`"RG_R_OUEST_30_NOFB_3_10_1"`	Limits debug circle display to a single region
`PREFIX_REGION`	`"RG"`	Nomenclature prefixes, configurable rather than hardcoded
`PREFIX_MODEL_GROUP`	`"MG"`	same
`PREFIX_SPAWN_ZONE`	`"SZ"`	same
`PREFIX_AIRBASE_DEFENSE`	`"AD"`	same
`DESIGNATED_PLAYER_NAME`	`""`	Name of the player allowed to see the F10 regions menu (see Manager & Events) — empty = nobody, outside `DEBUG_MODE`
`ERROR_SOUND_FILE`	`"l10n/DEFAULT/Alert.ogg"`	Sound played on a critical validation error

Internal structures and functions¶

mappingSlottypeGroupModel (hardcoded table, ~25 entries) maps each aircraft type to the MG_ tags it "counts" toward for dynamic filtering in FB mode.
ADtemplates is an internal table (not meant to be overridden) populated by the mission scan, indexed by coalition.
mergeConfig(defaults, overrides) allows a granular override by the mission maker (e.g. changing only defenseSpawnGroupCount.max) — exposed but unused internally, meant to be called directly from a mission DO SCRIPT (the mechanism the templates/DynamicMission_Config.lua template file uses).
validate() runs automatically on load and fixes malformed values with a warning, never blocking unless mappingSlottypeGroupModel is entirely empty.

Two fields can't be overridden after the fact

REGION_TICK_INTERVAL and MAX_CYCLES_DEFAULT are consumed once, while parsing a region's nomenclature, before any DO SCRIPT placed after DynamicMission.lua loads can run — the only lever left is the region's own nomenclature segment (segments 4 and 7, see Regions).