MassExtinction

Minecraft 版本： 1.20 1.20.1 1.20.2 1.20.3 1.20.4 1.20.5 1.20.6 1.21 1.21.1 1.21.2 1.21.3 1.21.4 1.21.5 1.21.6 1.21.7 1.21.8 1.21.9 1.21.10 1.21.11 26.1 26.1.1 26.1.2 26.2

平台： bukkit paper purpur spigot

---

? What is MassExtinction?

MassExtinction is a chaos/challenge plugin built around a single rule:

Whatever happens to one block or mob, happens to all of them.

It's the "Minecraft, But..." YouTube challenge format, turned into a real server
plugin — built to run safely on live servers without freezing your main thread,
thanks to tick-batched, throttled processing under the hood.

### ? Block Chain-Break Break a block (or blow one up with TNT/Creepers) and **every block of that material** in loaded chunks breaks instantly, dropping normal loot.

### ? Mob Chain-Kill Kill a mob and **every loaded mob of that same type** dies too, with full loot drops — as if it died naturally.

### ? Fluid Chain-Drain Scoop up water or lava with a bucket and **every source/flowing block of that fluid** disappears from loaded chunks.

---

⚡ Performance First

Naively looping over every block in every chunk on the main thread will crash your server. MassExtinction never does that.

Instead, every chain reaction runs as a throttled, tick-batched task:

• ? Scan phase — walks a handful of loaded chunks per tick using lightweight chunk snapshots
• ? Break/Kill phase — processes a capped number of blocks/entities per tick
• ?️ Duplicate guards — the same material or mob type can't be chained twice at once (no runaway recursive loops)
• ? Tool-aware drops — breaks use the same tool you used originally, so Fortune/Silk Touch still work correctly across the whole chain

All of this is fully configurable — see Configuration below.

---

? Installation

1. Download the latest .jar from this page (or use /massextinction update — see Commands)
2. Drop it into your server's /plugins folder
3. Restart the server
4. Done — chain reactions are on by default. Break something and watch the world unravel.

Requires Spigot or Paper 1.20+. Java 17 or newer.

---

? Commands

All commands are under /massextinction, with aliases /me and /massext.

Command	Description
/massextinction start	Turns the chain-reaction system ON
/massextinction stop	Turns it OFF — blocks/mobs/fluids behave normally
/massextinction status	Shows whether it's currently active
/massextinction reload	Reloads config.yml without restarting
/massextinction version	Shows your version and checks for updates
/massextinction update	Downloads the latest version from Modrinth (applies on next restart)

Permission: massextinction.admin (default: op)

---

⚙️ Configuration

MassExtinction generates a config.yml in /plugins/MassExtinction/ on first run.
Every option is commented inline. Here's the full file with explanations:

# =========================================
#  MassExtinction Configuration
#  "Minecraft, But Breaking a Block Breaks Them All"
# =========================================

# Radius mode for scanning loaded chunks around the origin block.
#   "global"  -> scan ALL currently loaded chunks in the world.
#   <number>  -> only scan chunks within that many chunks of the origin (e.g. 15).
# Use a numeric radius on larger/busier servers to reduce lag.
scan-radius: "global"

# How many blocks to break per server tick during a chain reaction.
# Lower = safer for low-end servers. Higher = faster chains but more lag per tick.
blocks-per-tick: 200

# How many chunks to scan (search for matching blocks) per tick.
chunks-per-tick: 5

# How many entities to kill per tick during a mass entity elimination.
entities-per-tick: 50

# Materials that will NEVER be chain-broken (grief/world protection).
blacklisted-blocks:
  - BEDROCK
  - BARRIER
  - END_PORTAL_FRAME
  - END_PORTAL
  - END_GATEWAY
  - COMMAND_BLOCK
  - CHAIN_COMMAND_BLOCK
  - REPEATING_COMMAND_BLOCK
  - STRUCTURE_BLOCK
  - STRUCTURE_VOID
  - JIGSAW
  - SPAWNER
  - REINFORCED_DEEPSLATE

# Entity types that will NEVER be mass-killed (safety — never touch players!).
blacklisted-entities:
  - PLAYER
  - ARMOR_STAND

# Feature toggles — turn individual chain-reaction types on/off.
features:
  block-chain-break: true
  explosion-chain-break: true
  entity-chain-kill: true
  fluid-chain-drain: true

# Prints extra chain-reaction info to console. Useful for tuning blocks-per-tick /
# chunks-per-tick on your hardware.
debug: false

# Checks Modrinth once on startup for a newer version — purely informational,
# never auto-downloads anything on its own. Use /massextinction update for that.
check-for-updates: true

# Whether the chain-reaction system is switched ON immediately when the server
# starts. Set to false if you'd rather leave it dormant until an admin runs
# /massextinction start.
auto-start: true

? Config Reference

Key	Type	Default	What it does
scan-radius	string/number	"global"	Limit chain reactions to a chunk radius instead of the whole loaded world
blocks-per-tick	int	200	Break throttle — lower this if you see TPS drops
chunks-per-tick	int	5	Scan throttle — how many chunks get searched per tick
entities-per-tick	int	50	Mob-kill throttle per tick
blacklisted-blocks	list	see above	Materials immune to chain-breaking
blacklisted-entities	list	PLAYER, ARMOR_STAND	Entity types immune to chain-killing
features.*	bool	true	Toggle each chain-reaction type independently
debug	bool	false	Verbose console logging for tuning
check-for-updates	bool	true	Startup Modrinth version check
auto-start	bool	true	Whether chain reactions are active immediately on boot

---

? Example Configs

?️ Small/low-end server (safer, slower chains) ```yaml scan-radius: 10 blocks-per-tick: 40 chunks-per-tick: 2 entities-per-tick: 15 ``` ? Large/powerful server (fast, global chains) ```yaml scan-radius: "global" blocks-per-tick: 500 chunks-per-tick: 10 entities-per-tick: 100 ``` ? Event mode (off by default, admin starts it manually) ```yaml auto-start: false ``` Then during your event: `/massextinction start`. When it's over: `/massextinction stop`.

---

⚠️ Good to Know

• Explosions (TNT, Creepers) trigger the same chain reaction as manually breaking a block.
• Fluids don't drop items when chain-drained — only solid blocks drop loot.
• Command blocks, spawners, portals, and bedrock are blacklisted by default to protect world structures.
• /massextinction update stages the new jar in your plugins/update/ folder — you must restart the server to apply it.

---