How to Tell Whether a Mod Actually Needs Cupboard (and What It's Doing for You)

Why you installed a "library" mod

Cupboard is a library mod, not a content mod. It adds no blocks, items, mobs, or recipes of its own. If you installed it, it's almost certainly because another mod on your list declares it as a dependency. That means the answer to "what does Cupboard do?" is: it does work *on behalf of other mods*.

Reading the signs in-game

You can usually confirm Cupboard is present and functioning without opening any GUI:

• Check your mod list. In the mods screen, Cupboard should appear as a loaded entry alongside the mods that depend on it. If a dependent mod is missing Cupboard, it typically fails to load or shows a dependency error at startup instead.
• Look for config files. Cupboard provides a JSON-based configuration framework, so mods built on it tend to write their settings as JSON rather than the older .toml/.cfg style. If you see JSON config files appearing for a mod, that mod is likely using Cupboard's framework.
• Watch for shared player data. Cupboard handles player data and client/server synchronization for dependent mods. In practice this means things like per-player settings or tracked values persist correctly across sessions and stay consistent between singleplayer, LAN, and dedicated servers.

What you should *not* expect

Don't go looking for a Cupboard block to place or a Cupboard item to craft — there isn't one. Your interaction with Cupboard is indirect: you configure the mods that use it, and Cupboard makes sure those configs load, save, and sync properly. If a dependent mod misbehaves, its config file is the first place to look, not Cupboard itself.