Better Dropped Item Stacker

Better Dropped Item Stacker 1.7.0

Sign in to download
Combines scattered dropped items into one container
Documentation License Changelog (9) Reviews (4) Version History Discussion
This plugin helps improve your server performance by automatically combining dropped items into one container instead of leaving them scattered on the ground. It's useful during raids or when bases decay where large quantities of items are dropped at once.



How It Works

When a player drops an item, a short delay starts before checking for nearby dropped items. If the number of nearby items within the configured detection radius meets or exceeds the required threshold, the items will be grouped into a single container.

Grouping will not occur in the following cases:
  • The number of nearby items is below the minimum required for grouping.
  • The item is inside a safe zone.
  • The item belongs to a category listed in the exclusion list.
  • The item does not have a direct line of sight to the dropped location due to obstacles like terrain or buildings.

Configuration

JSON: 
{
  "Version": "1.7.0",
  "Time Delay Before Grouping Items Seconds": 5.0,
  "Minimum Nearby Items Required To Group": 5,
  "Item Detection Radius": 4.0,
  "Container Lifetime Seconds (0=auto-calculate)": 600.0,
  "Group Into Existing Containers": true,
  "Item Categories To Ignore During Grouping": [
    "Weapon",
    "Ammunition"
  ]
}
  • Time Delay Before Grouping Items Seconds - How long to wait after an item is dropped before checking for nearby items to group (in seconds).
  • Minimum Nearby Items Required To Group - Specifies the minimum number of dropped items that must be within the detection radius to trigger grouping. If fewer than this number are found, no grouping occurs.
  • Item Detection Radius - Determines the range in which nearby dropped items are detected for grouping.
  • Container Lifetime Seconds - Defines how long dropped item containers remain before despawning. Set to 0 to allow the game to automatically calculate the container's lifetime based on its contents.
  • Group Into Existing Containers - If set to true, the plugin will attempt to find an already existing dropped item container within range (and with a clear line-of-sight) and merge newly dropped items into it rather than spawning a new container.
  • Item Categories To Ignore During Grouping- A list of item categories that will NEVER be auto-grouped into containers. Categories include:
    • Weapon
    • Ammunition
    • Construction
    • Items
    • Resources
    • Attire
    • Tool
    • Medical
    • Food
    • Traps
    • Misc
    • All
    • Common
    • Component
    • Search
    • Favourite
    • Electrical
    • Fun

Developer Hooks

C#: 
void OnDroppedItemsGrouped(DroppedItemContainer container, List<DroppedItem> groupedItems)
Called after dropped items have been grouped into a container—whether by merging into an existing container or after spawning a new one.
  • No return behavior.
Author
VisEntities
Downloads
191
First release
Last update

Ratings

5.00 star(s) 4 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.7.0

    Dropped items are now merged into an existing container if one is found within range and...

  2. 1.6.0

    Added a new config option Container Lifetime Seconds. If set to a value greater than 0...

  3. 1.5.0

    Added OnDroppedItemContainerSpawned hook triggered after a dropped item container is spawned to...
Read more…

Latest reviews

magnumk
Works great!
Upvote 0 Downvote
srtbull
Love it. Works exactly as described. This will reduce drag on your server when players are raiding and leaving items behind to despawn.
Upvote 0 Downvote
fuscazo
love it
Upvote 0 Downvote
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 -