Gost

Gost 2.3.2_B Changelog

• This release is a patch update for version 2.3.2, focusing on resolving stability issues in the backpack restoration system and completely reworking the logic for handling player disconnections.
• No new gameplay features have been added; plugin and configuration versions remain unchanged.

🐛 Fix: Backpack restoration failure (restoring in-game items instead of original contents)

• Issue description
  In certain cases, after players end or leave a game session, their restored backpacks contain in-game items (such as adrenaline or berserk potions) rather than the original items they had before entering the game.

• Root cause
  The backpack snapshot was saved using [player.getInventory().getContents()], which shares references with actual in-game items. When "clearing the backpack and distributing in-game items" occurs at game start, this snapshot becomes contaminated, resulting in the player receiving a polluted "game backpack" upon restoration. Additionally, there was no protection against overwriting during snapshot saving—any secondary save during the match would overwrite the original backpack with the current game inventory.

• Fixes implemented

① Deep copy of snapshots: Added item cloning logic to perform [ItemStack.clone()] individually during both saving and restoring, completely severing reference sharing between snapshots and in-game items. Locations are also cloned to prevent contamination via teleportation later.

② Prevent duplicate overwrites: Added protection in [savePlayerState]—if a player already has an existing original snapshot, skip redundant saves and log a warning, preventing the original backpack from being overwritten by the game inventory.

③ Preemptive backup before clearing: Before clearing the backpack [in updatePlayerInventory], if a player is detected in the game but lacks a snapshot, immediately save one first, ensuring that a valid original backup exists prior to clearing.

④ Fixed execution order: Clearly define the fixed sequence in the game joining process—"first save original backpack, then clear/reset"—to prevent future modifications from accidentally reversing the order.

⑤ Diagnostic logging: Log the number of items in the backpack during both saving and restoring (e.g., "Saved player X's original backpack (N items)" / "Restored player X's original backpack (N items)") to facilitate future issue tracking.

🐛 Optimization: Player disconnection handling

• Changes made
  All player disconnections are now treated as voluntary exits from the game and queue, triggering immediate restoration of the original backpack without distinction based on online status.

• Specific changes

① Disconnection = exit: Unconditionally trigger the game exit procedure when a player disconnects, immediately restoring the original backpack. The restoration action runs synchronously within the PlayerQuitEvent (before player data is persisted), ensuring correct backpack restoration even if the player is already offline. 、

② Disconnection results in queue exit: If a player disconnects while in the matchmaking queue, they will be automatically removed from the queue and their entry fee refunded.

③ Silent handling: No notification messages will be sent to players upon disconnection (to avoid sending packets to disconnected users), but queue refunds, boss bar refreshes, broadcasts, and other logic will proceed as normal.

④ Snapshot fallback protection: If a player is no longer in the game session but has leftover snapshots, the exit process will perform an additional inventory restore to prevent unprocessed snapshot remnants.