How to Collect the Information Mod Authors Need From a Mixin Conflict

Gather before you close the screen

Mixin Conflict Helper shows a friendly summary, but the moment you click a button the game crashes normally. Capture everything you need first, because the GUI will not come back on its own.

Information checklist

1. The name of the failing mixin and the mod it belongs to, as shown on the GUI.

2. The target class and method the mixin tried to modify.

3. The names of any other mods known to touch that same target.

4. The full crash report from your crash-reports folder and the latest log from your logs folder.

5. Your mod loader, its version, and the Minecraft version.

6. A short description of what you did right before the crash, such as opening a world, using a specific block, or launching the game.

Formatting the report

Put the summary in the issue title, for example naming both mods and the shared target. In the body, list the mods and versions, then attach the log files. If the log is huge, upload it to a paste service and link it. Mention that Mixin Conflict Helper identified the conflict, since that tells the author the report is already narrowed down. Avoid pasting only the GUI text, as it omits the stack trace authors rely on.