TrialChamberPro

This plugin version is compatible with Minecraft 26.X.X

[1.7.0] - 2026-07-02

Added

• Tunnel-breaking: let players mine INTO a walled chamber — without letting them farm it. Properly-generated Trial Chambers have no entrance; with block-break protection on, players were locked out entirely, and with it off they could strip-mine the (endlessly restored) tuff for infinite blocks. The new opt-in protection.tunnel-breaking mode allows breaking a configurable block set (default: the tuff-brick shell family) inside registered chambers with drops always suppressed — no items, no XP — so there's nothing to farm, and the tunnel heals on the next reset. An optional shell-depth (default 3) restricts digging to the outer wall so the interior can't be hollowed out; players digging too deep get a clear "outer wall only" message (tunnel-only-outer-wall in messages.yml). Everything else stays protected.
• Import datapack rooms into the dungeon engine: /tcp dungeon import <file|folder|zip> [tags…]. Vanilla .nbt structure templates — the format "crazy chambers"-style datapacks use for their custom rooms — can now be imported straight into TCP's procedural dungeon system. Drop a loose .nbt, a folder of them, or a whole datapack .zip into plugins/TrialChamberPro/dungeon/import/ and import; zip imports pick up every data/<namespace>/structure/**/*.nbt entry and auto-tag rooms by their folder (e.g. spawner, large). Jigsaw blocks in the templates become door connectors exactly as with in-world capture, and generated dungeons register as normal chambers (resets, loot, protection all apply). Limits: rooms import literally (worldgen processor randomizers aren't applied), only the first palette is read, and vertical jigsaw connectors become walls.
• Auto-discovery now understands datapack-enlarged chambers. When a naturally-generated Trial Chamber is found, discovery now asks the game for the structure's exact bounds (discovery.use-structure-bounds, default on) instead of flood-scanning blocks — so chambers enlarged by datapacks that override the vanilla layout with custom rooms register at their full, correct size in one pass (no clipping, no fragments), and bounds are marked confirmed immediately. Player-built chambers still discover via the block scan. A separate discovery.structure-max-volume cap (default 15,000,000; -1 = uncapped) applies to these, since datapack chambers can be much larger than vanilla ones.

Changed

• Chamber scanning, snapshot capture and spawner resets are now batched across ticks. These three operations used to walk the chamber's entire volume in a single tick — fine at vanilla sizes, but a freeze risk for the much larger chambers this release enables (structure-bounds discoveries and imported dungeons can run to millions of blocks). Each now processes ~100k blocks per scheduled task, so even a 15-million-block chamber scans smoothly in the background; small chambers behave exactly as before. Spawner resets also swap their old whole-scan 10-second timeout for a per-batch one, so huge chambers can't time out halfway. Note that block restoration speed is still governed by global.blocks-per-tick — for very large chambers, raise it or enable global.use-fawe.
• All TCP database tables are now prefixed (tcp_chambers, tcp_vaults, …) and the prefix is configurable. TCP's generic table names (chambers, vaults, spawners, …) could collide with other plugins on a shared MySQL database. New database.table-prefix setting (default tcp_, letters/digits/underscore, max 16 chars). Existing installs migrate automatically on first start: legacy unprefixed tables are safely renamed (only when their columns unmistakably match TCP's schema — a same-named table belonging to another plugin is left alone and reported), foreign keys and data are preserved, and the migration is a no-op on every later start. No action needed; change the prefix only if you have a collision.