Most likely it's just two mods that are incompatible, at least that was what did it for me. Open your modpack folder -> Logs -> Latest. "For any that are still stumbling on this error like I did, the exit code is meaningless. No doubt I still have minor mod conflicts (my modpack has 230 mods so its almost inevitable) but at least the game can start. The glaring issue for me was that my Curseforge launcher wasn't up to date. There were some minor mod conflicts but I didn't want to look through them to find the biggest culprit so I asked ChatGPT to read it. So yeah, for me the actual errors showed up in the latest logs.
I'm just going to quote what some other guy said:įor any that are still stumbling on this error like I did, the exit code is meaningless. Hope this could help a mac user later on.
I made sure my java args were valid in the Minecraft launcher in the installation settings.Īfter doing all that, it finally worked. I did not manually change the default java runtime. I made sure the RAM allotted to the modpack was exactly what was recommended, not the minimum needed. I reinstalled the latest version of Java. I deleted minecraft itself, alongside all files related to it including other installations. I reinstalled a fresh copy of CurseForge. I deleted all launchers, as well as all launcher content (such as settings) found in my Application Support and Documents. I am on macOS Big Sur using a 2018 Macbook Pro. I followed a lot of advice found online, but here's everything I did that might have helped the error disappear, since most advice online is for Windows. Some packs worked fine, other would immediately crash once running in the Minecraft launcher with Exit Code 1, which is an error to do with an invalid java runtime. I've struggled for the last couple of days trying to get CurseForge packs running off the CurseForge launcher and GDLauncher.
0 kommentar(er)
