How to Tell Which Mod Is Conflicting With Another Using MixinTrace

Mixin conflicts happen when two mods inject into the same target class and their changes clash. MixinTrace makes these visible by listing every mixin applied to a class in the crash report, so you can see exactly which mods are fighting over the same code.

Find the shared target class

In the MixinTrace section of the crash report, look for a target class that has multiple mixin entries. That class is where the conflict lives. Note every mixin listed under it and the configuration name beside each one.

Identify the owners

Each configuration name maps to a mod. Check your mods folder for jars whose names contain that identifier. You now have the full list of mods patching that class. The crash stack trace will usually point at one specific mixin's injected code — that is the one whose assumptions were broken by another.

Resolve the conflict

Try updating both mods first; conflict fixes are common. If that fails, check whether either mod has a config option to disable the specific patch. As a last resort, remove one of the conflicting mods. When reporting the bug, include the target class, both mixin names, and both config names — that is exactly what the authors need to coordinate a fix.