[Crash]: Chunk generation server crash after updating to 2.9
andremiller opened this issue · 19 comments
Possible Fixes
Yes
Modpack Version
2.9
What happened?
Running a dedicated server, while exploring the server crashed. I thought perhaps my world file got corrupted and started with a fresh 2.9 install, generated new world, but after logging in and taking a few steps, the server crashed again.
It looks like it could be related to an interaction between Productive Bees (Wood Solitary Nest), XyCraft (DirtFeature) and Farmer's Delight (Rich Soil Giant Tree)
Crash log is uploaded to gisthub, but here is a snippet:
Description: Feature placement
java.lang.NullPointerException: Cannot invoke "net.neoforged.neoforge.common.ModConfigSpec$DoubleValue.get()" because the return value of "java.util.Map.get(Object)" is null
at TRANSFORMER/[email protected]/cy.jdkdigital.productivebees.gen.feature.WoodSolitaryNestFeature.place(WoodSolitaryNestFeature.java:28) ~[productivebees-1.21.1-13.6.7.jar%23749!/:?] {re:classloading}
at TRANSFORMER/[email protected]/net.minecraft.world.level.levelgen.feature.Feature.place(Feature.java:168) ~[server-1.21.1-20240808.144430-srg.jar%23483!/:?] {re:mixin,re:classloading,pl:mixin:APP:xycraft_core.mixins.json:DirtFeature from mod xycraft_core,pl:mixin:APP:farmersdelight.mixins.json:KeepRichSoilGiantTreeMixin from mod farmersdelight,pl:mixin:A}
at TRANSFORMER/[email protected]/net.minecraft.world.level.levelgen.feature.ConfiguredFeature.place(ConfiguredFeature.java:28) ~[server-1.21.1-20240808.144430-srg.jar%23483!/:?] {re:classloading}
Crash Log
Latest.Log
No response
Xycraft and Farmers delight are likely innocents, they just have mixins far up on the stack trace
I have a similar crash already on load. Happened during terrain generation and caused the internal server to crash. The world won't load now.
I don't have a productivebees-server.toml in the worlds serverconfig folder - only in the config filter of the instance. Tried editing that but it gets regenerated on launch it seems so changes are mandated to a .bak file.
Tried copying the productivebees-server.toml to the serverconfig folder of the world but this also gets moved to a .bak file and a "correct" version is put in it's place.
Edit It seems to be Neoforge that is attempting to correct it:
[23Dec2024 18:46:10.558] [Server thread/INFO] [net.neoforged.fml.config.ConfigTracker/CONFIG]: Found config file override in path C:\Games\Minecraft\Original\Instances\All the Mods 10 - ATM10\saves\ATM10-LP\serverconfig\productivebees-server.toml
[23Dec2024 18:46:10.567] [Server thread/WARN] [net.neoforged.fml.config.ConfigTracker/CONFIG]: Configuration file C:\Games\Minecraft\Original\Instances\All the Mods 10 - ATM10\saves\ATM10-LP\serverconfig\productivebees-server.toml is not correct. Correcting
[23Dec2024 18:46:10.574] [Server thread/DEBUG] [net.neoforged.fml.config.ConfigTracker/CONFIG]: Loaded TOML config file C:\Games\Minecraft\Original\Instances\All the Mods 10 - ATM10\saves\ATM10-LP\serverconfig\productivebees-server.toml
can you find the config file in your worlds serverconfig folder called productivebees-server.toml
and find the segment [Worldgen]
and add these two values?
cherry_wood_nest = 0.05
mangrove_wood_nest = 0.05
can you find the config file in your worlds serverconfig folder called
productivebees-server.toml
and find the segment[Worldgen]
and add these two values?cherry_wood_nest = 0.05 mangrove_wood_nest = 0.05
Similar to jones-g, I don't have a productivebees-server.toml in the worlds serverconfig folder, there's only a few files in there, all starting with ftb*.
I've also tried editing the productivebees-server.toml in the ~/config folder, but that got reset during server startup.
In case it helps, I started a new world with a new seed ( -3093124618459941078 ), which ran fine for a few hours, until that too crashed when I explored:
Crash report: https://gist.github.com/andremiller/c4c40f0eadf6973ae48762aba3d1df10
what do you mean it resets? the game/server has to be closed when you change configs
what do you mean it resets? the game/server has to be closed when you change configs
The server is stopped/closed when I edit the config file. But when I then start the server, the file is updated during server startup - I can see the timestamp of the config file changes when the server starts up and those lines I added are gone.
See jones-g post above, it looks like neoforge detects an incorrect config and reverts it?
An update: I reverted to productivebees-1.21.1-13.6.6.jar on both server and client and the crash went away
did you indent the new config options to match the existing ones under [Worldgen]?
Yes, here is the .bak file the server created of my edited config file:
https://gist.github.com/andremiller/40f6938a9958793ba0745aadc2b2d77c
I also unfortunately have the same problem, I was playing in a server with 5 other people and after 2 days of playing every time we enter the server it crashes.
I sincerely hope it will be fixed as soon as possible!
I also unfortunately have the same problem, I was playing in a server with 5 other people and after 2 days of playing every time we enter the server it crashes. I sincerely hope it will be fixed as soon as possible!
It looks like it is fixed in 2.10, but the server file is not out yet.
I tried again 2 hours ago to open the server, but unfortunately the problem remains, if anyone finds a way to fix it let us know ❤️
Confirming that it worked for me - loading took a bit longer but I was able to start the world and play for a few hours.
This is the latest crash report, thank you very much for your help!
https://mclo.gs/wdzyU2T