Open No3371 opened 3 years ago
We use BYG as well and hadn't had a problem so far but minecraft modding is like that isn't it?
Please provide a worldseed, minecraft version, and the x,y,z coordinates. Pending this info, I'll load HWM with BYG and give it a look to see if I can generate a crash..
I just finished a major upgrade with a rewrite of the spawn weight functions and uploaded a new version for 1.16.3, 1.16.4, and 1.16.5.
You are the first report of this problem. However, it could explode into a big deal any time so always best to try to stay ahead of these things.
Note: check for double spawner entries. check for null spawner entries.
I may have fixed this. I think it occurred when a biome had no existing spawns defined for it. Would appreciate your worldseed so I can look at it personally!
Sorry for the silence, got busy.
Just quickly took a look in the level.dat: 6513664960513486835
, hope it helps. (Unfortunately we did not note the coordinates.
No Problem! We all do. I'll give this a look.
I have a really huge modpack and recently this happened out of no where:
After done some research this is caused by wrong weight calculation when picking mob to spawn from a biome's mob candidates. So I did some A/B test with mob mods and it turns out It's Hostile Water Monster.
This is weird because It has been days since I got the mod, and It had been running OK (except for the noise/console spams). As the exception always happens when any player arrive a certain area in my world, I deduced it's one of the biome somehow has a corrupted weight table when Hostile Water Monster is loaded.
As Minecraft just don't give any useful info when stuff spawning goes wrong, unfortunately the only related information I have for you is I have BYG (Oh The Biomes You Go) installed and I've triple checked all the config values are good. Also I can not isolate the potential problematic biome because it will instant crash as soon as anyone get close to the area.
So this is a FYI/reminder to let you know this happended so if anyone else also encountered this It's not so surprising.