Only one mod's initializer gets loaded about fabric-loader HOT 6 CLOSED

According to https://stackoverflow.com/posts/12447162/revisions, a class loaded by two different class loaders will have two different Class<T> instances. Since Class doesn't implement equals and hashCode, it's not a suitable key for a map when multiple class loaders are involved,

Interestingly enough, this only happens when I use the generated IntelliJ runs, not ./gradlew runClient.

from fabric-loader.

Nice catch! I'm aware of most of the repercussions of multiple classloaders, but couldn't quite identify where things went wrong.

This was already on its way to be fixed in 0.4.0, but with the analysis one could probably get this fixed in 0.3.x...

from fabric-loader.

This was already on its way to be fixed in 0.4.0, but with the analysis one could probably get this fixed in 0.3.x...

Is 0.4.0 just around the corner? If not, I could make the PR to fix in 0.3.x this weekend if you like.

from fabric-loader.

This issue should be reopened since my fix was bad.

from fabric-loader.

I'm not giving it another shot at a fix in 0.3.x. It's fixed properly in 0.4.x, backporting the proper fix is way too much effort.

from fabric-loader.

I just meant leave the issue open until 0.4.x release, as an indicator it's a known issue.

from fabric-loader.