/
/tcp pause <name> or the new toggle in the Chamber Detail GUI. Pausing preserves the full DB record — no history, stats, or vault data is lost — but suspends all active behavior: automatic resets stop scheduling, protection events skip the chamber, vault interactions are blocked with a chamber-is-paused message, and player/mob tracking is silenced. Resume at any time with /tcp resume <name> or the GUI toggle.protection.auto-pause-on-destruction: false opt-in (disabled by default). When enabled, a MONITOR-priority break observer counts vault and trial spawner destructions inside a chamber; once the count reaches protection.auto-pause-threshold (default 6), the chamber auto-pauses and ops with tcp.discovery.notify permission are notified. Counter resets on every pause/resume transition and on chamber reset, so a resumed chamber always starts fresh.tcp.admin.pause (default op) — required to use /tcp pause and /tcp resume.protection.auto-pause-on-destruction (default false) — master switch for the automatic pause on critical-block destruction.protection.auto-pause-threshold (default 6) — how many combined vault + trial spawner destructions inside a chamber trigger the auto-pause. Minimum effective value is 1. A low value (1-2) catches individual mischief; the default (6) targets systematic demolition. Resets on every pause/resume cycle and on chamber reset.chamber-paused, chamber-resumed, chamber-already-paused, chamber-not-paused, chamber-is-paused, chamber-auto-paused (with {chamber}, {block}, {count} placeholders), info-paused, help-pause, help-resume, usage-pause, usage-resume.gui.chamber-detail: pause-toggle-name, pause-toggle-lore-active, pause-toggle-lore-paused.
Because Trial Chambers deserve better than being a "one and done" dungeon.