MassExtinction

<div align="center"> # ⛏️ MassExtinction ### *"Minecraft, But Breaking a Block Breaks Them All."* <img src="https://img.shields.io/badge/Minecraft-1.20+-62B47A?style=for-the-badge&logo=minecraft&logoColor=white" alt="Minecraft 1.20+"/> <img src="https://img.shields.io/badge/Platform-Spigot%20%7C%20Paper-orange?style=for-the-badge" alt="Spigot/Paper"/> <img src="https://img.shields.io/badge/Author-Pawan-blueviolet?style=for-the-badge" alt="Author: Pawan"/> <br> Break **one** block, and every identical block on the server shatters with it. Kill **one** mob, and its entire species goes extinct. Scoop **one** bucket of water, and every ocean vanishes. This is chaos, gamified. </div> --- ## 📖 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. <table> <tr> <td width="33%" valign="top"> ### 🧱 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. </td> <td width="33%" valign="top"> ### 💀 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. </td> <td width="33%" valign="top"> ### 🌊 Fluid Chain-Drain Scoop up water or lava with a bucket and **every source/flowing block of that fluid** disappears from loaded chunks. </td> </tr> </table> --- ## ⚡ Performance First <blockquote> <b>Naively looping over every block in every chunk on the main thread will crash your server.</b> MassExtinction never does that. </blockquote> 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`. <table> <thead> <tr><th>Command</th><th>Description</th></tr> </thead> <tbody> <tr><td><code>/massextinction start</code></td><td>Turns the chain-reaction system <b>ON</b></td></tr> <tr><td><code>/massextinction stop</code></td><td>Turns it <b>OFF</b> — blocks/mobs/fluids behave normally</td></tr> <tr><td><code>/massextinction status</code></td><td>Shows whether it's currently active</td></tr> <tr><td><code>/massextinction reload</code></td><td>Reloads <code>config.yml</code> without restarting</td></tr> <tr><td><code>/massextinction version</code></td><td>Shows your version and checks for updates</td></tr> <tr><td><code>/massextinction update</code></td><td>Downloads the latest version from Modrinth (applies on next restart)</td></tr> </tbody> </table> **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: ```yaml # ========================================= # 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 -