Leaderless Team Disband

Leaderless Team Disband 1.0.0

Sign in to download
Breaks up teams when their leader dies
Documentation License Version History Discussion
This plugin automatically disbands teams whenever the team leader is killed.




Configuration

JSON: 
{
  "Version": "1.0.0",
  "Disband If Killed By Player": true,
  "Disband If Killed By NPC": false,
  "Disband If Killed By Animal": false
}
  • Disband If Killed By Player - Determines whether the team disbands when the leader is killed by another player.
  • Disband If Killed By NPC - Specifies if the team should disband when the leader is killed by an npc.
  • Disband If Killed By Animal - Specifies if the team should disband when the leader is killed by an animal.
Author
VisEntities
Downloads
9
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

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 -