Changelog

v2.9

Fixes

• Main-thread SQLite blocking during player quit - onPlaytimeQuit, onPlaytimeJoin, and login streak processing now run database operations asynchronously. This eliminates 15-40 second watchdog timeouts when SQLite write contention occurs on the main thread.
  • savePlaytimeFor() - now wraps setPlayerData() in runTaskAsynchronously
  • processStreak() - entire body runs async, UAA API calls dispatched to main thread via runTask
  • incrementStreakSync() / resetStreakSync() - DB writes async, in-memory cache updates stay fast
• Removed Thread.sleep(50) in PlayerDataListener.onPlayerQuit() - the 50ms main-thread block is eliminated; progress sync now uses runTaskAsynchronously
• Text support in placeholder conditions - checkPlaceholderCondition() now supports string comparisons (==, !=, contains) when the placeholder returns text instead of a number. Enables filtering triggers by day name (%localtime_time_E% == Fri), player name, biome, etc.
• Spigot compatibility for vanilla advancement display - Fixed ClassCastException on Spigot when reading vanilla advancement display data. Uses instanceof check with fallback to Bukkit API (getTitle(), getDescription(), getType()) when Paper API is unavailable. Affects vanilla webhooks and vanilla advancement loading in the editor.

Fixes - Web Editor

• Advancement disappearing after ID rename - Fixed _initTabIds() stale cache issue. After renaming an advancement ID (e.g. new_advancement → test), the non-reactive _idSets was never re-synced, causing subsequent operations to overwrite tab.advancementIds and drop renamed advancements from the sidebar.
• ID rename silently corrupting on duplicate - Renaming to an ID that already exists in another tab now shows a toast ID "x" already exists in tab "y" and safely reverts the ID instead of silently corrupting the advancement object.
• ID rename watch triggering on tab switches - The rename watcher no longer fires when switching tabs or creating new advancements, preventing false "ID already exists" toasts.
• Toast disappearing too fast - Fixed timer collision where a new toast inherited the remaining timeout of a previous toast, causing it to vanish almost instantly.
• Toast stacking - Multiple toasts now stack on top of each other with slide/fade transitions instead of replacing each other.