[Bug]: Dedicated server cannot launch, attempts to load ClientWorld class
sctjkc01 opened this issue · 16 comments
Bug Description
Attempting to load a dedicated server with Resourceful Bees on causes the server to fail to initialize, due to trying to load net/minecraft/client/world/ClientWorld.
How to Reproduce?
- Create a new dedicated server from Forge 36.2.0 with just Resourceful Bees installed.
- Launch the server (
java -jar forge-1.16.5-36.2.0.jar) - Observe crash.
Expected Behavior
Expected the server to load
Version
0.9.9
Mod Loader Version
1.16.5-36.2.0
Logs or additional context
net.minecraftforge.fml.LoadingFailedException: Loading errors encountered: [
Resourceful Bees (resourcefulbees) has failed to load correctly
§7java.lang.RuntimeException: Attempted to load class net/minecraft/client/world/ClientWorld for invalid dist DEDICATED_SERVER
]
at net.minecraftforge.fml.ModLoader.waitForTransition(ModLoader.java:269) ~[forge:?] {re:classloading}
at net.minecraftforge.fml.ModLoader.dispatchAndHandleError(ModLoader.java:236) ~[forge:?] {re:classloading}
at net.minecraftforge.fml.ModLoader.gatherAndInitializeMods(ModLoader.java:194) ~[forge:?] {re:classloading}
at net.minecraftforge.fml.server.ServerModLoader.load(ServerModLoader.java:44) ~[forge:?] {re:classloading}
at net.minecraft.server.Main.main(Main.java:95) ~[?:?] {re:classloading}
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_292] {}
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_292] {}
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_292] {}
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_292] {}
at net.minecraftforge.fml.loading.FMLServerLaunchProvider.lambda$launchService$0(FMLServerLaunchProvider.java:51) ~[forge-1.16.5-36.2.0.jar:36.2] {}
at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-8.0.9.jar:?] {}
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-8.0.9.jar:?] {}
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-8.0.9.jar:?] {}
at cpw.mods.modlauncher.Launcher.run(Launcher.java:82) [modlauncher-8.0.9.jar:?] {}
at cpw.mods.modlauncher.Launcher.main(Launcher.java:66) [modlauncher-8.0.9.jar:?] {}
at net.minecraftforge.server.ServerMain$Runner.runLauncher(ServerMain.java:63) [forge-1.16.5-36.2.0.jar:?] {}
at net.minecraftforge.server.ServerMain$Runner.access$100(ServerMain.java:60) [forge-1.16.5-36.2.0.jar:?] {}
at net.minecraftforge.server.ServerMain.main(ServerMain.java:57) [forge-1.16.5-36.2.0.jar:?] {}
Acknowledgement
- I agree that I read the terms at the top of the page.
My apologies. Here you go.
It should be the automatically generated default, but just in case: here you are.
I don’t see what the Config has anything to do with the error. It crashes after loading the biome dictionary. So it’s whatever the next step in the load process is.
the line it crashes on is the init for custom bee Data builder on the loading of apiary outputs at least in my build
at com.resourcefulbees.resourcefulbees.api.beedata.CustomBeeData$Builder.<init>(CustomBeeData.java:462) ~[resourcefulbees:1.16.5-0.9.9]
@sctjkc01 can you reproduce the error? does it happen every load
Yeah gravy and I compared the last release and the code base Bc of the commit fiasco when we switched the main branch to arch. We couldn’t find anything that didn’t match so I’m just hoping we didn’t miss something.
@sctjkc01 try downloading the update we pushed to curse and let us know if you still have an issue please.