Supply_Scripts — v1.5

DCS World mission scripts that manage airfield logistics: fuel resupply flights and tracked aircraft deliveries for warehouse restocking in the Normandy theatre.

Overview

These Lua scripts listen for two world events:

• Landing (event.id 4 / world.event.S_EVENT_LAND) — triggers fuel deliveries to target warehouses when a resupply group lands, and tracks landed aircraft for warehouse restocking.
• Player Leaves Unit (event.id 21 / world.event.S_EVENT_PLAYER_LEAVE_UNIT) — converts tracked aircraft into warehouse stock when the player exits the delivery aircraft.

v1.5 correction: earlier versions of this README described the second event as "Unit Removed". Event 21 in DCS is S_EVENT_PLAYER_LEAVE_UNIT. The functional behavior (warehouse restock) is the same: a player delivers a tracked aircraft to the airbase, lands, exits, and the configured aircraft_return_multiplier is added to the warehouse item count at the airbase where the aircraft was tracked.

There is no F10 menu in this version; players or mission makers read warehouse state directly in the Mission Editor or via external tools.

Current Mission Scripts

All of these share the same generic engine (supplies_template.lua). Only the CONFIG table at the top differs per mission.

Legacy originals moved to old/ (archived for reference only).

Generic Template: supplies_template.lua

supplies_template.lua is a mission-agnostic drop-in replacement. You configure a single CONFIG table at the top of the file instead of editing hardcoded logic throughout the script.

Configuration Sections

When an aircraft tracked by aircraft_deliveries is left by its player (event 21 fires), the script adds the configured aircraft_return_multiplier to the warehouse item count. Set this value higher than 1 to reward larger stock returns per delivery (for example, CONFIG.aircraft_return_multiplier = 3).

Example snippet

CONFIG.resupply_flights = {
  {
    group_name = "Blue_Resupply 1-1",
    land_at = "Sainte-Laurent-sur-Mer",
    deliveries = {
      { airbase = "Saint Pierre du Mont", liquid_type = 1, amount = 4000 },
      { airbase = "Cricqueville-en-Bessin", liquid_type = 1, amount = 5000 },
    }
  },
}

CONFIG.aircraft_deliveries = {
  {
    aircraft_type = "MosquitoFBMkVI",
    land_at = { "Saint Pierre du Mont", "Sainte-Croix-sur-Mer" },
    warehouse_item = "MosquitoFBMkVI",
    tracked_table = "mosquitos",
    exclude_pattern = "Player deliverable",
  },
}

Neutral Bases

Instead of auto-scanning all airbases at mission start, each mission file now contains an explicit CONFIG.neutral_bases list. Only the named bases are forced neutral (coalition = 0, autoCapture = false).

This avoids surprises when the map changes or new airbases are added by ED, and makes the mission configuration fully self-documenting.

Migration from v1.2 templates:

• Remove CONFIG.limited_bases, CONFIG.counted_aircraft, and CONFIG.f10_update_interval.
• Keep CONFIG.neutral_bases = { "Name1", "Name2", ... }.
• Populate the list by copying the names from the old neutralBases table or extracting from your mission's airbase list.

Logic Flow Diagrams

Landing Event Flow

Player Leave / Warehouse Restock Flow

Neutral Base Setup Flow

Changelog

Dependencies

• DCS World with Lua 5.1 runtime