Skip to content
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

upgrade request 1.18.2 #18

Open
ptk2003 opened this issue May 7, 2022 · 8 comments
Open

upgrade request 1.18.2 #18

ptk2003 opened this issue May 7, 2022 · 8 comments

Comments

@ptk2003
Copy link

ptk2003 commented May 7, 2022

I can build jar from source 1.18.1 but it not loading in 1.18.2 mc

@AuroraRAS
Copy link
Collaborator

Can you provide more details? like some errors line in your game launcher.

@ptk2003
Copy link
Author

ptk2003 commented May 7, 2022

Mod File: SimElectricity-1.0.0.jar
Failure message: SimElectricity Essential (sime_essential) has failed to load correctly
	java.lang.NoClassDefFoundError: net/minecraftforge/event/RegistryEvent$NewRegistry
Mod Version: 1.0.0
Mod Issue URL: https://github.com/RoyalAliceAcademyOfSciences/SimElectricity/issues
Exception message: java.lang.ClassNotFoundException: net.minecraftforge.event.RegistryEvent$NewRegistry

latest.log
crash-2022-05-07_17.28.06-fml.txt
2022-05-07 17_28_19-Minecraft_ 1 18 2

@AuroraRAS
Copy link
Collaborator

Maybe you need redownload forge and its library? I guess.
enable your VPN if you are living in China.

@ptk2003
Copy link
Author

ptk2003 commented May 7, 2022

I download and install latest 1.18.2-forge-40.1.16 it not solve issue (same error), all other mods build for 1.18.2 loading properly (they are removed for test to prevent mod incompatible).

Wich version of forge you can load mod (tested)?

@AuroraRAS
Copy link
Collaborator

Hey, @rikka0w0 ! We need some help.

@ptk2003
Copy link
Author

ptk2003 commented Jun 16, 2022

Hi. Any news?

@rikka0w0
Copy link
Owner

That's a known problem, 1.18.1->1.18.2 isn't a minor update, despite the gameplay does not change at all, things have changed quite a lot internally. I'm working on a total re-write of the registry stuff and it will fix this issue. Be patient. If you are also a developer, any help would be appreciated.

@rikka0w0
Copy link
Owner

Basically, the problem originates from the instantiation of registrable objects. Before 1.18.2, you can instantiate those things at any time before the actual registration happens, so we chose to initialize them statically. But since 1.18.2, you have to instantiate them at the correct instant, just before the registration event is fired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants