vJourney

v1.3.1

• Fix: Advancement-screen protection now intercepts delayed vJourney advancement packets that were already queued by UltimateAdvancementAPI, preventing frequent trigger checks from closing the open advancements screen.
• Compatibility: The delayed-packet guard works through PacketEvents or ProtocolLib and only defers vJourney advancement updates until the player closes the screen.
• Fix: Player data can no longer be wiped when a periodic or quit save runs before the asynchronous load finishes, when the load fails, or when a player reconnects before a previous load completes. Player sessions now use a load-state machine (LOADING/LOADED/FAILED) with a session token, and only fully loaded sessions are ever saved.
• Fix: Progress earned while a player's data is still loading is now merged with the loaded data instead of being overwritten, and a failed load retries up to three times before the session is marked non-savable for that session.
• Fix: A delayed load that completes after the player disconnects no longer recreates stale in-memory data for the offline player.
• Storage: Auto-save, shutdown, and database migration now persist only loaded players that have unsaved changes, and concurrent saves are de-duplicated by sequence so an older snapshot can never overwrite newer data.
• Fix: Trigger evaluation is now paused during /vjourney reload and resumed only after the advancement tabs are rebuilt, preventing an async evaluation cycle from racing against a half-rebuilt state. The polling task is also cancelled before any restart so reloads cannot leak a timer.
• Fix: Non-persistent achievements are no longer briefly revoked and then re-granted while a player's data is still loading, since count-based triggers temporarily read zero during that window.
• Fix: permission triggers are now resolved during the main-thread snapshot phase, so LuckPerms/Bukkit permission lookups no longer run on the async evaluation thread.
• Performance: BetonQuest tag and point lookups now cache the resolved reflection methods instead of re-scanning the API on every evaluation cycle.
• Performance: WorldGuard region_enter checks now resolve all configured regions with a single query per player per cycle instead of one query per region.
• Validation: Achievement keys longer than 191 characters now log a warning at load time, since they could otherwise silently fail to save to the database.