Which mod is causing my crash, and how do I find it?
When a modded server crashes, the Console almost always tells you which mod is to blame — you just need to know where to look. Here's how to find and fix the culprit.
Reading the crash
- Open the Console and read the lines just before it stopped — a crash report usually points at a mod ID or class.
- Use "Share logs via mclo.gs" to get a clean, shareable link.
- If it's not obvious, bisect: remove half the mods, test, and narrow down.
- Update or remove the culprit (and check its dependencies).
Common patterns
Crashes right at "Loading" are usually a missing dependency or a wrong-version mod.
Tip: The "Share logs via mclo.gs" button in the Console gives you a tidy link you can share with our team or a mod author when you need a second pair of eyes.
Frequently asked questions
Where does it say which mod crashed? In the Console/crash report — read the lines just before it stopped for a mod ID or class name.
What if the report doesn't name a mod? Bisect: remove half your mods, test, and keep narrowing until you find the culprit.
More in Mods
- How do I install mods?
- Mods need Forge/Fabric — how do I set that up first?
- Are mods client-side or server-side — do players need them too?
- How do I install a mod manually or from CurseForge when it's not in the list?
- How do I fully remove a mod without leaving broken data or crashing?
- Can I add mods after the server has started, or will it crash?