No Chinook Crate Pileup

No Chinook Crate Pileup 1.1.0

Sign in to download
Prevents multiple chinook crates from piling up in the same area
Documentation License Changelog (1) Version History Discussion
No Chinook Crate Pileup is a Rust plugin that solves a common issue where multiple hackable locked crates from Chinook helicopters can land in the same location, creating unfair advantages and cluttered gameplay. This plugin automatically detects when a new crate lands near existing crates and removes the older ones, ensuring a clean and balanced loot distribution across your map.

The plugin will NOT remove crates that are:
  • Currently being hacked by players
  • The newly landed crate itself

Configuration

JSON: 
{
  "Version": "1.1.0",
  "Nearby Crate Search Radius": 1.5
}
  • Nearby Crate Search Radius - The distance in meters from a newly landed crate to check for existing crates. Any crates found within this radius that are not being actively hacked will be automatically removed.
Author
VisEntities
Downloads
38
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 Nearby Crate Search Radius config option to customize the detection range for removing...
Read more…
  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
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

Cart

Total -