Bradley Kill Cooldown

Bradley Kill Cooldown 1.1.0

Sign in to download
Adds a cooldown after killing a Bradley so the same players can't farm it nonstop
Documentation License Changelog (1) Version History Discussion
Works With
Clans, Friends
This Rust plugin stops the same players from killing all the Bradleys across the map by applying a configurable global cooldown. Whether they're in a team, clan, or friends list, anyone in that group will be blocked from damaging another Bradley until the cooldown ends. Great for servers that want to prevent nonstop Bradley farming and give other players a fair chance to take one down too.



Permissions

  • bradleykillcooldown.bypass - Allows the player to ignore the Bradley kill cooldown entirely.

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Minutes Before Player Can Kill Another Bradley": 60.0,
  "Bradley Kills Needed To Start Cooldown": 1
}
  • Minutes Before Player Can Kill Another Bradley - How many minutes a player and their allies must wait before being allowed to kill another Bradley APC.
  • Bradley Kills Needed To Start Cooldown - How many Bradley kills by the same player are required before the cooldown starts.

Localization

JSON: 
{
  "Notice.OnCooldown": "You must wait {0} before engaging another Bradley.",
  "Notice.CooldownStarted": "You and your allies are restricted from attacking another Bradley for the next {0}."
}
Author
VisEntities
Downloads
15
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.1.0

    Cooldown now triggers after X Bradley kills.
Read more…
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

Cart

Total -