TrialChamberPro icon

TrialChamberPro -----

Trial Chamber Management Plugin



TrialChamberPro-1.1.6
1.1.6 - 2025-11-20
Added
  • Added "Locked: X Normal, X Ominous" display to /tcp menu chamber tooltips showing per-player locked vault counts
  • Added vault-locked message for permanent vault locks (distinct from time-based cooldowns)
  • Added in-memory lock to prevent vault spam-clicking race condition (5-second window per player-vault)
  • Added getLockedVaultCounts() function to query locked vaults per player per chamber
Fixed
  • CRITICAL: Fixed Dispatchers.Main error when opening vaults - now uses Bukkit scheduler instead of non-existent Android Main dispatcher
  • CRITICAL: Fixed vault statistics never being recorded - incrementVaultsOpened() now called when opening vaults
  • CRITICAL: Fixed database connection pool exhaustion causing 60s timeouts:
    • Increased SQLite connection pool from 1 to 5 (WAL mode supports concurrent readers)
    • Reduced connection timeout from 60s to 30s (fail faster)
    • Added SQLite busy_timeout=5000 for better lock handling
    • Added leak detection threshold (10s) to identify connection leaks
    • Staggered vault count refreshes in menu to prevent connection stampede
  • Fixed UPSERT race condition in recordOpen() - now uses atomic SQL INSERT ... ON CONFLICT DO UPDATE
  • Fixed vault spam-clicking allowing multiple opens before database write completed
  • Removed all references to deprecated /tcp add command from help, docs, and tab completion
Changed
  • BREAKING: Changed default vault cooldown from 24/48 hours to -1 (permanent lock, vanilla behavior)
    • Set normal-cooldown-hours: -1 (permanent until chamber reset)
    • Set ominous-cooldown-hours: -1 (permanent until chamber reset)
    • Set reset-vault-cooldowns: true by default (required for vanilla behavior)
    • Cooldown can still be customized to time-based (e.g., 24 = 24 hours)
  • Updated canOpenVault() to interpret negative cooldown as permanent lock
  • Vault opening now shows different messages for permanent lock vs time-based cooldown
  • Replaced /tcp add with /tcp generate wand in all documentation and examples
Internal
  • Database schema changes: None (backwards compatible)
  • Config changes: Default cooldown values changed from 24/48 to -1
  • Permission tcp.bypass.cooldown now properly documented as separate from tcp.admin.*
Migration Notes
  • Existing vaults opened with old cooldowns will now be permanently locked
  • Run /tcp reset <chamber> to unlock all vaults in a chamber
  • Admins: explicitly deny tcp.bypass.cooldown permission if you want to test locking behavior
----------, Today at 7:44 AM
Resource Information
Author:
----------
Total Downloads: 91
First Release: Oct 24, 2025
Last Update: Today at 7:44 AM
Category: ---------------
All-Time Rating:
1 ratings
Find more info at darkstarworks.gitbook.io...
Version -----
Released: --------------------
Downloads: ------
Version Rating:
----------------------
-- ratings