Solved Ownership Based on Grenade Thrower

Return to plugin
coresnap

coresnap

Supporter
Amazing plugin! Again, something I've looked for quite awhile now and this does everything I ever wanted!
Would it be possible to add in base/entity ownership? ie, whoever throws the grenade is who the base/entities are linked to.

Obvious use case would be to immediately designate who the owner is (using something like EntityOwner) and being able to remove all placed/owned entities by said owner (using something like PlayerEntityRemover).

Much love, and wonderful addition to your catalog. :D
 
Recent First Highest Voted
coresnap said:
Amazing plugin! Again, something I've looked for quite awhile now and this does everything I ever wanted!
Would it be possible to add in base/entity ownership? ie, whoever throws the grenade is who the base/entities are linked to.

Obvious use case would be to immediately designate who the owner is (using something like EntityOwner) and being able to remove all placed/owned entities by said owner (using something like PlayerEntityRemover).

Much love, and wonderful addition to your catalog. :D
Click to expand...
welp, scrap that cuz I could've sworn that wasn't a thing and my copy/paste plugin is broken AF! Looks like you already have that. I'm sure you love me at this point! XD
Thanks again!
 
Upvote 0 Downvote
coresnap said:
welp, scrap that cuz I could've sworn that wasn't a thing and my copy/paste plugin is broken AF! Looks like you already have that. I'm sure you love me at this point! XD
Thanks again!
Click to expand...
I mean Copy Paste provides the entityowner option, but I haven't tested whether it actually sets the pasted entities' owner to the player doing the pasting (in this case the one who threw the grenade). You could try adding it under Paste Options and see if it works (y)
 
Upvote 0 Downvote
You must log in or register to reply here.
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 -