Added a new config option Container Lifetime Seconds. If set to a value greater than 0, containers will use this exact lifetime. If set to 0, the container's lifetime is automatically calculated based on the longest despawn duration of the items inside it (matching vanilla behavior).
Removed redundant fallback despawn time calculation for containers. The game already guarantees containers have a despawn duration based on their contents.
Renamed the hook from OnDroppedItemContainerSpawned to OnDroppedItemStackerSpawned.
Added OnDroppedItemContainerSpawned hook triggered after a dropped item container is spawned to group items. This is useful for plugins that need to set the owner id of the dropped item container.
Prevent grouping dropped items when being in safe zones. This's to address the issue where dropped item containers, having no owner, could not be opened due to safe zone restrictions on inventory access.
Implemented a LOS check so that items are only grouped if they are visible to each other, preventing items in different rooms or behind walls from being grouped together.
Dropped item containers now spawn more accurately on the nearest surface.
The removal time for dropped item containers is now dynamically calculated based on the items inside. This means items with a quick despawn duration will influence the overall removal time of the container, but will never be less than the configured fallback time specified by Dropped Item Container Fallback Despawn Time Seconds.
Added Item Categories To Exclude From Grouping config option that allows specifying item categories to exclude from moving into the dropped item container. Refer to the documentation for a complete list of categories.
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.
