Open FoxSamu opened 3 years ago
I'll be honest I have no idea how this happens. It could be caused by CCA generating classes before Identifier
gets loaded by minecraft, but that really should not happen.
Hey, look, a wild bug (re)appeared! https://pastebin.com/iucgj9yG
Edit: outside the context of a mod-specific method https://pastebin.com/2envGamS
Updating to the 1.16
branch has (re)fixed the issue for me, but this seems too inconsistent currently for that to be a definite fix
Edit: literally out of the blue at random without refreshing gradle or even reopening the project, the issue is back
Edit edit: the issue is gone again!?!?!?
Updating to the
1.16
branch has (re)fixed the issue for me, but this seems too inconsistent currently for that to be a definite fix Edit: literally out of the blue at random without refreshing gradle or even reopening the project, the issue is back Edit edit: the issue is gone again!?!?!?
hm.. this definitely looks like some kind of race condition then
In the development environment and maybe other places, in some contexts Cardinal Components fails when loading the world because the
Identifier
class is being loaded from different classloaders. It happens when using thecustom.cardinal-components
configuration infabric.mod.json
, and when using theStaticComponentInitializer
.Depending on the world settings, upon creating a new world the game either crashes after loading the complete world, or it prints a lot of crash reports while generating the world and then hangs. Anyway, it's all the same issue:
I was trying to help @andantedevs with his mod, who literally has the same environment, he had the same issue but for him it works fine now. I tried to do everything he did to fix it but it didn't work for me - that is:
I'm working in IntelliJ Community Edition 2021.1, on Windows 10