Solved Add Player to TC, Remove Yourself, Break TC to Ban Them

Return to plugin
jesusitonton

jesusitonton

I found a bug that can affect other players, you can prevent players from authorizing other players since authorizing them and destroying the closet bans them without any fault.
 
Recent First Highest Voted
If someone not authorized breaks the cupboard, it punishes everyone who was authorized, that's the point, it meant to stop people from being careless about who they let on their cupboard. If someone removes themselves and then destroys it, that's on the players for trusting the wrong person. In other words, the plugin isn't meant to handle trust issues...
 
Upvote 0 Downvote
VisEntities said:
If someone not authorized breaks the cupboard, it punishes everyone who was authorized, that's the point, it meant to stop people from being careless about who they let on their cupboard. If someone removes themselves and then destroys it, that's on the players for trusting the wrong person. In other words, the plugin isn't meant to handle trust issues...
Click to expand...
I mean that the one who is raiding does not need to raid the base by placing a foundation and then a closet, you authorize the one you want to ban and then you deauthorize yourself by breaking the closet, you ban the player without being at fault
 
Upvote 0 Downvote
You can make it so players can't authorize their friends, so they have to authorize themselves by pressing E in front of the cabinet to prevent this error since on my server players are kicking each other and it's very annoying.
 
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 -