How to Read a MixinTrace Crash Report to Find the Guilty Mod

When Minecraft crashes with MixinTrace installed, the crash report contains a section that lists every mixin that was applied to the classes involved in the crash. Your job is to read that list and work backwards to the mod that owns the offending mixin.

Locate the MixinTrace section

Open the crash report (in your crash-reports folder, or the window that pops up on crash). Scroll past the stack trace until you find the block MixinTrace adds — it lists mixins grouped by the target class they were injected into. Each entry shows the mixin class name and, where available, its configuration name (the .mixins.json file it came from).

Match the mixin to a mod

Mixin class names usually contain a recognizable package prefix, often the mod's id or author namespace. The configuration name is the strongest clue: it typically matches the mod's internal name. Cross-reference that name against your mods folder — the jar filename usually contains the same identifier. If two mods patch the same target class, the one whose mixin appears in the failing stack frame is the prime suspect.

Act on it

Disable or remove the suspect mod, relaunch, and reproduce the crash. If it disappears, you found the culprit. If not, repeat with the next mixin in the list that touches the same class. Report the mixin name and config to the mod author so they can fix the conflict.