TC Ban

TC Ban 1.1.0

Sign in to download
Bans or kicks players when their cupboard gets destroyed
Documentation License Changelog (1) Version History Discussion
This plugin automatically kicks or bans players if someone outside their group destroys their tool cupboard. Great for adding consequences to poor placement and making cupboards more valuable.




Permissions

  • tcban.ignore - Players with this permission will not be punished when their cupboard is destroyed, even if they were authorized.

Configuration

JSON: 
{
  "Version": "1.1.0",
  "Punishment Type (Ban or Kick)": "Kick",
  "Broadcast Punishment": true,
  "Delete Owned Entities After Punishment": false
}
  • Punishment Type - Decides how to punish players who were authorized on the destroyed cupboard. Options: Ban or Kick.
  • Broadcast Punishment - If enabled, sends a global message to all players when a punishment happens.
  • Delete Owned Entities After Punishment - If enabled, after a player is punished (banned or kicked) due to their cupboard being destroyed, the plugin will iterate over all of that player's owned entities and remove them.

Localization

JSON: 
{
  "BanReason": "You were banned because your tool cupboard was destroyed by an outsider.",
  "KickReason": "You were kicked because your tool cupboard was destroyed by an outsider.",
  "BanBroadcast": "All players authorized on the destroyed tool cupboard have been smacked with a BAN!",
  "KickBroadcast": "All players authorized on the destroyed tool cupboard got KICKED off the server!"
}
Author
VisEntities
Downloads
8
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.1.0

    Added a new config option to remove all entities owned by banned or kicked players.
Read more…
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 -