You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything further down the stack than net.minecraft.launchwrapper.Launch.main(Launch.java:28) can probably just be dropped without much issues.
For some reason the reflection between launchwrapper and nmcm.Main doesn't have any source file nor line. No idea why.
Instead one could also cut at net.minecraft.client.main.Main.main() which would solve that issue but then one would loose the info that it's using launchwrapper as opposed to modlauncher (Forge 1.13+) or knot (Fabric).
But then again, 99% of crashes will probably not depend on the specific launcher used, so personally I'm for cutting at nmcm.Main.
Beware that the source name and line may change over different versions but package/class/method should always be the same (at least for 1.6.4-1.14.3).
Servers do not appear to be affected from this issue (though tbh I'm not entirely why).
Also remember that on the uppermost stacktrace should be modified and not any of the caused by (yes, that's a server so it wouldn't be affected anyway but it was the first one with caused-by that I could find).
The text was updated successfully, but these errors were encountered:
MultiMC launches MC from its own wrapper class for reasons leading to duplicate crash reports:
https://openeye.openmods.info/crashes/ccfdcc458cd87da5d75d51493f740403
https://openeye.openmods.info/crashes/1901be9a40fe69ba7ca917288b83edf9
There appear to be other launchers doing similar stuff, e.g. https://openeye.openmods.info/crashes/8f1faca0ffefb8e6a79c0742bea7a108
Everything further down the stack than
net.minecraft.launchwrapper.Launch.main(Launch.java:28)
can probably just be dropped without much issues.For some reason the reflection between launchwrapper and nmcm.Main doesn't have any source file nor line. No idea why.
Instead one could also cut at
net.minecraft.client.main.Main.main()
which would solve that issue but then one would loose the info that it's using launchwrapper as opposed to modlauncher (Forge 1.13+) or knot (Fabric).But then again, 99% of crashes will probably not depend on the specific launcher used, so personally I'm for cutting at nmcm.Main.
Beware that the source name and line may change over different versions but package/class/method should always be the same (at least for 1.6.4-1.14.3).
Servers do not appear to be affected from this issue (though tbh I'm not entirely why).
Also remember that on the uppermost stacktrace should be modified and not any of the caused by (yes, that's a server so it wouldn't be affected anyway but it was the first one with caused-by that I could find).
The text was updated successfully, but these errors were encountered: