Better Dropped Item Stacker (Legacy Thread)

Return to plugin
Status
Not open for further replies.
Recent First Highest Voted
Hey, any chance that the item drop despawn time be based on the item rarity of the contents inside? IE: a rock and torch inside would despawn much faster than a AK/Boom items.

Thanks!
 
Upvote 0 Downvote
Hey, any chance that the item drop despawn time be based on the item rarity of the contents inside? IE: a rock and torch inside would despawn much faster than a AK/Boom items.
Click to expand...
Done! Please refer to the documentation for examples of how the new despawn logic works
 
Last edited:
Upvote 0 Downvote
Great idea, really like this one!

Unfortunately for the PVE server I admin on both LootDefender and PreventLooting are used to protect player dropped loot and loot is locked to players who dealt the most damage to an NPC or Heli for example.
I think those plugins would interfere with this one, or vice-versa because of the fact the Loot containers here have no owner.

Might there be some way I could work around this?
 
Upvote 0 Downvote
(Manky)sieve said:
Unfortunately for the PVE server I admin on both LootDefender and PreventLooting are used to protect player dropped loot and loot is locked to players who dealt the most damage to an NPC or Heli for example.
I think those plugins would interfere with this one, or vice-versa because of the fact the Loot containers here have no owner.

Might there be some way I could work around this?
Click to expand...

This can't be resolved from the Better Dropped Item Stacker side as the plugin doesn’t have the information about who dealt the most damage or who should be set as the owner of the dropped container, so I'm not sure how this can be solved. What I could do is provide a hook that's triggered when this plugin spawns a dropped item container for grouping items, which other plugins could then use to set the owner id
 
Upvote 0 Downvote
VisEntities said:
This can't be resolved from the Better Dropped Item Stacker side as the plugin doesn’t have the information about who dealt the most damage or who should be set as the owner of the dropped container, so I'm not sure how this can be solved. What I could do is provide a hook that's triggered when this plugin spawns a dropped item container for grouping items, which other plugins could then use to set the owner id
Click to expand...
Thanks for your reply, I understand that. Adding a hook would be greatly appreciated, I hope its not too much trouble!

We could modify those plugins to set the owner id then like you suggest.
Hopefully in turn having a neater server by using this plugin and maintaining our loot locking mechanisms.
 
Upvote 0 Downvote
VisEntities said:
This can't be resolved from the Better Dropped Item Stacker side as the plugin doesn’t have the information about who dealt the most damage or who should be set as the owner of the dropped container, so I'm not sure how this can be solved. What I could do is provide a hook that's triggered when this plugin spawns a dropped item container for grouping items, which other plugins could then use to set the owner id
Click to expand...
This would help a lot for my situation as well. The dev of the plugin I use wouldnt have to track everyitem for PVE players to check who owns what item when its dropped. The plugin could let normal items be open for grabs but when packed, could assign the owner and negate looting. I am looking forward to this being implemented!
 
Upvote 0 Downvote
Status
Not open for further replies.
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 -