TrialChamberPro

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

1.5.4 - 2026-06-09

Fixed

• Spawner glow outline never rendered (v1.2.27 regression). The opt-in spawner-waves.glow-active-spawners feature spawned an Interaction entity at each active spawner and set its isGlowing flag — but Interaction entities are explicitly immune to the Glowing effect (no renderable model for the outline pass), so the feature silently rendered nothing on every client since v1.2.27. Swap to an invisible Shulker: shell-cube hidden by INVISIBILITY, glow outline remains, perfect 1×1×1 cube marker through walls. Inert mob (no AI, silent, non-persistent), PDC-tagged so mob-cap / anti-cheat plugins can identify the overlay and skip it from monster counts.

Added

• ChamberEnteredEvent / ChamberExitedEvent — public Bukkit events for "player crossed into/out of a registered chamber." Fired from PlayerMovementListener on the block-boundary-crossing transition, and from PlayerQuitEvent for any player who disconnects while inside (keeping entry/exit pairs balanced for downstream listeners that allocate per-player state on entry). Both fire un-gated by the statistics.* config flags — listeners that need chamber-presence signals shouldn't have their behaviour silently disabled by the admin's stats preferences. Direct chamber→chamber transitions fire an exit-then-entry pair (with entry/exit messages suppressed on the transition to avoid spam). Primary intended consumer: the TCP-MythicTrials HUD; useful for any plugin reacting to chamber presence (welcome messages, region effects, etc.).
• spawner-waves.glow-mode (default wave-active). New chamber-remaining mode lights up every uncleared spawner in a chamber when any wave starts inside it, not just the wave-active one — solves "which spawner did I miss?" navigation on large chambers. Standalone glow entities are tracked per chamber, cleaned up on each spawner's wave completion and on chamber reset. Recommended for premium difficulty modules (TCP-MythicTrials's HUD pairs with this).

[1.5.3] - UNRELEASED

Fixed

• Update checker mis-parsed -mc26 release tags. fetchLatestVersion() only stripped a leading v, so a releases/latest tag of v1.5.2-mc26 became 1.5.2-mc26 and isNewerVersion() parsed the third segment (2-mc26) as 0 — i.e. 1.5.0 — producing wrong update results whenever the most recently published release was an mc26 tag. It now also strips the track suffix (.substringBefore('-')) so both vX.Y.Z and vX.Y.Z-mc26 collapse to the same X.Y.Z before comparison.