Half Looted Emptier

Half Looted Emptier 1.1.0

Sign in to download
Empties loot containers that players leave half-looted
Documentation License Changelog (2) Version History Discussion
This Rust plugin empties loot containers that players leave partially looted, ensuring they despawn so new ones can spawn in their place.




Configuration

JSON: 
{
  "Version": "1.1.0",
  "Emptying Trigger Mode": "Looted",
  "Number Of Items To Trigger Emptying": 1,
  "Delay Before Emptying Container Seconds": 30.0,
  "Remove Items Instead Of Dropping": false
}
  • Emptying Trigger Mode - Determines the trigger condition for clearing a container. Use Remaining to base it on items left in the container or Looted to base it on items taken.
  • Number Of Items To Trigger Emptying - The count threshold; if the number of items (remaining or looted, depending on the mode) meets this threshold, the container will be emptied.
  • Delay Before Emptying Container Seconds - The delay after a player stops looting before the container is cleared.
  • Remove Items Instead Of Dropping - When set to true, the remaining items are removed rather than dropped on the ground.
  • Like
Reactions: DeviLuna
Author
VisEntities
Downloads
140
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

  • House Keys
    House Keys
    Enables remote control of doors, locks, and turrets in any building
  • Restart Countdown
    Restart Countdown
    Shows a countdown ui when a server restart is scheduled
  • One Time Bag
    One Time Bag
    Turns sleeping bags into single-use respawn points

Latest updates

  1. 1.1.0

    You can now choose whether a container should be emptied based on the number of items left...

  2. 1.0.1

    Improved item drop behavior to ensure items don't appear in unintended or obstructed locations.
Read more…
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 -