Limited Siege Bomb Deploy

Limited Siege Bomb Deploy 1.0.0

Sign in to download
Stops players from placing too many siege bombs close together
Documentation License Version History Discussion
This plugin prevents siege bomb spam by limiting how many can be placed in one area. Players attempting to place too many in close proximity will be blocked. The limit and detection range can be customized in the config.




Permissions

  • limitedsiegebombdeploy.ignore - Allows a player to bypass the limit and place unlimited siege bombs.

Configuration

JSON: 
{
  "Maximum Nearby Siege Bombs": 5,
  "Siege Bomb Check Radius": 5.0,
  "Siege Bomb Prefab Names": [
    "assets/prefabs/weapons/deployablesiegeexplosives/flammablesiegedeployable.prefab",
    "assets/prefabs/weapons/deployablesiegeexplosives/explosivesiegedeployable.prefab"
  ]
}
  • Maximum Nearby Siege Bombs - Sets the maximum number of siege bombs a player can place within the check radius. Once this limit is reached, additional bombs cannot be deployed.
  • Siege Bomb Check Radius - Determines the area around a newly placed bomb that is checked for existing bombs. If too many are found within this radius, placement will be blocked.
  • Siege Bomb Prefab Names - A list of prefabs that are affected by the limit. Only siege bombs matching these names will be restricted.

Localization

JSON: 
{
  "BombDeployRestricted": "Too many siege bombs deployed nearby."
}
  • Like
Reactions: (Manky)sieve
Author
VisEntities
Downloads
16
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

  • No Raid Debris
    No Raid Debris
    Disables debris that block building during raids
  • TC Ban
    TC Ban
    Bans or kicks players when their cupboard gets destroyed
  • Barricade To Wall
    Barricade To Wall
    Turns barricades into high external walls automatically
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 -