Arma Reforger · Online Manual

STW/Air Drops

Faction-aware cargo delivery by map marker: mark a clear drop zone, choose an available item, then watch it arrive beneath a parachute.

Faction deliveryLeader requestsValidated drop zonesOptional C-130 flyby

For players

Only the leader of a player group can request an airdrop by default. The server resolves the leader's faction, filters the available items for that faction, and validates the marked area before any item can be selected.

  1. Become the leader of your group.
  2. Open the map and place a marker at the intended delivery point.
  3. Write one of the recognised marker texts: AIRDROP, AIR_DROP, or AIR DROP. They are case-insensitive.
  4. After the request is accepted, close the map. The delivery dialog opens after the map has closed.
  5. Select a Schedule: Immediate, Delayed, or Set Time of Day; then confirm the available Item to deliver. The faction is preselected and cannot be changed by the client.
Map-wheel shortcut: group leaders can use the Airdrop → Place AIRDROP command on the map wheel. It places the same request marker for you.

Scheduling a delivery

The delivery dialog can schedule a selected vehicle or crate using the scenario's in-game clock. The available choices are:

Delayed and absolute-date requests must meet the server's minimum scheduling delay. A date/time in the past, or one earlier than that minimum, is rejected safely and does not create a delivery. Multiple future requests may be scheduled; normal player requests still obey the faction cooldown when they become due, while Game Master requests remain exempt from that cooldown.

Game time: scheduled dates follow scenario time, including its configured time acceleration, rather than the server computer's real-world clock.

Crate drops and custom crate types

Request a crate drop with a marker named CRATE_DROP, CRATE DROP, or CRATEDROP; the text is case-insensitive. Group leaders can also use Airdrop → Place CRATE DROP on the map command wheel. After closing the map, choose the available crate type in the delivery dialog.

Create a new crate drop

  1. Create and configure an STW Crate in a Workbench session. Add the exact items and packed containers you want delivered.
  2. Let STW Crates save the crate. The generated crate-content JSON must be from STW Crates v2, which preserves items inside backpacks and other containers.
  3. Copy the JSON for exactly one crate into this server-profile folder:
$profile:STW/ParachuteDrop/CratesContent/

Give the file a meaningful .json name, for example STWEngineerCrateContentsUS.json. Its filename becomes the crate type shown in the drop dialog. The system discovers valid JSON files in this folder automatically—no configuration edit or server restart is needed after the file is copied.

Example custom crates: download the US medical crate or USSR medical crate, copy the file into CratesContent, and it will appear in the crate-drop picker.

Get more crates: visit the STW Discord crate resources channel for additional crates.

Easy-to-edit one-item sample

Download the one-item US crate sample for the smallest valid STW Crates v2 crate definition. It contains one US medical kit, making it a clean starting point for a new crate type.

  1. Download the sample, rename it (for example, STWAmmoCrateContentsUS.json), and place it in $profile:STW/ParachuteDrop/CratesContent/.
  2. Replace the value of the item's prefab field with the full ResourceName of the item you want to deliver.
  3. To add items, duplicate the complete object inside the items array, separate the objects with commas, and change each prefab value. Keep the outer file to exactly one crate.
Editing tip: preserve the JSON punctuation and the STW_PERSISTENT_CRATES, version, and inventory-format fields. For containers such as backpacks, create and save the desired crate in STW Crates instead so its nested contents are captured correctly.
Easy workflow: make one STW Crate, let it persist, copy its v2 JSON contents into CratesContent, then request a CRATE_DROP. The delivered crate receives a new identity and the requesting player's faction, while retaining the configured contents.
Important: a full persistence snapshot used as a crate type must contain one crate only. STW Crates v1 files are obsolete and are ignored. The two built-in medical samples are installed automatically when missing.

Random crate catalog download

Random Combat Supplies and Random Apparel Crates are supplied by STW Crates and can be selected in the crate-drop dialog only when their public catalogs are installed on the server.

  1. Download STWRandomCratesWeapons.json and STWRandomCratesApparel.json. You can also download the STWExplosivesAndMinesUS_USSR.json crate.
  2. Place both catalog files in:
$profile:STW/Crates/Catalogs/

Restart the scenario/server after copying the files. The weapons catalog is required for Random Combat Supplies Crates and the apparel catalog is required for Random Apparel Crates. The path uses Catalogs, with an s.

Automatic airdrop deployments

The authoritative server can periodically deploy one random STW crate to a random safe location anywhere on the map. This is independent of player markers, player cooldowns, and Game Master placement requests.

Every cycle waits a newly randomized real server-time interval. The default range is 60 to 90 minutes. Scenario time acceleration does not shorten it, and a server/scenario restart starts a fresh interval rather than preserving a countdown.

Each deployment chooses an available random crate type with equal weight, then selects an eligible faction and available size at random. Random Combat Supplies and Random Apparel crates remain available when their public STW Crates catalogs are installed; they are faction-neutral.

The server samples up to 64 map locations and applies the same landing-zone validation used for ordinary airdrops. If no safe location is found, it skips that cycle and schedules the next one; it never drops a crate at an unsafe fallback location.

Scenario Properties

Game Masters can make session-only changes through Scenario Properties → STW Air Drops:

ControlEffect
Automatic Airdrop DeploymentsEnables or disables future automatic deployments for the current session.
Minimum PeriodShortest real server-time delay before the next automatic deployment.
Maximum PeriodLongest real server-time delay before the next automatic deployment.
Session-only: Scenario Properties overrides do not rewrite the server profile. The next server/scenario session returns to the JSON configuration defaults.

Drop-zone rules

STW/Air Drops uses the established Transport Helipads landing-zone acceptance rules. A request is rejected when the target area is unsafe for a delivery.

Choose clear, level ground

Keep the target clear of substantial obstacles and avoid steep or sharply uneven terrain.

Keep out of water and trees

Water, trees, and major obstructions reject the request. Choose an open field, yard, or other landing-sized clear area.

The server checks the location when the marker is accepted and checks again immediately before starting the delivery. If the area is no longer valid, no payload is released.

What you see after acceptance

Your typed request marker is immediately replaced with a locked STW airdrop icon in your faction colour. It is visible only to the owning faction and remains while you select an item and while the payload is descending.

Cooldown: after a successful request, the faction must wait for the configured cooldown before making another delivery. The server remains authoritative for this check.

Delivery availability and optional vehicle content

The item list is faction-filtered and resource-checked by the server. STW/Air Drops carries its own allow-list, so it does not require STW/Light Vehicles and does not start that mod's automatic vehicle spawner.

Vanilla choices are available for their factions. Optional RHS, HMMWV variants, TIGR, and JLTV entries appear only when their source prefabs are installed and usable by the server. Players can never submit an item the server has not approved.

Multiplayer requirement: every client and the server need the source add-on for any selected optional vehicle prefab. If it is absent, STW simply leaves it out of the delivery picker.

For Game Masters and scenario authors

Use a clear target area and a faction with at least one valid delivery item. The map-marker request flow is intended for live players; Game Master use follows the configured default faction when no ordinary player faction can be resolved.

For a cinematic event, leave the C-130 flyby enabled. For a minimal or silent logistics experience, disable it: the parachute delivery remains fully functional without the aircraft visual.

Scenario design tip: provide obvious open delivery fields rather than placing objectives inside dense forests, water margins, or closely packed compounds. The validation is deliberately strict so delivered vehicles do not arrive inside unsafe geometry.

Server configuration

The server creates the configuration file on its first start:

$profile:STW/ParachuteDrop/STWParachuteDropConfig.json

Stop the server before editing it, then restart the scenario/server after saving changes.

SettingPurposeDefault
EnabledMaster switch for the airdrop service.true
EnableChatMessagesShows airdrop request and delivery status updates in the player's radio chat.true
EnableNotificationMessagesShows the same status updates as on-screen hint notifications.false
EnableMarkerRequestsEnables recognised map-marker requests and the map-wheel flow.true
RequireGroupLeaderForMarkerRequestsRestricts delivery requests to group leaders.true
AllowImmediateDeliveryAllows Immediate scheduling. When false, the dialog offers only Delayed and Set Time of Day.true
MinimumSchedulingDelayMinutesMinimum lead time for Delayed and Set Time of Day deliveries.10
AutomaticAirdropDeploymentsEnables periodic, server-authoritative automatic crate deployments.true
AutomaticAirdropMinimumPeriodMinutes
AutomaticAirdropMaximumPeriodMinutes
Random real server-time interval between automatic deployment attempts.60
90
AutomaticAirdropEnabledFactionKeysOptional faction allow-list for faction-specific automatic crates. An empty list permits all active factions.[]
AutomaticAirdropExcludedFactionKeysFaction deny-list for automatic crates. Exclusions override the allow-list.[]
RequestTimeoutSecondsLegacy setting; accepted requests now remain pending until they are confirmed or cancelled.60
CooldownSecondsFaction wait time after a successful delivery request.300
DefaultDropAltitudeAGLStarting payload height in metres above ground level.300
DescentSpeedMetersPerSecondControlled cargo descent rate.6
EnableAircraftFlybyEnables the optional C-130 visual and sound flyby.true
AircraftFlybyAltitudeAGL
AircraftFlybyDistanceMeters
AircraftFlybySpeedMetersPerSecond
Controls the flyby's height, route length, and visual speed.300
1600
110
DefaultGameMasterFactionFallback faction for Game Master-directed use.US