mojang.et1et
Assigned
Reported
Comments
There seems to be a "fix". I noticed there is a bugfix in chunker.app version 1.19.10 which is addressing some chunk blending bug in 1.20.30. So chunker might have fixed the bug that is still present in bugrock.
The "fix" steps are as follows.
Take your 1.20.15 world and move to a location where all the chunks are already generated (so bad chunks don't get generated in).
Update bedrock to 1.20.30 (using the unofficial bedrock launcher is a good way to do this) and load in the world, and then save the game. Now your 1.20.15 world is a 1.20.30 world.
Export your 1.20.30 world, and upload it to chunker.app, and convert it to the same version for the output (so 1.20.30). All entities will be lost, but at least you will keep your items.
Now update your bedrock to 1.20.40, and import the chunker converted 1.20.30 world. Now, new 1.20.40 chunks will generate properly, and the world gets updated to 1.20.40
No clue about how "stable" this fix is (it's possible that 1.20.50 will break things again), but it at least made it possible to get a 1.20.15 world up to the latest and get proper chunk generation again.
Note, after you have done steps 1-4, there is also a way to fix the previously generated back chunks if you have any in your world. Simply delete those chunks in Amulet, and then they will regenerate back in properly.
I don't have a 1.20.30 screenshot handy, but I did do this check over the weekend when I was looking into this, and I can confirm that 1.20.30 and 1.20.15 generation is identical block for block. This is easy to confirm, just create a new world with this seed in 1.20.30 and visit these coordinates and you will find it is actually identical to my 1.20.15 screenshot.
The bug however appears when chunks that were not saved in 1.20.15 are subsequently generated in 1.20.30.
I would beg to differ. Having the landscape torn up like that really breaks the immersion.
This is also not a blending issue. If you were to generate the exact same seed and location using 1.20.30, it actually generates block by block identical to 1.20.15, which is the expected behavior because the chuck generation did not change between these two versions.
It only generates differently when it is a 1.20.15 world being loaded in 1.20.30, so that is clearly a bug. The reproduction steps are pretty clear and on two separate devices, I've been able to reproduce this 100% of the time.
Edit: I think the changed title is actually less accurate, because there is not supposed to be any blending between 1.20.15 and 1.20.30 as the terrain generation did not change. This can be demonstrated by generating the same terrain in both versions to confirm.
I am also encountering this on 1.21.31, this one really ought to be fixed since it impacts dark forest/pale forest more, and that's a big part of the upcoming release.
In some biomes (like the dark forest, and it's pale variant), even if you delete the chunks and cause them to regenerate, the problem remains because the trees do not generate in the same way each time.