Airdrop Turrets

Airdrop Turrets 1.1.0

Sign in to download
Deploys auto turrets onto airdrops
Documentation License Changelog (1) Version History Discussion
This plugin adds auto turrets to airdrops as soon as they spawn, with customizable options for the turret's weapon, attachments, and ammo.

Upon loading the plugin, any existing airdrops still in the air will also have turrets deployed on them, and when the plugin is unloaded, all turrets are removed, leaving no traces behind.


Compatible Plugins

  • Airdrop Settings - Allows customization of airdrops and cargo planes.
  • Legacy Airdrops - Brings back legacy airdrops where cargo planes drop multiple airdrops instead of just one.

Configuration

JSON: 
{
  "Version": "1.1.0",
  "Weapon Shortname": "rifle.ak",
  "Clip Ammo": {
    "Shortname": "ammo.rifle",
    "Amount": 30
  },
  "Reserve Ammo": [
    {
      "Shortname": "ammo.rifle",
      "Amount": 128
    },
    {
      "Shortname": "ammo.rifle",
      "Amount": 128
    }
  ],
  "Attachment Shortnames": [
    "weapon.mod.lasersight"
  ],
  "Peacekeeper": true,
  "Turn On Only After Airdrop Has Landed": false
}
  • Weapon Shortname - The shortname of the weapon to be placed in the auto turret.
  • Clip Ammo - Specifies the type and amount of ammo loaded in the turret's weapon clip.
  • Reserve Ammo - A list of ammo types and amounts for the turret's reserve. Note that each entry will occupy its own slot in the turret's inventory, adhering to the maximum allowed stack size.
  • Attachment Shortnames - A list of weapon attachments to be added to the turret's weapon.
  • Peacekeeper - Specifies whether the turret should be in peacekeeper or hostile mode.
  • Turn On Only After Airdrop Has Landed - Determines whether the auto turret should be turned on only after the airdrop has landed on the ground or immediately after it spawns.
Author
VisEntities
Downloads
36
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.1.0

    Added config option to turn on turret only after airdrop has landed.
Read more…
Back
Top
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.
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.
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. Make sure 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

Cart

Total -