Cupboard Mod FAQ

Cupboard is a library mod, not a content mod, so it adds no items, blocks, or mobs on its own. It gives other mods shared tools like a JSON config system, logging helpers, player data handling, and client-server data syncing, which is why you usually only notice it when something else depends on it.

No, you never install Cupboard for its own sake. You install it because another mod in your pack lists it as a required dependency, and removing it will break that mod.

Check your mods folder for mods that declare Cupboard as a dependency, or look at the crash log or mod list screen where missing dependency errors name the mod that needs it. In-game, the mods menu usually shows Cupboard as a library entry with no config of its own.

Cupboard itself typically has little or nothing to configure, because its config framework is used by the mods that depend on it. Those dependent mods each generate their own config files, usually in the standard config folder, and that is where you actually change settings.

Edit the config file belonging to the dependent mod, not Cupboard's, since Cupboard only provides the framework that reads and writes those files. If a mod offers an in-game config screen, use that instead so the values are validated and synced properly.

That mod was built on top of Cupboard's shared code for things like config handling, player data, or networking, so it cannot run without the library present. Install the matching Cupboard version for your Minecraft version and loader, and the error goes away.

Only remove it if no other mod depends on it. If any mod lists Cupboard as a requirement, deleting it will cause that mod to fail to load or crash the game on startup.

Cupboard is a lightweight library and rarely causes problems by itself. If you suspect it, check whether the crash log points at a dependent mod's config or networking code, since that is usually where the real issue lives.

Yes, in most cases it must be present on both sides, because it handles client-server data synchronization for the mods that use it. A mismatch between client and server versions of Cupboard or its dependent mods commonly causes connection or sync errors.

Yes, Cupboard is designed to coexist with other libraries and does not replace them. Each dependent mod uses whichever library it was built against, so having several library mods installed at once is normal and expected.

Check the dependencies section on each mod's download page, or read your game log after removing Cupboard, since missing dependencies are usually named there. Mods that use Cupboard's config or player data systems will fail to load or lose settings without it.

Open the dependent mod's JSON file in the config folder with a plain text editor and change only the values, keeping the structure and punctuation intact. A malformed JSON file will usually reset to defaults or cause the mod to log an error on startup.

Most Cupboard-based configs are read at startup, so you need to fully restart the game rather than just reloading a world. If the file was invalid JSON, the mod may have silently regenerated it, so check the file contents after restarting.

Crashes are almost always caused by a dependent mod being the wrong version for your Cupboard or game version, not by Cupboard itself. Update all mods that depend on Cupboard together and check the log for which mod failed first.

Yes. Because Cupboard handles client-server data sync, it must be installed on both the client and the server, along with any dependent mods. A client-only install will cause sync errors or connection refusals.

Player data issues usually come from the dependent mod, not Cupboard, and often appear after updating that mod mid-world. Back up your world, then check whether the dependent mod changed its data format or needs a fresh config.

Cupboard is lightweight and mostly runs at startup and during config or data sync events, so it rarely affects frame rate. If you see lag, it is more likely from the dependent mods using Cupboard's systems than from Cupboard itself.