Fixing Mixin Issues - 04Slash/Breaking-Down-Minecraft-Forge-Crash-Reports GitHub Wiki
Update: Mixin crashes can be easily fixed by adding in this mod. No need to do anything else unless this mod, for whatever reason, doesn’t work. If it doesn’t work, ensure the issue you are having is actually a mixin crash and not one of the other billion possible crashes.
This should only be a problem in 1.12.2. This is because some mods have decided to update the version of mixins that their mods are using. Mods using version 0.7 mixins are not compatible with 0.8 and will cause a crash. I will go over how to figure out what mods are using mixins and how to go about fixing it.
First off, the main sign of a mixin issue is that the game will crash instantly after launching it. This doesn’t mean it’s always a mixin issue, but it’s a good first clue.
Within the crash report will look something like this. Notice the “spongepowered.asm.mixin”. There may not be a crash report generated and in this case you will have to look in the latest.log which will have a very similar message. You are just looking for the above bit I mentioned.
To find out what mods are using mixins we will need to open the latest.log. CTRL + F and search for Mixin. These lines will appear near the top of the latest.log, usually mixed in with some other information. I separated them to they are easier to see. This will tell you which mods are using mixins.
Just below is a line [mixin]: SpongePowered MIXIN Subsystem Version=0.8 which will tell us what version of mixins is being used. Here we can see 0.8 is being used.
To fix the issue is usually simple. You have to find out if the mods listed have updates that updated their mixin version. Most mods have updated to 0.8 and it’s just a matter of getting those mods updated. In the above I can already tell that Phosphor 2.6 and Vanillafix -99 are using 0.7 mixins. This is just from past knowledge. The easiest way to go about this would be to just update the mods that are using mixins.
If it still crashes after updating the mods, while giving the same error, then it gets a little trickier. You will have to go to each of the mod’s curseforge page and look through the 1.12.2 changelogs until you find out what was the first verison that updated mixins. You would then have to downgrade to the previous version, or remove the mod that has yet to update mixins. So far the only mod I know of that has not updated mixins would be ‘BetterPortals’.
Some mods support both 0.7 and 0.8 mixins. So far the only mod I have ran into is MalisisCore. However, if MalisisCore is the first mixins mod that is loaded, it will load 0.7 mixins even if every other mod you have uses 0.8. This will cause a crash. To fix this, put 3 z infront of the malisiscore.jar name, like so: zzzmalisiscore-1.12.2-6.5.1.jar. This will force it to load after some mods, however I found it still doesn’t load last. If that doesn’t work then you’re forced to either remove malisiscore and the mods that depend on it or downgrade all other mods using mixins.
This is not a complete list. The below listed mods are the latest versions that are using 0.7 mixins. Anything newer will be using 0.8 unless stated otherwise.
- VanillaFix-1.0.10-99.jar
- phosphor-1.12.2-0.2.6+build50-universal.jar
- malisiscore-1.12.2-6.4.0.jar – The 6.5.1 version supports both 0.7 and 0.8, but can cause the above mentioned issues
- levelup2-1.3.0-shaded.jar
- DynamicSurroundings-1.12.2-3.6.0.2.jar
- Sledgehammer-1.12.2-2.0.4.jar OR Sledgehammer-1.12.2-2.0.8-thin.jar. – The ‘thin’ versions shouldn’t have issues with mixins.
- Surge-1.12.2-2.0.77.jar
- betterportals-0.3.7.7.jar – No 0.8 mixin version. If you have this mod you must downgrade every mod to the version that uses 0.7 mixins.