Skip to main content
← All Guides
Server Admin · 7 min read

How to Allow or Disallow TNT in Specific Regions

Configure TNT permissions per region on a Minecraft server: WorldGuard tnt flag, Multiverse per-world settings, Paper TNT entity limits, faction war zones, and event-specific TNT enabling.

TNT is one of those blocks that makes Minecraft interesting and makes server administration painful. Players love it for mining, PvP, map-making, and sheer entertainment. Griefers love it for exactly the same reasons. The solution is not to disable TNT everywhere, that kills legitimate gameplay, but to control precisely where it works and where it does not. This guide covers every method for region-based TNT control, from WorldGuard flags to faction plugins to event-specific overrides.

The default problem

In vanilla Minecraft, TNT works everywhere. A player can walk up to someone's build, place TNT, light it with flint and steel, and watch weeks of work disappear in seconds. Even on servers with build protection, TNT explosions can sometimes bypass claim boundaries depending on the protection plugin's configuration. Creepers add another dimension, their explosions are TNT-like and can be triggered by luring them into protected areas if mob-grief is not handled.

WorldGuard TNT flags

WorldGuard is the standard tool for region-based control on Paper/Spigot servers. The relevant flags for TNT are:

/rg flag spawn tnt deny
/rg flag spawn creeper-explosion deny
/rg flag spawn other-explosion deny

These three flags cover the main explosion types:

  • tnt, blocks TNT explosions (both player-placed and dispensed)
  • creeper-explosion, blocks creeper explosions specifically
  • other-explosion, blocks other explosion types (end crystals, beds in the nether, respawn anchors)

For a typical server, deny all three in the spawn region and leave them allowed elsewhere. You can apply these to the __global__ region to disable TNT server-wide, then allow it in specific regions:

/rg flag __global__ tnt deny
/rg flag pvp-arena tnt allow
/rg flag mining-world tnt allow

Region hierarchy matters: flags on a specific region override the __global__ region when a player is inside both. This lets you create a default-deny policy with targeted exceptions.

Per-world settings via Multiverse

If you run Multiverse, you can control TNT behavior per world using the mobGriefing gamerule and Multiverse's own settings:

/mvm set gamerule mobGriefing false world_creative

This prevents creeper explosions from destroying blocks in the creative world. Note that mobGriefing false also stops endermen from picking up blocks, villagers from farming, and other mob interactions, so it is a broader setting than just TNT.

For player-placed TNT specifically, Multiverse does not have a direct toggle. You need WorldGuard's tnt flag or a Paper configuration change in the per-world config.

Paper TNT entity limits

Paper exposes configuration options that limit TNT's impact without disabling it entirely:

# paper-world.yml
max-tnt-per-tick: 20

This limits how many TNT entities can detonate per tick. If a player lights 100 TNT blocks simultaneously, only 20 process per tick and the rest queue for subsequent ticks. The explosions still happen, but they spread over multiple ticks instead of freezing the server in a single massive calculation.

This is a performance safety net, not a grief prevention tool. The TNT still destroys blocks, it just does so without crashing the server. Combine it with WorldGuard region protection for actual grief prevention.

Creating a "war zone" where TNT works

Many servers want TNT enabled in specific PvP or raiding zones. The setup is straightforward with WorldGuard:

# Step 1: Deny TNT globally
/rg flag __global__ tnt deny
/rg flag __global__ creeper-explosion deny

# Step 2: Define the war zone
/rg define warzone

# Step 3: Allow TNT in the war zone
/rg flag warzone tnt allow
/rg flag warzone pvp allow
/rg flag warzone creeper-explosion allow

Players in the war zone can use TNT freely. The moment they step outside it, TNT stops working. This is ideal for servers that want controlled PvP with destructive elements, the war zone is where you go to fight, and everywhere else is safe.

Consider adding visual boundaries: a bedrock wall, a particle effect border, or signs warning players they are entering the war zone. There is nothing worse than a player accidentally wandering into a TNT-enabled area and losing their inventory.

Factions and faction-based TNT rules

Faction plugins like Factions or FactionsUUID have their own explosion rules that operate alongside WorldGuard:

  • Faction territory, by default, TNT is disabled in claimed faction land. Enemies cannot TNT-raid a faction base unless the faction's power drops below their land claim count (making some claims "unprotected").
  • Warzone, faction warzone areas typically allow TNT. This is separate from WorldGuard's war zone concept.
  • Wilderness, unclaimed land usually allows TNT by default, but this is configurable.
  • Raiding mechanics, some faction configs allow TNT in enemy territory only during declared wars or when the defending faction is "raidable" (low power). This creates a strategic layer where TNT is a weapon of war, not casual griefing.

If you run Factions alongside WorldGuard, make sure their TNT settings do not conflict. WorldGuard's deny takes priority in most plugin load orders, so a region with tnt deny will block TNT even if faction rules allow it.

Event-specific TNT

Some servers enable TNT only during scheduled events, raids, demolition derbies, or siege battles. The cleanest approach is a temporary WorldGuard flag change managed by a command block or a scheduled plugin:

# Enable TNT for the event
/rg flag event-arena tnt allow

# After the event ends
/rg flag event-arena tnt deny

Automate this with a scheduler plugin that runs the commands at specific times, or tie it to a manual staff command. For more complex events, a small custom plugin or datapack can listen for specific triggers (all players in the arena, a lever pulled, a countdown finished) before enabling TNT.

Preventing creeper grief without disabling TNT

Players often conflate TNT control with creeper control. They are separate issues. You can allow player-placed TNT while preventing creeper explosions from damaging blocks:

/gamerule mobGriefing false

This stops creeper explosions from breaking blocks (creepers still explode and deal damage to players, they just do not destroy terrain). It also affects other mob interactions, so test the side effects. Alternatively, use WorldGuard's creeper-explosion deny flag in specific regions for more precision.

For a comprehensive breakdown of all redstone and mechanical grief prevention, including redstone-powered traps and per-world redstone controls, see our related guides.

Summary of TNT control methods

MethodScopeControls player TNTControls mob explosions
WorldGuard tnt flagPer-regionYesNo (separate flag)
WorldGuard creeper-explosionPer-regionNoYes (creepers only)
mobGriefing gamerulePer-worldNoYes (all mobs)
Paper max-tnt-per-tickPer-worldRate limits onlyNo
Factions pluginPer-faction claimYesDepends on config
PlotSquared explosion flagPer-plotYesYes

Layer these methods to match your server's needs. A typical SMP setup: WorldGuard tnt deny and creeper-explosion deny in spawn, allowed everywhere else, with mobGriefing false as a global safety net and max-tnt-per-tick: 20 as a performance backstop. For servers that need keepInventory in TNT zones, combine the region flags with per-world gamerules for a polished experience.

Need a server that handles this? Astroworld Hosting runs NVMe SSD, Pterodactyl panel, and DDoS protection. See features , plans from €6.39/mo.

Related Tools & Resources

🔧

Minecraft Tools

Calculators, generators & server tools

🧱

Item Database

Browse all Minecraft items, stats & recipes

⚒️

Crafting Recipes

Visual crafting guides for every recipe