CodxLib Mod FAQ

No—CodxLib works automatically in the background once it's in your mods folder. You'll know it's loaded correctly if your Codx mods start without errors; there are no configuration steps or in-game menus to interact with.

Any mod built on the Codx framework will fail to load and you'll see error messages in your log file. CodxLib is a required dependency for all mods in the Codx collection, so you must have it present to run them.

Yes—that's exactly what CodxLib is designed for. It centralizes shared code so multiple Codx mods can coexist without conflicts or duplicate files slowing down your game.

Check your latest.log file in the logs folder for a startup message confirming CodxLib loaded, or verify that any Codx mods you have installed are running without dependency errors.

No—CodxLib runs silently in the background and only loads the shared code once, making your game more efficient than if each Codx mod carried its own copy of the same files.

CodxLib is the foundation that other mods depend on; it provides shared tools and services. Individual Codx mods add their own features and content on top of that foundation.

Yes—CodxLib works on both single-player and multiplayer servers. Make sure it's installed on the server and all clients have the same version to avoid sync issues.

CodxLib includes built-in update checking for connected mods, but it doesn't install updates automatically; it notifies you so you can download them manually through your mod manager or launcher.

Check your log file for specific error messages, verify CodxLib itself loaded successfully, and make sure all your mods are compatible with the same Minecraft version and loader (Forge/Fabric).

Yes—CodxLib provides multiloader support, meaning there are separate versions for each loader. Download the correct version for your modloader to ensure compatibility.