You Shall Not Spawn

You Shall Not Spawn 1.1.2

Sign in to download
Prevents certain entities from spawning
This Rust plugin stops specified entities from spawning and removes any that are already present when the plugin is loaded.




Configuration

JSON:
{
  "Version": "1.1.2",
  "Clean Up Existing Entities On Startup": false,
  "Entity Keyword Blocklist (prefab or type keywords to block from spawning or remove if spawned)": [],
  "Entity Keyword Exception List (keywords to ignore even if matched in blocklist)": []
}
  • Clean Up Existing Entities On Startup - If true, the plugin will remove specified entities that already exist when the plugin is loaded.
  • Entity Keyword Blocklist - This is the main list of entity keywords you want to block. Add partial names of prefabs or entity types (e.g. scientist, chicken, BradleyAPC) and the plugin will prevent those entities from spawning. If the cleanup option above is enabled, it will also remove any already spawned ones.
  • Entity Keyword Exception List - This is used to skip specific matches from the blocklist. If something in this list matches an entity that would otherwise be blocked, it will be allowed instead. Use this when you want to block a broad category (like scientist) but allow specific ones (like scientistnpc_full_any)
Author
VisEntities
Downloads
48
First release
Last update

Ratings

5.00 star(s) 1 reviews

Also by VisEntities

Latest updates

  1. 1.1.2

    Fixed an issue where blocked entities weren't fully removed on plugin load when the cleanup...

Latest reviews

Sick of meddling with server convars or pesky items appearing where they shouldn't? Maybe you just don't like bears - whatever you dont like spawning on your server, this is the plugin for you!
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