Fixing Player Data and Sync Problems Caused by Dependent Mods

Recognize a sync issue

Cupboard handles player data and client/server synchronization for the mods that depend on it. When that pipeline goes wrong, the symptoms are usually one of these:

• A setting or tracked value looks correct for you but wrong (or missing) for other players on the server.
• Per-player data resets after you log out and back in.
• Singleplayer works fine, but the same mod behaves differently on a dedicated server.

Because Cupboard is the shared layer, the fix is almost always about the *dependent mod's* data, not Cupboard itself.

Work through it step by step

1. Confirm client and server match. Cupboard synchronizes data between the two sides, so a version mismatch between what the client and server are running is the most common cause of desync. Make sure the dependent mod and Cupboard are present and consistent on both sides.

2. Check the dependent mod's config on the server. Server-side config values are what get pushed to clients. If a value is set differently on the server than you expect, clients will reflect the server's version.

3. Restart rather than reload. Player data and sync state are established at connection time. A clean restart of both client and server clears stale state far more reliably than an in-game reload.

4. Test with a fresh player profile if the issue follows one specific player — that isolates corrupted per-player data from a general sync fault.

If the problem persists across all players and both sides are matched, report it to the *dependent mod's* issue tracker and mention that it uses Cupboard, since the fault likely lies in how that mod calls Cupboard's data handling.