Contents (4)
Start with the log
Crafted Core itself rarely crashes the game, but a dependent mod calling into it can. Open your crash report or latest.log and search for the words "Crafted Core" and "dependency." The stack trace usually names the dependent mod that triggered the failure, even when the core appears in the trace.
Check version alignment
The most common cause is a mismatch: a dependent mod built for one Minecraft version or loader running alongside a Crafted Core built for another. Confirm every mod that depends on the core is built for the same Minecraft version and the same loader as the core itself. Remove any file that does not match.
Isolate the culprit
If versions look correct, temporarily remove mods one at a time — starting with the ones that depend on Crafted Core — and launch between each removal. When the crash stops, you have found the mod interacting badly with the core. Re-add the others and leave that one out until an update is available.
Rule out unrelated conflicts
Sometimes the crash is not about Crafted Core at all, but about two dependent mods conflicting with each other through the shared code. In that case, check whether both mods are current, and test them together without other mods to confirm the interaction. Report the conflict to the mod authors with your log so they can address it.
