The attached screenshots show portions of a desert and savanna biome that were generated in version 1.19.4, and the same areas in version 1.20 pre2. In the 1.20 pre2, the area was partially regenerated / overwritten by various ocean biomes (Cold Ocean, Deep Cold Ocean).
This causes a change in foliage color and sharp chunk boundaries between biomes. In this case, much of the pre-existing Desert biome (sand) collapsed into the ocean upon loading of the area in 1.20 pre2.
This was observed in a preexisting / old (pre-1.19) world.
Attachments
Comments 9
I have used OptiFine sporadically throughout the last many years, no mods apart from that.
The world was too large to attach here; so here is a Dropbox link to a zip folder: https://www.dropbox.com/s/wn2hqrqk1n7321v/The%20Wastelands.zip?dl=0
Hmm, I'm unable to reproduce this issue with the attached world. When loading it in 1.20-pre2, the area looks the same as in 1.19.4.
It would be great if you could also attach the game logs from the game session where the world corrupted. Also, are you able to reproduce this issue consistently, or was it just once?
I'm able to reproduce the issue at will, though it tends to occur in slightly different locations (a few hundred m apart) each time that a new copy of the 1.19.4 world is loaded up in 1.20 pre2.
In this example (screenshot attached), the behavior is same as before; a large chunk of pre-existing terrain was corrupted and overwritten by deep ocean biomes.
I have attached the game log and screenshot where the issue occurred again.
[media][media]
@unknown Thank for the detailed report and the world download. It was very helpful for tracking down the issue!
We were able to reproduce this issue, but not in all locations shown in the screenshots. While we fixed the cause for the locations we could reproduce it in, we don't see a reason why it should be happening in some locations like
.
There was an issue with similar effect a couple of snapshots ago. Are all attached screenshots from backups of the world that were updated from a 1.19.4 directly to 1.20-pre2 or were some of them possibly loaded in other in-between versions?
Great, I'm glad it was able to be reproduced! I'm not surprised it occurred in different locations for you, as it seemed to differ in its location each time I was able to replicate it as well.
Yes, this world (and all backup versions of it) were updated directly from 1.19.4 to 1.20-pre2; I did not use any other snapshots or pre-release versions in between.
@unknown When you say "all backup versions of it" does that mean you keep playing in this world in 1.19.4 and updated different backups in different points in time to the snapshots?
Because if the screenshots might have been taken on an earlier backup that could explain why some of the locations in the screenshots are not affected in the world download. (And allow me to stop worrying about the possibility that there might be another cause of this issue 🙂)
Yes, that is correct - when I originally moved the world from 1.19.4 to 1.20-pre2, I noticed the issue and immediately loaded a backup into 1.19.4 to continue playing. Here I was asked if the issue could be reproduced, so I loaded several other backups into 1.20-pre2 and the issue occurred in a slightly different spot each time (in each backup copy).
So, that would lead me to believe that it will occur in different spots each time, meaning it should be fixed for good then!
@unknown Ahh perfect!
I happens to chunks that were partially generated before 1.18, then partially (but not fully) upgraded in 1.19 and then loaded in 1.20-pre2. So when moving around in the backup a bit in 1.19 it might fully upgrade some chunks, so the issue would stop happening for them and partially upgrade other chunks, so the issue could start happening for those.
Anyway, this explains the last bit of mystery for me.
Thank you for the quick replies! 🙂
Have you ever opened this world with mods installed, or with 3rd party programs?
Please attach the world for reproduction.