This vulnerability occurs when the server and client become desynchronized during container interaction. When a player interacts with a clan chest under unstable packet conditions, the inventory state may not be properly finalized, leading to inconsistent transaction handling.
In certain cases, item movement operations can be processed twice due to missing synchronization between open, interact, and close states. This results in duplication where items appear in both the player inventory and the clan chest simultaneously.
The issue is not caused by any specific hacked client, but rather a logic-level weakness in how inventory state transitions are handled on the server side. It becomes more noticeable under lag, packet interruption, or delayed container closure scenarios.
We are currently implementing a fully server-authoritative inventory model to ensure all item transactions are validated in real-time. This removes dependency on client-side state or container close events, which are unreliable under modified or unstable network conditions.
This is a controlled and non-critical issue. It does not lead to server crashes or world corruption. The impact is limited strictly to item duplication in clan chest systems and does not affect core server stability.
A fix is already in progress and will ensure full prevention of desynchronization through strict event handling and immediate state updates on all inventory actions.
Temporary Mitigation
As an immediate precautionary measure, the Clan Chest feature can be disabled via config.yml to prevent exploitation while the permanent fix is being deployed. Setting the clan chest module to disabled will fully eliminate exposure to the desynchronization exploit until the updated inventory handling system is released. This action is recommended for servers operating in competitive or high-value economy environments where item duplication impact must be minimized immediately.