Better No Escape

Better No Escape 1.1.0

Prevents teleportation, crafting, building, and more while in combat or raiding
image.jpg




This plugin temporarily blocks players from using certain commands and actions while in combat or during a raid. When a player attacks or gets attacked by others, or damages another player's base, they'll be placed into combat- or raid-block for a set duration. During this block, actions such as teleportation, crafting, repairing, building, and many more are disabled until the timer runs out.

Features

  • Temporarily block commands and actions during combat or raids.
  • Configurable block durations for both combat and raid.
  • Supports dual-blocking (raid and combat blocks active simultaneously).
  • Block commands entered by players via chat or the in-game F1 console.
  • Restrict over 20 different player actions, including crafting, building, teleporting, and more.
  • Customize which damage types (e.g., bullets, explosives) cause blocks.
  • Control exactly which entities trigger combat or raid blocks based on prefab or entity type.
  • Only trigger raid blocks when damaging entities owned by players, preventing accidental blocks from attacking neutral objects at monuments.
  • Control whether damage dealt or received triggers combat block, with configurable damage thresholds.
  • Optionally ignore friendly fire from teammates, friends, and clan members.
  • Supports creating automatic raid zones that block all actions within their radius.
  • Choose which players get raid blocked depending on their relationship with raiders or defenders (e.g., friends, clanmates, authorized players).
  • Grant VIPs or specific groups different restrictions for commands and actions during combat or raids.
  • Automatically unblock players upon death, respawn, or disconnect.
  • User-friendly HUD displays remaining combat and raid block durations clearly, with customizable appearance (colors, icons, text, position).
  • Admin command to instantly clear combat or raid blocks for any player.
  • Compatible with Zone Manager, NTeleportation, Clans, Backpacks, and other popular plugins.

Permissions

  • betternoescape.admin - Allows use of administrative commands, including clearing combat or
  • betternoescape.bypass - Players with this permission ignore all combat and raid block restrictions.
  • betternoescape.{suffix} - Grants the restrictions configured in your permission profile. (Replace {suffix} with your actual permission profile suffix, e.g., betternoescape.vip).

Commands

  • bne.reset <playerNameOrId> [combat|raid]- Clears the specified type of block from a player.
    • playerNameOrId - The name or Steam ID of the target player.
    • [combat|raid] - (Optional) Type of block to clear. Defaults to both if omitted.

Combat Block

Settings that determine when and how players get blocked after engaging in combat.
JSON:
  "Combat Block": {
    "Enabled": true,
    "Block Duration Seconds": 180.0,
    "Block Attacker On Damage Dealt": true,
    "Minimum Damage To Block Attacker": 0.0,
    "Block Victim On Damage Taken": true,
    "Minimum Damage To Block Victim": 0.0,
    "Damage Accumulation Window Seconds": 5.0,
    "Ignore Friendly Fire": true,
    "Include Entity Keywords (prefab or type name substring)": [
      "scientist",
      "patrolhelicopter",
      "bradleyapc"
    ],
    "Exclude Entity Keywords (prefab or type name substring)": [
      "corpse"
    ],
    "Allowed Damage Types": [
      "Bullet",
      "Arrow",
      "Blunt",
      "Slash",
      "Stab",
      "ElectricShock"
    ],
    "Ignored Weapon Prefabs": [],
    "Blocked Commands": [
      "tp"
    ],
    "Disallowed Actions": [
      "NoCraft",
      "NoBuild",
      "NoItemDrop",
      "NoRepair",
      "NoUpgrade",
      "NoRecycle",
      "NoVending",
      "NoKit",
      "NoTeleport",
      "NoTrade",
      "NoBackpack",
      "NoHeal",
      "NoStash",
      "NoMount",
      "NoItemDeploy",
      "NoAuth",
      "NoDeauth",
      "NoItemPickup",
      "NoBank"
    ]
  },
  • Enabled - Turn on or off combat blocking entirely. Disable this if you only want raid blocking.
  • Block Duration Seconds - How long the player remains blocked after combat starts, in seconds.
  • Block Attacker On Damage Dealt - Enable to block a player whenever they deal damage. Useful if you want aggressive players blocked, not just victims.
  • Minimum Damage To Block Attacker - Total accumulated damage a player must deal within the set time window to become blocked. Set higher to avoid minor damage (like accidental hits) triggering blocks.
  • Block Victim On Damage Taken - Enables blocking players when they're hit, even if they don't fight back. Good for enforcing fair fights or preventing quick escapes.
  • Minimum Damage To Block Victim - Minimum damage a victim must receive before being blocked. Useful to prevent very minor damage (e.g., tiny fall damage) from triggering unnecessary blocks.
  • Damage Accumulation Window Seconds - Damage totals reset after this time window. Set short (e.g., 5–10 seconds) to ensure only concentrated attacks trigger blocks.
  • Ignore Friendly Fire - If enabled, teammates, clan members, or friends hitting each other will never trigger blocks, avoiding accidental friendly-fire penalties.
  • Include Entity Keywords - Keywords used to specify which entities trigger the combat block when damaged. The plugin checks if either the prefab name or the entity type name contains any of these keywords (partial matches allowed, case-insensitive). Leave empty to allow all entities unless specifically excluded.
  • Exclude Entity Keywords - Entities matching these keywords will never trigger combat block, overriding included keywords. Checks occur against both prefab and type names (partial, case-insensitive). For example, you might add ZombieNPC (type name from the Zombie Horde plugin) to exclude only zombies spawned by that plugin, while still allowing other npcs like scientists to trigger the block.
  • Allowed Damage Types - Only these damage types trigger combat blocks. Useful to exclude certain damage types like radiation or fall damage.
  • Ignored Weapon Prefabs - Weapon prefab names listed here will never trigger combat blocks.
  • Blocked Commands - Players cannot use these listed commands while combat-blocked.
  • Disallowed Actions - Specific in-game actions (crafting, building, healing, etc.) that players can't do during combat blocks.

Raid Block

Settings controlling when players become blocked during raids (when damaging buildings, doors, etc.).
JSON:
  "Raid Block": {
    "Enabled": true,
    "Block Duration Seconds": 300.0,
    "Only Block If Entity Health Below Percent (0-100)": 0,
    "Only Block If Entity Has Owner": true,
    "Ignore If Attacker Farther Than (metres)": 10.0,
    "Include Entity Keywords (prefab or type name substring)": [
      "building",
      "door"
    ],
    "Exclude Entity Keywords (prefab or type name substring)": [
      "ladder"
    ],
    "Allowed Damage Types": [
      "Explosion",
      "Blunt"
    ],
    "Ignored Weapon Prefabs": [],
    "Block Nearby Players Within Distance (only used if raid zone is disabled)": 30.0,
    "Relations To Block Near Attacker (ignored if raid zone is enabled)": [
      "Owner",
      "Teammate",
      "Auth"
    ],
    "Blocked Commands": [
      "tp"
    ],
    "Disallowed Actions": [
      "NoCraft",
      "NoBuild",
      "NoItemDrop",
      "NoRepair",
      "NoUpgrade",
      "NoRecycle",
      "NoVending",
      "NoKit",
      "NoTeleport",
      "NoTrade",
      "NoBackpack",
      "NoHeal",
      "NoStash",
      "NoMount",
      "NoItemDeploy",
      "NoAuth",
      "NoDeauth",
      "NoItemPickup",
      "NoBank"
    ]
  },
  • Enabled - Toggle raid blocking on/off entirely.
  • Block Duration Seconds - How long players stay blocked after starting a raid.
  • Only Block If Entity Health Below Percent - Players become blocked only if the attacked structure's remaining health drops below this percent after damage. Set to 0 to always trigger blocking regardless of remaining health.
  • Only Block If Entity Has Owner - Blocks attackers only when they damage player-owned structures. Prevents unnecessary blocks from attacking random objects like wooden barricades covering doorways at monuments or barrels scattered around the map.
  • Ignore If Attacker Farther Than - Players further away than this distance won't trigger raid blocks.
  • Include Entity Keywords - Keywords used to specify which entities trigger the raid block when damaged. The plugin checks if either the prefab name or the entity type name contains any of these keywords (partial matches allowed, case-insensitive). For example, adding door would include all door-related prefabs, and adding BuildingBlock (type name) would include all structural building elements. Leave empty to allow all entities unless specifically excluded.
  • Exclude Entity Keywords - Entities matching these keywords will never trigger a raid block, overriding included keywords. Checks occur against both prefab and type names (partial, case-insensitive). For example, you might add ladder to exclude ladders from triggering the raid block, even if other building entities like walls and doors still trigger it.
  • Allowed Damage Types - Raid blocks trigger only with these damage types (typically explosions or blunt).
  • Ignored Weapon Prefabs - Specific weapons or explosives here never trigger raid blocks.
  • Block Nearby Players Within Distance - If raid zones aren't enabled, nearby players within this distance also get raid blocked. Set high to catch everyone nearby or low to minimize collateral blocking.
  • Relations To Block Near Attacker -
  • Defines player relationships to apply raid blocks to when a raid is triggered. Ignored entirely if you use raid zones, since zones automatically block all players within them.
    • Owner - Player who owns the damaged structure.
    • Teammate - Players on the same Rust team as the attacker or owner.
    • Friend - Players listed as friends via the Friends plugin.
    • Clanmate - Players in the same clan (requires Clans plugin).
    • ClanAlly - Players in allied clans (requires Clans plugin).
    • Auth - Players authorized on the targeted building's tool cupboards.
  • Raid Zone - Creates a physical area using the Zone Manager plugin, automatically raid-blocking all players within the zone.

Raid Zone

Settings for creating a special zone during raids to automatically block all players inside. Requires the Zone Manager plugin.
JSON:
    "Raid Zone (blocks all players in zone, ignores relations)": {
      "Create Zone": true,
      "Zone Radius": 40.0,
      "Zone Flags": {
        "nobuild": "true",
        "nodeploy": "true",
        "noplayerloot": "true"
      },
      "Dome Stack (set to 0 to disable)": 1,
      "Dome Color (0-standard, 1-red, 2-blue, 3-green, 4-purple)": 0
    },
  • Create Zone - Automatically creates a raid-blocking zone at the raid location, instantly blocking all players inside. Requires the Zone Manager plugin to work.
  • Zone Radius - Determines how large the created raid zone will be.
  • Zone Flags - Adds specific zone flags to the raid zone (e.g., nobuild, nodeploy, noplayerloot). For a complete list of available flags, see the Zone Manager documentation.
  • Dome Stack - Sets the visual dome height for the raid zone, providing a clear visual indicator of its boundaries. Requires the Zone Domes plugin. Set this to 0 to disable the dome completely.
  • Dome Color- Chooses the dome's color for easy visual distinction:
    • 0 - Standard (default)
    • 1 - Red
    • 2 - Blue
    • 3 - Green
    • 4 - Purple

Unblock Conditions

Conditions that immediately end any active combat or raid block timers.
JSON:
  "Unblock When": {
    "Unblock When Player Dies": true,
    "Unblock When Player Respawns": true,
    "Unblock When Player Respawns At Bag": false,
    "Unblock When Player Disconnects": true
  },
  • Unblock When Player Dies - Clears block immediately upon player death.
  • Unblock When Player Respawns - Clears blocks after normal respawn.
  • Unblock When Player Respawns At Bag - Optionally clear blocks specifically when respawning at sleeping bags/beds.
  • Unblock When Player Disconnects - Clears blocks automatically when a player disconnects.

Permission Profiles

Lets you create specific permissions that grant tailored blocking rules, allowing some players fewer restrictions compared to regular users.
JSON:
 "Permission Profiles": [
    {
      "Permission Suffix": "vip",
      "Blocked Commands": [
        "tp"
      ],
      "Disallowed Actions": [
        "NoBuild",
        "NoUpgrade"
      ]
    }
  ],
  • Permission Suffix - Name suffix used to generate permissions like betternoescape.vip. Players/groups with this permission follow the rules specified below instead of default block rules.
  • Blocked Commands - Commands restricted specifically for players/groups with this permission during blocks.
  • Disallowed Actions - Actions specifically blocked for these permissions, allowing you to give select players fewer or different restrictions compared to normal players.

Hud Notifications

Controls the appearance of the HUD notifications players see while blocked, including color, positioning, text labels, and icons.
JSON:
 "UI": {
    "Combat HUD": {
      "Background Color (RGBA)": "0.950 0.490 0.000 0.670",
      "Icon Color (RGBA)": "0.950 0.490 0.000 0.670",
      "Font Color (RGBA)": "0.989 0.922 0.910 1",
      "Icon Path": "assets/icons/target.png",
      "Title Text": "Combat Block",
      "Anchor Min": "1 0.5",
      "Anchor Max": "1 0.5",
      "Offset Min": "-176 -109.3333",
      "Offset Max": "-16 -82.6667"
    },
    "Raid HUD": {
      "Background Color (RGBA)": "0.950 0.000 0.020 0.670",
      "Icon Color (RGBA)": "0.950 0.000 0.020 0.670",
      "Font Color (RGBA)": "0.989 0.922 0.910 1",
      "Icon Path": "assets/icons/explosion.png",
      "Title Text": "Raid Block",
      "Anchor Min": "1 0.5",
      "Anchor Max": "1 0.5",
      "Offset Min": "-176 -79.3333",
      "Offset Max": "-16 -52.6667"
    },
    "Font": "RobotoCondensed-Bold.ttf"
  }
  • Font - The font file used for the ui. You can use other Rust font files, such as robotocondensed-regular.ttf.
  • Combat HUD and Raid HUD- Each has separate controls for appearance:
    • Background Color - Background panel color, specified as an RGBA value.
    • Icon Color - Color applied to the icon image, specified as an RGBA value.
    • Font Color - Color of the displayed text, specified as an RGBA value.
    • Icon Path - Path to the displayed icon image. You can find alternate icon paths here.
    • Title Text - Text label displayed to players when they're combat- or raid-blocked.
    • Anchor Min and Anchor Max - Screen anchor positions controlling overall ui placement.
    • Offset Min and Offset Max - Pixel offsets adjusting ui element size and exact positioning relative to anchors.

Blocked Actions

These rules define player actions that can be blocked during combat or raid blocks. If an action is included in the configured block, players can't perform that action while blocked:
  • NoCraft - Players can't craft items.
  • NoBuild - Prevents building structures (walls, foundations, etc.).
  • NoItemDrop - Players can't drop items on the ground.
  • NoRepair - Disables the repairing of damaged structures or items.
  • NoUpgrade - Players can't upgrade building blocks (wood to stone, etc.).
  • NoRecycle - Blocks players from using recyclers.
  • NoVending - Stops players from accessing vending machines.
  • NoKit - Prevents players from redeeming kits.
  • NoTeleport - Disables teleportation commands.
  • NoTrade - Blocks trading between players.
  • NoBackpack - Prevents players from opening backpacks.
  • NoHeal - Blocks using medical or healing items.
  • NoStash - Stops players from hiding stashes.
  • NoMount - Prevents players from mounting vehicles or animals.
  • NoItemDeploy - Blocks deploying placeable items (boxes, bags, etc.).
  • NoAuth - Stops players from authorizing on tool cupboards.
  • NoDeauth - Stops players from deauthorizing from tool cupboards.
  • NoItemPickup - Prevents picking up dropped items or deployables.
  • NoBank - Blocks access to banking or currency storage plugins.

Developer API

C#:
bool API_IsCombatBlocked(BasePlayer player)
Checks if the player is currently in a combat block state.
  • player - The player to check.
  • Returns true if the player is blocked due to combat, otherwise false.
C#:
bool API_IsRaidBlocked(BasePlayer player)
Checks if the player is currently in a raid block state.
  • player - The player to check.
  • Returns true if the player is blocked due to a raid, otherwise false.
Author
VisEntities
License duration
Unlimited
Price
14.99 USD
First release
Last update

Ratings

0.00 star(s) 0 reviews

Also by VisEntities

  • Lucky Barrel
    Lucky Barrel
    Place a storage barrel, and with a bit of luck, it might turn into a random loot barrel
  • Custom Helicopter Tiers 2
    Beta Custom Helicopter Tiers 2
    Replaces Rust's patrol helicopter with smarter, stronger, and fully customizable tiered helicopters
  • Forever Ripe
    Forever Ripe
    Stops plants from dying by keeping them in a ripe state all the time

Latest updates

  1. 1.1.0

    Added API methods API_IsCombatBlocked and API_IsRaidBlocked to let other plugins check if a...
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. 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