Minecraft Crashes in my Modpack when I try to start it with exit code 0 about chiseled-me HOT 3 OPEN

Uh, it's another one of these.

So this exact crash is known, but I have absolutely zero idea why it happens:
Forge complains that a thing that I register is not registered while, I mean, I do register it, in code, properly, what else to tell it 🤷

Try to update Forge, but usually this is caused by some other random mod somehow (at one point I remember it was Forestry, but then the next forestry version fixed it) so you can try to find it, or maybe it's your unique set of mods, who knows.

But yeah, this crash is known and once I know wth happens I will fix that.

P.S. process exit codes mean absolutely nothing in the context of minecraft or modding it, in fact exit code 0 means that the program finished successfully, not a single clue why mojang decided to include the exit code in the crash popup but I am tired of people telling me their game 'crashed with exit code 0'.
You are not like them, you at least gave the debug.log which is all I am asking for, keep it up, you are great.

from chiseled-me.

Hey, thanks for your answer, And I figured out, why it was crashing the whole time, it seems like, that it isn't compatible with LagGoggles and/or tickCentral

(I have no Idea what those mods do, so I deleted them, and now it works just fine ^^)

maybe this information will help you to fix it some day :)

from chiseled-me.

Yeah this would help, ty

from chiseled-me.