Airdrop Settings

Airdrop Settings 1.3.1

Sign in to download
Allows customization of airdrops and cargo planes
This Rust plugin lets you fully customize airdrops and cargo planes, including drop speed, flight height, parachute behavior, supply signal precision, and more.




Features

  • Setting how high the cargo plane spawns above the terrain.
  • Controlling how fast the cargo plane flies across the map.
  • Determining the speed at which the airdrop falls to the ground.
  • Enabling airdrops to spawn instantly without the need for a cargo plane.
  • Removing the parachute from airdrops.
  • Dropping airdrops exactly where the supply signal was thrown.
  • Setting how long the supply signal smoke lasts, with an option to remove it.
  • Customizing the despawn duration for airdrops.

Compatible Plugins

Configuration

All default values in the config match vanilla settings.
JSON:
{
  "Version": "1.2.0",
  "Cargo Plane Spawn Height": 250.0,
  "Cargo Plane Speed Level": "Normal",
  "Instant Drop Without Plane": false,
  "Airdrop Fall Speed Level": "Normal",
  "Remove Airdrop Parachute": false,
  "Drop Airdrop Exactly At Supply Signal Position": false,
  "Supply Signal Smoke Duration Seconds": 210.0,
  "Airdrop Despawn Time Seconds": 0.0
}
  • Cargo Plane Spawn Height - Sets the height at which the cargo plane spawns. Higher values will increase the plane's flight altitude, while lower values (including negative) will decrease it.
  • Cargo Plane Speed Level - Adjusts the speed of the cargo plane.
  • Instant Drop Without Plane - If enabled, airdrops will spawn instantly without being dropped by a cargo plane.
  • Airdrop Fall Speed Level - Controls how quickly the airdrop descends by adjusting its air resistance.
  • Remove Airdrop Parachute - If enabled, not only will the parachute be removed, but it will also cause the airdrop to fall faster.
  • Drop Airdrop Exactly At Supply Signal Position - If enabled, the airdrop will land exactly at the position where the supply signal was dropped. By default, the airdrop lands at a random position within a radius around the supply signal.
  • Supply Signal Smoke Duration Seconds - Sets the duration of the smoke emitted by the supply signal in seconds. Setting it to 0 removes the smoke entirely.
  • Airdrop Despawn Time Seconds - Specifies how long an airdrop remains before despawning. Set this value to 0 or any negative number to disable despawning.
Available speed levels for both Cargo Plane Speed Level and Airdrop Fall Speed Level config options:
  • VerySlow
  • Slow
  • Normal
  • Fast
  • VeryFast

Developer Hooks

C#:
object OnSupplyDropSettingsChange(SupplyDrop supplyDrop)
Called when a supply drop is about to be altered. Useful for preventing this plugin from modifying supply drops.
  • Returning false prevents the supply drop from being altered.
  • Returning null allows the default behavior.
C#:
object OnCargoPlaneSettingsChange(CargoPlane cargoPlane)
Called when a cargo plane is about to be altered. Useful for preventing this plugin from modifying cargo planes.
  • Returning false denies the settings change for the cargo plane.
  • Returning null allows the default behavior.
C#:
object OnSupplySignalSettingsChange(SupplySignal supplySignal)
Called when a supply signal is about to be altered. Useful for preventing this plugin from modifying supply signals.
  • Returning false denies the settings change for the supply signal.
  • Returning null allows the default behavior.

Harmony Hooks

The following hooks are implemented via Harmony patches:
C#:
object OnCargoPlaneUpdateDropPosition(CargoPlane cargoPlane, Vector3 newDropPosition)
Called before the cargo plane updates its drop position. Useful for modifying the drop position.
  • Returning a non-null value prevents the cargo plane from updating the drop position.
  • Returning null allows it.
C#:
object OnSupplySignalExplode(SupplySignal supplySignal)
Called before the supply signal explodes. Useful for modifying the airdrop position or altering the spawned cargo plane.
  • Returning a non-null value prevents the supply signal from exploding.
Author
VisEntities
Downloads
177
First release
Last update

Ratings

5.00 star(s) 2 reviews

Also by VisEntities

Latest updates

  1. 1.3.1

    Addressed potential issue related to recent changes in 0Harmony unpatching logic.
  2. 1.3.0

    Introduced the following hooks for developers to intercept and prevent modifications made by...
  3. 1.2.0

    Added Airdrop Despawn Time Seconds config option to specify how long an airdrop remains before...

Latest reviews

Very nice, simple, effective and no negative performance impact.
Great, simple to use airdrop plugin that works as expected and offers the config options any admin might need.
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart