Peca21
Members
-
Joined
-
Last visited
-
So I just removed BOTH better loading screen AND hammerlib and now it shows the incompatibility screen as it should. I guess we fixed it and found the problems. Brb gonna yell at the hammerlib and better loading screen devs.
-
So how do I list all the coremods present so I can remove them? I tried removing hammerlib but it didn't help.
-
I am asking why is it crashing when trying to render the screen that says That ladders requireds 1.18.1. It should not crash but show the screen that says i have the wrong version, Why doesn't it say that I have the wrong version?
-
So it does show the message in the debug log. I know that fast ladder needs new minecraft but i still don't know why is forge crashing like that, that's what I want to know.
-
I removed loading screen mod, still crashes but the report is different this time Crash report: https://pastebin.com/JDs3DW3U Debug log: https://pastebin.com/M0hRyKV5
-
So I built a modpack using GDLauncher and I didn't realize but GDLauncher is currently broken and it was not downloading mod libraries, only mods. So every time I downloaded a mod I had to manually check if I am missing a library. But when I missed one minecraft would just crash with this error and not show the error screen that the mod is missing something. Crash log: https://gnomebot.dev/paste/967084929479499806 Latest log: https://gnomebot.dev/paste/967090029308547102 I think the same thing is happening when I have the wrong version for a mod, it tries to show me an error screen saying this mod requires this forge version but instead it crashes. Working mod list (this time built in curseforge launcher): https://pastebin.com/0LxhzYuC If I add something like colossal Chests mod to that mod list WITHOUT its library mod it will crash with the above crash report which tells me nothing. Also if I add Faster ladder climbing to that same working modpack (it doesn't need any library mods as far as I can see), it ALSO crashes with the SAME CRASH REPORT. Am I doing something wrong or is this a bug in Forge? If it's not bug in forge how do I find what's broken since the crash report is always the same?