🎃 Halloween Sale is live with 30% off all plugins 👻 Loading…

Unload Plugin When Specific Player Joins

jordo2k1

Supporter
ok so this is a strange one. so i have a situation with a plugin and ive had to remove it due to a player having issues with it.
however the other 99% of players want the plugin back...
is there a way to write a plugin that will unload a certain plugin when a specific player (or players) come online and then loads the named plugin again once they log off the server?

strange request i know but if possible it could open the ability for other things maybe....
 
This sounds more like a custom request than something I would include in a public plugin, since it's very specific to your situation
 
i mean it could be used in more situations but i suppose its very specific to an issue i have lol. i would be will to purchase if its possible
 
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