-
-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IdMappingEvent can't be posted successfully #2041
Comments
As far as I can tell, this event is quite useless. It is fired a single time right after registries are frozen, and with no remaps. We should probably remove it in 1.21.5? |
This is an amazingly usefull event during porting and migrations! Do we have any kind of alternative for this system? |
The alternative is to use aliases. 😛 Known registry entries are not saved to disk anymore since the registry rework, so I don't see how this event could possibly work. |
I noticed this event because I wanted to do something after completing all the registries. I just noticed that |
Have you tried
Yes |
Minecraft Version: 1.21.4
NeoForge Version: 21.4.91-beta
changelog here https://neoforged.net/changelog/ don't show information that may have fixed this
Steps to Reproduce:
subscribe the IdMappingEvent(on forge bus)
Description of issue:
The IdMappingEvent can't be posted successfully, the reason is as follows
The forge bus is an
EventBus
that is shutdown when createdas
startShutdown
is calledNeoForge/src/main/java/net/neoforged/neoforge/common/NeoForge.java
Lines 12 to 22 in f1d3f70
the bus is enabled at this place
it is too late for
IdMappingEvent
, as here we have almost complete mod loading and are collectingModLoadingIssue
NeoForge/src/main/java/net/neoforged/neoforge/client/loading/ClientModLoader.java
Lines 110 to 128 in f1d3f70
but the event IdMappingEvent is fired at this place, where the
freezeData
is calledwhere the mod loading Message is still
REGISTERING
, the bus still shutdown and haven't be startedNeoForge/src/main/java/net/neoforged/neoforge/internal/CommonModLoader.java
Lines 46 to 55 in f1d3f70
The text was updated successfully, but these errors were encountered: