How to Fix a Mixin Conflict by Reordering or Removing Mods

Understand the two fixes

A mixin conflict happens when two mods patch the same target. You cannot edit the mixins yourself, but you can change which mods load and in what order. Removing one of the conflicting mods is the guaranteed fix; reordering sometimes works when one mod's injection is more tolerant of the other's changes.

Steps

1. From the conflict GUI, note both mods involved and the shared target class or method.

2. Decide which mod you can live without, or check whether either has a config option to disable the conflicting patch.

3. If you want to keep both, try changing load order. In most loaders, mods load in the order they appear in the mods folder or according to declared dependencies. Renaming files to change alphabetical order can shift load order, but this is unreliable and loader-specific.

4. Relaunch and reproduce the situation that triggered the crash.

5. If the conflict persists, disable one mod and confirm the game starts.

6. Check each mod's config screen for toggles that turn off specific patches, which is cleaner than removing the whole mod.

When reordering fails

If both mods inject at the exact same point with incompatible expectations, no load order will help. In that case, only an update from either author resolves it, so keep one disabled until a fix is released.