Topic category: Help with MCreator software
That's the only way I can put it. Random mods (I haven't finished going through them but I have around 50-60 mods in my modpack) instantly crash the game with minimal error. The error has varied throughout my trials, between Neoforge and Forge 1.20.1, always with Mcreator build 2025.2. Said error almost always references an internal part of Forge/Neoforge itself as the source of the crash, and it has gone as far as to list loading the Forge logo being the problem.
The mods I have located which cause it so far are PuzzlesLib, Embeddium Extra, Create: Slice and Dice, ModernFix, Oculus and Moonlight Library. I have gone through mods which start with letters K and onwards, but I know that there is at least one mod which can individually cause the crash in sections of mods A-B, C, D-E, F-G, and I-J, because I tried launching those chunks of mods separately, and the only category which didn't have a single one was T and onwards. This error makes absolutely no sense, to put it bluntly.
Here's the entire error, as of right now:
Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.modrinth.theseus.MinecraftLaunch.relaunch(MinecraftLaunch.java:63)
at com.modrinth.theseus.MinecraftLaunch.main(MinecraftLaunch.java:28)
Caused by: java.lang.module.ResolutionException: Modules mixinextras.neoforge and MixinExtras export package com.llamalad7.mixinextras.sugar.impl to module transition
at java.base/java.lang.module.Resolver.resolveFail(Unknown Source)
at java.base/java.lang.module.Resolver.failTwoSuppliers(Unknown Source)
at java.base/java.lang.module.Resolver.checkExportSuppliers(Unknown Source)
at java.base/java.lang.module.Resolver.finish(Unknown Source)
at java.base/java.lang.module.Configuration.
Yep, that's it. I get that 2025.2 isn't technically supported anymore, but I also don't really care, because modern versions of the game have been increasingly awful as of late, as the capitalist machine known as Microsoft demands even more unnecessary content for a game which was finished long ago. This is the earliest version I can reasonably use with modern modding technology, because even now that people agree modern updates suck, they still just keep updating things for new versions by voluntary choice instead of sticking with an old one. This is the exact kind of conundrum that almost made me entirely stop the process of modding (as in both installing and making mods) for this game, and I mean both the version thing and this bug.
Unfortunately you did not provide full log, as well as 2025.2 no longer being supported. If you mod for 1.20.1, use plugin and the latest version