Keeping Core Lib and Its Companion Config Library Straight

Two separate technical mods by the same author have confusingly similar names, and mixing them up is a frequent source of broken installs.

Tell them apart by role

One is the core library: GUI, block, tile entity, packet, and registry utilities. The other is the config library: it handles in-game configuration screens and saved config files for mods that use it. They are not interchangeable and neither replaces the other.

Decide which you need

Check each dependent mod's requirements. Some need only the core library, some need only the config library, and many need both. When a mod's description or error message lists both, install both — a mod that opens a config screen at runtime will fail without the config library even if the core library is present.

Avoid duplicate files

Keep exactly one copy of each library in your mods folder. Two copies of the same library, or a core library file renamed to look like the config library, will cause load failures that are hard to read. If you are unsure which file is which, check the mod list screen after launch — it shows each loaded mod by its real name, so you can confirm both are present and distinct.