Cloth Config API

Cloth Config API: The Quiet Dependency

Cloth Config doesn't add any features you'd notice directly — it's a shared configuration library that many other mods rely on for their settings menus. With over 136 million downloads, it's one of the most depended-upon libraries across the Fabric and Forge ecosystems.

Whether it belongs on your server depends entirely on what the mods that require it actually do: some configuration options are purely cosmetic client-side menus, while others control server-relevant behavior. When in doubt, install Cloth Config on both client and server — it's lightweight and won't cause issues either way.

Practical tip: If a dependent mod needs Cloth Config and it's missing, your server log will usually show a clear "Missing Dependency" error on startup — that's your signal to add the jar to the mods folder.

Plan the rollout and operation

Cloth Config is needed only when an installed mod requires the matching loader variant. Record which entry depends on it so the library is not removed later as apparently useless. After updates, open configuration screens for dependant mods on the client and, where relevant, the server. Keeping several variants for the wrong loaders in one folder is more likely to cause startup failures than broaden compatibility.

Before installation, back up the world, mods, config, and defaultconfigs, and record the Minecraft, loader, mod, and dependency versions. Start the complete list on a copy first and read the log for missing or incompatible requirements. A meaningful test covers server boot, joining with a matching client, chunk loading, the core feature, saving, restarting, and joining again. Measure performance mods against the same world and load; validate libraries through at least one dependant feature. Update only one package or one related dependency group per run. Before removal, determine whether blocks, entities, items, or configuration remain in the save. Only a cleanly loading world copy justifies changing the live server. Keep previous files and the backup ready rather than mixing several versions during a boot failure. Finally, record the result with the server log and client version so later updates can be compared against a proven working state.