TrialChamberPro

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

1.5.1 - 2026-05-27

Added

• Per-chamber spawner cooldown can now match the chamber's reset interval. New cycle option in ChamberSettingsView's spawner-cooldown toggle: Match Chamber Reset. At reset time, each trial spawner in the chamber is stamped with cooldownLength = chamber.resetInterval, so the spawner naturally rearms right as the chamber resets. Stored as the sentinel value -2 on chambers.spawner_cooldown_minutes; existing per-chamber values, the null = global config default, and the -1 = vanilla 30m / 0 = immediate modes are unchanged.
• Legacy loot audit (/tcp loot audit + startup warning + GUI badge). Pre-1.5.0 loot entries were stored as material + amount only — so an "enchanted book" row added before the v1.5.0 faithful-loot fix still drops as a plain book (no migration is possible because the enchant data was never persisted). Three new touchpoints surface this without reading the user's mind: (a) at startup, a single warning line counts entries whose structured fields can't produce the intended item (enchanted book without enchants, potion/tipped arrow without potion type, goat horn without instrument) and points at the audit command; (b) /tcp loot audit lists them grouped by table / pool with the row kind/index/material/reason, capped at 50 rows; (c) LootEditorView decorates each legacy row with a ⚠ Legacy entry — re-add to capture NBT lore line so it's obvious which to re-enter. Plain 10 cobblestone-style entries are deliberately not flagged.
• Snapshot reminder for snapshotless discovered chambers. Auto-discovered chambers can sit in the DB without a snapshot, in which case they silently can't be reset. New SnapshotReminderService pings admins with tcp.admin.snapshot (a) once on login if any chamber lacks a snapshot, and (b) periodically as a coalesced console + admin-chat summary. Configurable under discovery.snapshot-reminder.* (enabled, on-join, interval-minutes). Defaults: on, 30 min interval.

Changed

• Pending-reset console output coalesced. With global.reset-require-confirmation enabled, the per-chamber is due for reset — awaiting confirmation log line is replaced by a single per-tick summary (N chamber(s) due for reset — M total awaiting confirmation. Use /tcp reset pending to list, /tcp reset confirm all to release.). The in-game clickable [confirm] [list all] ping for admins is unchanged.
• Default vault cooldowns are now 0 instead of -1. vaults.normal-cooldown-hours and vaults.ominous-cooldown-hours ship at 0 (vanilla behaviour — locked until chamber reset). The old -1 default was being clamped to 0 by the config validator and producing a startup warning on every fresh install; the value and the comment now reflect what actually happens.