I was wandering around in my snapshot test world but I went too far and the game crashed. This crash did not occur when I generated a completely new world, so my current theory is that because my world was made before 1.18, and I had never traveled towards that direction, the chunk blending crashed the game.
My world is too big, so I can't upload it here.
The exception's message, "Asking for biomes before we have biomes", made me audibly laugh. Kudos Mojang.
How to reproduce:
Create a world in 1.17.1 or older.
Upgrade the world to 23w16a.
If the game doesn't immediately crash, start traveling around a bit until it does.
Stack trace
23w16a: crash-2023-04-20_20.34.22-server.txt
Description: Exception generating new chunk
java.lang.IllegalStateException: Asking for biomes before we have biomes
at deh.getNoiseBiome(SourceFile:267)
at dic.b(SourceFile:255)
at dic.a(SourceFile:187)
at dic.a(SourceFile:168)
at dic.a(SourceFile:122)
at dib.a(SourceFile:96)
at dds.e(SourceFile:70)
at dds.a(SourceFile:256)
at ahq.a(SourceFile:704)
at com.mojang.datafixers.util.Either$Left.map(Either.java:38)
at ahq.a(SourceFile:693)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at ahs.b(SourceFile:62)
at bcl.h(SourceFile:91)
at bcl.a(SourceFile:146)
at bcl.run(SourceFile:102)
at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1395)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Linked issues
is duplicated by 1
Attachments
Comments 5
I am unfortunately not on my computer right now, so I can't attach the world at the moment. Please expect it in around 7 hours from now. I will attach it, I promise.
I am also having this issue. I have had to use MCA many times to delete chunks that I don't care that much about in the area of this glitch. It fixes it sometimes but I just had to stop playing because its happened again and I'm getting tired of figuring out what chunks to delete to fix it. Thankfully it hasn't affected my main base chunks. It seems to affect areas that have loaded from previous versions that you then go load more fresh adjacent chunks.
Please attach the affected world. This will help a lot!