Basically the title. This doesn't affect any cave biomes. To recreate this you just have to enter "REDApRES" into the seed field and create a new world. After that you can locate and tp/walk to any of the new mountain biomes except Meadow and the world will crash. I tried this on a server and the error was "java.lang.NullPointerException: Cannot invoke "dfw.a(double, double, double)" because "this.a" is null" and the server closed with error code "255".
I understand that technically seed "0" isn't even supposed to be entered but it have worked with all previous versions so I think this crash counts as a bug.
My guess is that this new mountain generation is completely based on the raw seed so there probably won't be any fix for this bug but I am still reporting it because I often use it and I got hope.
Stack trace
crash-2021-09-21_15.04.25-server.txt
Description: Exception generating new chunk
java.lang.NullPointerException: Cannot invoke "dfw.a(double, double, double)" because "this.a" is null
at dff.a(SourceFile:38)
at dfi.a(SourceFile:24)
at dff.a(SourceFile:30)
at dff.a(SourceFile:13)
at det.a(SourceFile:27)
at bze.a(SourceFile:352)
at crh.a(SourceFile:330)
at cod.e(SourceFile:98)
at cod$d.doWork(SourceFile:306)
at cod.a(SourceFile:256)
at abj.a(SourceFile:625)
at com.mojang.datafixers.util.Either$Left.map(Either.java:38)
at abj.a(SourceFile:619)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1146)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)
at abl.b(SourceFile:58)
at ask.g(SourceFile:91)
at ask.a(SourceFile:146)
at ask.run(SourceFile:102)
at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1434)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:295)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
Linked issues
is duplicated by 1
Attachments
Comments 7
I just found that I can visit the nearest Snowy Slopes with seed 0 without getting a crash. But at the same time if I create a Single Biome world with Snowy Slopes and seed 0, I once again get a crash.
Looks like it doesn't crash anymore in 21w40a, even in single biome worldgen.
EDIT: After restarting the game and creating a new seed 0 world, I can also confirm the crash in 21w40a.
Can confirm this is still an issue in 21w40a. Execute /locatebiome snowy_slopes
and teleport to the location. Instant crash.
The error message has changed because the obfuscation map has also changed. Instead of dfw.a
it is now dhi.a
.
Just so you know, obfuscations cycle around each time a new version comes out, so I don't think much use in tracking obfuscated name changes
How I discovered this bug
I first discovered this bug on July 15, 2021 in Minecraft 1.18 Experimental Snapshot 1, when I was first trying to check out Minecraft 1.18's new mountains. I used seed 0 ("creashaks organzine") because I considered it to be kind of ubiquitous. However, when I used /locatebiome to locate the nearest Snowy Slopes biome and teleport there, my game crashed.
I was just about to create a bug report of my own when I discovered this one.
I have done some testing with this bug
The object listed in the exception "dfw
" is only called that in snapshot 21w37a, it's called "dfk
" in 1.18 Experimental Snapshot 1, "dfn
" in Experimental Snapshot 5, "dfq
" in Experimental Snapshot 7, "dha
" in 21w39a, and "dhi
" in 21w40a. According to a previous comment by the user "ampolive", the name changed because the obfuscation map changed.
I have concluded that this crash occurs when trying to generate grove, snowy slopes, jagged peaks, frozen peaks, and stony peaks biomes. When testing these biomes, I set my render distance and simulation distance to 2 as to make sure the chunks being generated were only those of the biome I was looking at.
I have attached all of my crash reports where the game crashed this way.
edit: it is inaccessible let me add the links
[media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media][media]I hope this information is useful!
Can confirm.