How to Fix a Mod That Won't Load Because Crafted Core Is Missing

Confirm the dependency is the problem

When a mod that depends on Crafted Core is installed without it, the game usually crashes during startup or the mod simply never appears in your mod list. Open your crash report or the latest.log file and look for a line naming Crafted Core as a missing or required dependency. That message is your confirmation — the dependent mod cannot initialize its shared code without the core present.

Get the core in place

Place the Crafted Core file in the same mods folder as the mod that requires it. Both must be built for the same Minecraft version and the same mod loader, or the loader will reject one of them. Do not rename either file; loaders match mods by their internal metadata, not the filename.

Verify the fix

Launch the game and check the mod list. Crafted Core should now appear alongside the dependent mod, and the dependent mod's items, blocks, or config options should show up in-game. If the crash persists, read the new log — it may now point to a different missing dependency or a version mismatch between the two mods rather than an absent core.

Keep them together

Whenever you update the dependent mod, update Crafted Core at the same time. A newer dependent mod may require a newer core, and mixing versions is a common cause of the same startup failure returning.