Mixintrace Reloaded Unofficial Wiki › Guides › Identify Which Mod Caused a Crash
Identify Which Mod Caused a Crash
Reading the Mixin Stacktrace
When your game crashes, MixinTrace Reloaded adds a section called Mixins in Stacktrace to your crash log. This section lists every mixin that was active when the crash happened, along with the mod that injected it.
Each line shows:
- The Minecraft class being modified (e.g.,
net.minecraft.class_465) - The mixin class name (e.g.,
AbstractContainerScreenMixin) - The mixin JSON file in parentheses (e.g.,
bunchotrinkets.mixins.json)
Finding the Culprit
1. Open your crash report file (usually in .minecraft/crash-reports/)
2. Search for the Mixins in Stacktrace section near the end
3. Look for mixins related to the feature that broke (screen rendering, inventory, etc.)
4. The mixin JSON filename tells you which mod to investigate
5. Cross-reference the mod name with your modlist to confirm
If multiple mods modified the same class, check the order they appear in your mod folder—load order conflicts often cause crashes. Remove or update the suspicious mod and test again.