TagsBits

🛠️ Fixes Implemented

1. Core Fix — savePlayer() Completely Rewritten

The database save logic was redesigned to ensure safe and reliable SQLite operations under concurrent access.

✅ Introduced a ReentrantLock to guarantee serialized database access, allowing only one thread to interact with the connection at a time. ✅ Added an ensureConnection() method to automatically verify and re-establish the SQLite connection if it becomes invalid. ✅ Implemented getAutoCommit() checks before starting a new transaction to prevent nested transaction attempts. ✅ Added safe rollback() handling that only executes when autoCommit is disabled. ✅ Protected the restoration of the autoCommit state, including forced reconnection when critical failures occur. ✅ Configured PRAGMA busy_timeout = 5000 to reduce failures when the database is temporarily locked. 2. GUI-Related Fixes

Several compilation issues across GUI classes were resolved.

✅ Replaced ArrayList<Object> with ArrayList<Component> for item lore handling. ✅ Removed unnecessary (Object) casts from PersistentDataContainer.set() calls. 3. Clean Build Verification

The project was successfully rebuilt and validated.

✅ Compiled successfully against Paper 1.21.4. ✅ No compilation errors or warnings related to the reported issues. ✅ All required dependencies were correctly shaded and packaged, including SQLite and SLF4J. ✅ Result

The plugin now handles SQLite operations safely in multi-threaded environments, preventing transaction conflicts, improving connection resilience, and ensuring stable player data persistence without runtime transaction errors.