Summary:
Loading the experimental world (created before 1.17.20.23) creates a huge mountain at the exit site.
Steps to reproduce:
Create a world with experimental gameplay in 1.17.30.22 (and below)
or you can download my world. (not open at 1.17.30.23)
Enter the world at 1.17.30.23 (most likely you will spawn in a cave)
Observed results:
Loaded, the nearest area will be turned into a mountain.
And also the bedrock will be raised.
Expected results:
The generation of loaded chunks should not change.
Image:
[media][media][media][media]Linked issues
is duplicated by 9
relates to 2
Attachments
Comments 6
I’ve found a cinematic example of this issue. I agree that it shouldn’t be like this, but I have to admit that it does look cool sometimes…
[media]
Experience this as well. My partner and I have a world we just traveled to find an ocean monument in. Weve had the experimental features on all year so it's gone through each update. This most recent well the outcome is extreme as the surrounding chunks along the entire journeys path have done this. The oceans are especially frustrating. Hoping this is a quick and easy fix for Mojang and we can continue on our unopened just in case copy of the world. Otherwise sadly this has killed it and we will need a new one 😨
[media]
Confirmed.
In my case I used an old world from 2017 and then upgraded it to 1.17.20.23 and then 1.17.30.23
Original bedrock level of the world has been raised to 64, 1.17.20.23's bedrock extends from 0 to 64. Void exists in previously (2017 and 1.17.20.23) generated chunks that have been modified (ex mined a block) in some way modified from -64 to 0. Un touched but previously generated chunks are over written with new (but correct) genration except when near a previously modified chunck.