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

1.8.1 - 2026-07-10

Added

• World exclusion. New global.excluded-worlds list in config.yml keeps TCP inactive in named worlds — useful when a second overworld-type world has Trial Chambers you want to leave vanilla. In an excluded world, auto-discovery never registers chambers, /tcp generate and /tcp dungeon generate are refused, and wild trial spawners get no boss bars or wave tracking. Chambers registered before a world was excluded keep working; remove them with /tcp delete <name>.

Changed

• Updated the bundled PluginPulse updater to v0.8.0 (configurable source order, authenticated private-repo updates, Jenkins update source).

1.8.1 - 2026-07-10

Added

• World exclusion. New global.excluded-worlds list in config.yml keeps TCP inactive in named worlds — useful when a second overworld-type world has Trial Chambers you want to leave vanilla. In an excluded world, auto-discovery never registers chambers, /tcp generate and /tcp dungeon generate are refused, and wild trial spawners get no boss bars or wave tracking. Chambers registered before a world was excluded keep working; remove them with /tcp delete <name>.

Changed

• Updated the bundled PluginPulse updater to v0.8.0 (configurable source order, authenticated private-repo updates, Jenkins update source).

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

1.8.0 - 2026-07-05

Added

• Built-in updater with one-command installs. The old notify-only update check is replaced by PluginPulse: updates are now checked on Modrinth first (GitHub Releases as fallback), and a new /tcp update command lets admins act on them — check, download (fetches the new jar, verifies its checksum, backs up the current jar, and stages it in the server's update folder so it installs on the next restart), restore (roll back to the previous jar), ignore <version>, and status. Behaviour is controlled by the new update section in config.yml: mode (check-only / notify / download / auto-stage), check-interval-hours, and require-hash. Servers running the -mc26 build automatically follow -mc26 releases. Nothing is ever downloaded in the default notify mode.

• Optional no-restart updates. With update.allow-hot-reload: true, /tcp update apply swaps a staged, checksum-verified update in-place — the old version is unloaded, the jar replaced, and the new version enabled live (verified end-to-end on Paper 1.21.7). Refused on Folia and while other plugins depend on TCP; if the new version fails to load, TCP rolls back to the automatic backup. Off by default — restarting remains the recommended way to apply updates.

• (if you don't use any of the premium modules, you are safe to use allow-hot-reload: true -> /tcp update apply)

Changed

• Update checks are rate-limit friendly: check state persists across restarts in plugins/TrialChamberPro/pluginpulse/, and fleet servers no longer check in lockstep at startup.

1.8.0 - 2026-07-05

Added

• Built-in updater with one-command installs. The old notify-only update check is replaced by PluginPulse: updates are now checked on Modrinth first (GitHub Releases as fallback), and a new /tcp update command lets admins act on them — check, download (fetches the new jar, verifies its checksum, backs up the current jar, and stages it in the server's update folder so it installs on the next restart), restore (roll back to the previous jar), ignore <version>, and status. Behaviour is controlled by the new update section in config.yml: mode (check-only / notify / download / auto-stage), check-interval-hours, and require-hash. Servers running the -mc26 build automatically follow -mc26 releases. Nothing is ever downloaded in the default notify mode.

• Optional no-restart updates. With update.allow-hot-reload: true, /tcp update apply swaps a staged, checksum-verified update in-place — the old version is unloaded, the jar replaced, and the new version enabled live (verified end-to-end on Paper 1.21.7). Refused on Folia and while other plugins depend on TCP; if the new version fails to load, TCP rolls back to the automatic backup. Off by default — restarting remains the recommended way to apply updates.

• (if you don't use any of the premium modules, you are safe to use allow-hot-reload: true -> /tcp update apply)

Changed

• Update checks are rate-limit friendly: check state persists across restarts in plugins/TrialChamberPro/pluginpulse/, and fleet servers no longer check in lockstep at startup.

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

1.7.3 - 2026-07-04

Fixed

• Spawner-wave counter can no longer be stalled by a dead entity when a custom-mob provider fails mid-replacement. In both the chamber replace-after-spawn path and the wild-spawner resolver path, a provider that threw after the vanilla mob was removed caused the already-removed entity to be recorded into the wave — the counter then hung until the periodic sweep caught it. A failure after removal now records nothing (the wave undercounts that one spawn and completes normally); only failures before removal fall back to vanilla tracking.

1.7.3 - 2026-07-04

Fixed

• Spawner-wave counter can no longer be stalled by a dead entity when a custom-mob provider fails mid-replacement. In both the chamber replace-after-spawn path and the wild-spawner resolver path, a provider that threw after the vanilla mob was removed caused the already-removed entity to be recorded into the wave — the counter then hung until the periodic sweep caught it. A failure after removal now records nothing (the wave undercounts that one spawn and completes normally); only failures before removal fall back to vanilla tracking.

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

1.7.2 - 2026-07-03

Fixed

• Chamber resets no longer erase decorations. Snapshots only knew how to capture four block types (spawners, vaults, pots, chests) — everything else restored as a blank block, so sign text, player-head skins, banner patterns, lectern books, jukebox discs, chiseled-bookshelf contents, and suspicious-block items were silently wiped on every reset. All of these are now captured and restored faithfully, in chamber snapshots AND in captured/imported dungeon rooms. Re-run /tcp snapshot create <chamber> on decorated chambers to capture them with the new fidelity.
• Opening a vault can no longer consume the wrong item. The key was taken from whatever the player was holding at the moment loot was delivered — scroll your hotbar in the split second after clicking and the plugin ate your sword instead of the key. The key is now consumed from the slot that held it at click time (or wherever the key stack actually is), and never from a non-key item.
• Logging out — or crashing — while spectating no longer strands you in spectator mode. Quitting mid-spectate now restores your gamemode and position immediately, and a server crash/restart mid-spectate is recovered on your next join (the restore data survives in your player file).
• Statistics no longer lose counts on shared MySQL databases. Increments were read-modify-write, so two servers writing at once could drop each other's updates; every counter now increments atomically in the database — groundwork for cross-server networks.
• Key-to-reopen can't burn keys on a broken loot table. With reopen-cost-keys of 2+, a missing/typo'd loot table used to take part of the payment and give nothing; the table is now validated before any keys are consumed.
• Vault loot ejection (drop-loot-at-vault) now drops items on the vault's own region thread — fixes a potential cross-region error on Folia when the opener moved away during the open.
• Deleting a chamber now clears its wave-tracking state (active boss bars, clear-cycle progress, spawner caches) instead of leaving stale entries behind.
• /tcp generate fallback volume limit aligned with the rest of the plugin (750,000 — was 500,000 in one code path when the config key is absent).
• Explosions from outside a chamber can no longer destroy blocks inside it. The explosion filter only protected blocks when the blast center was inside a chamber — a creeper or TNT detonating just outside the wall blew chamber blocks up unprotected. Protection is now checked per affected block, and block-sourced explosions (beds/respawn anchors in the wrong dimension) — which previously bypassed chamber protection entirely — are covered too.
• Pausing a chamber now actually stops a reset that's already counting down. A chamber paused mid-countdown still reset when the timer fired, and its "resets in 30 seconds!" warnings kept broadcasting; pause (and deletion) now cancel the scheduled reset, its warnings, and any parked confirmation.
• Per-player container copies are saved if the server stops while a player has one open — previously the shutdown could discard the pending save, losing whatever they'd taken out or left in.
• Teleporting across a chamber boundary now counts as entering/leaving. Teleports don't fire movement events, so /tp, /home, ender pearls — and the reset eviction itself — left stale "in chamber" tracking (time kept accruing, exit never fired). Logging out inside a chamber and back in also registers the entry immediately now.
• Chamber names are no longer suggested in tab-completion to players without admin permission (they became visible to everyone when 1.7.1 opened /tcp for stats/leaderboard).
• The post-reset event now reports the real number of restored blocks instead of the chamber's full volume.

1.7.2 - 2026-07-03

Fixed

• Chamber resets no longer erase decorations. Snapshots only knew how to capture four block types (spawners, vaults, pots, chests) — everything else restored as a blank block, so sign text, player-head skins, banner patterns, lectern books, jukebox discs, chiseled-bookshelf contents, and suspicious-block items were silently wiped on every reset. All of these are now captured and restored faithfully, in chamber snapshots AND in captured/imported dungeon rooms. Re-run /tcp snapshot create <chamber> on decorated chambers to capture them with the new fidelity.
• Opening a vault can no longer consume the wrong item. The key was taken from whatever the player was holding at the moment loot was delivered — scroll your hotbar in the split second after clicking and the plugin ate your sword instead of the key. The key is now consumed from the slot that held it at click time (or wherever the key stack actually is), and never from a non-key item.
• Logging out — or crashing — while spectating no longer strands you in spectator mode. Quitting mid-spectate now restores your gamemode and position immediately, and a server crash/restart mid-spectate is recovered on your next join (the restore data survives in your player file).
• Statistics no longer lose counts on shared MySQL databases. Increments were read-modify-write, so two servers writing at once could drop each other's updates; every counter now increments atomically in the database — groundwork for cross-server networks.
• Key-to-reopen can't burn keys on a broken loot table. With reopen-cost-keys of 2+, a missing/typo'd loot table used to take part of the payment and give nothing; the table is now validated before any keys are consumed.
• Vault loot ejection (drop-loot-at-vault) now drops items on the vault's own region thread — fixes a potential cross-region error on Folia when the opener moved away during the open.
• Deleting a chamber now clears its wave-tracking state (active boss bars, clear-cycle progress, spawner caches) instead of leaving stale entries behind.
• /tcp generate fallback volume limit aligned with the rest of the plugin (750,000 — was 500,000 in one code path when the config key is absent).
• Explosions from outside a chamber can no longer destroy blocks inside it. The explosion filter only protected blocks when the blast center was inside a chamber — a creeper or TNT detonating just outside the wall blew chamber blocks up unprotected. Protection is now checked per affected block, and block-sourced explosions (beds/respawn anchors in the wrong dimension) — which previously bypassed chamber protection entirely — are covered too.
• Pausing a chamber now actually stops a reset that's already counting down. A chamber paused mid-countdown still reset when the timer fired, and its "resets in 30 seconds!" warnings kept broadcasting; pause (and deletion) now cancel the scheduled reset, its warnings, and any parked confirmation.
• Per-player container copies are saved if the server stops while a player has one open — previously the shutdown could discard the pending save, losing whatever they'd taken out or left in.
• Teleporting across a chamber boundary now counts as entering/leaving. Teleports don't fire movement events, so /tp, /home, ender pearls — and the reset eviction itself — left stale "in chamber" tracking (time kept accruing, exit never fired). Logging out inside a chamber and back in also registers the entry immediately now.
• Chamber names are no longer suggested in tab-completion to players without admin permission (they became visible to everyone when 1.7.1 opened /tcp for stats/leaderboard).
• The post-reset event now reports the real number of restored blocks instead of the chamber's full volume.