You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't always happen, but more often than not I can replicate it by just making new worlds and generating new rifts with the kaleidite cores. Sooner or later, the deadlock will happen.
I, too, am running a rather large modpack with a lot of customizations - which unfortunately makes it a lot harder to isolate whether it's a mod conflict or not. Please let me know if you need more information.
I compared my mod list with the mod list originally posted in #12 and did some testing with the mods we had in common.
I wasn't able to reproduce it with only Multiverse installed, so after testing I'm pretty sure it's an interaction with Alex's Caves; I can reproduce the deadlock with only Multiverse 3.0.3 and Citadel 2.6.0/Alex's Caves 2.0.2 installed.
What's interesting about this is that when I originally encountered the issue, I was using a custom datapack that restricted which biomes Multiverse was allowed to generate with - and Alex's Caves biomes were not on that list(specifically because I suspected their special generation would cause problems). It seems it happens regardless of whether Multiverses are actually configured to allow Alex's Caves biomes to spawn - in the logs I'm providing here, I'm using only the default settings of both mods.
As far as I can tell, I don't think it's an issue of deadlocking. It seems to be crashing relating to a tag missing. I'm working on a structural update right now, and I think it may fix this.
Not-February
changed the title
[1.20.1] Chunk generation deadlock upon entering rift
[1.20.1] Chunk generation crash upon entering rift
Dec 21, 2024
I'm still experiencing #12 with Multiverse 3.0.3.
It doesn't always happen, but more often than not I can replicate it by just making new worlds and generating new rifts with the kaleidite cores. Sooner or later, the deadlock will happen.
I, too, am running a rather large modpack with a lot of customizations - which unfortunately makes it a lot harder to isolate whether it's a mod conflict or not. Please let me know if you need more information.
Here's some logs and a relevant thread dump.
latest.log
debug.log
threaddump.txt
The text was updated successfully, but these errors were encountered: