When you take a world from 1.16.4 to 1.15.2 the seed automatically changes to 0. Even if you optimized the world. Also one time I got a Version with a really weird light bug. It keeps the seed 0 even if you take it back to 1.16.4 and optimize it again.
Attachments
Comments 7
And because I'm dumb, I made this in my Redstone testing world with hours of work, where I found another bug, that I tested in different the 1.15.2 Version, and now that world is seed 0 instead with everything deleted.
I hope I still have a backup.
It is difficult enough to support the current version. They do not have the resources to support every previous version of the game.
Heyo, think I know why. When your allocated RAM is full/nearly full in Minecraft and/or Java, it loads the worlds chunk incorrectly. For proof, if you actually rejoin the world, the chunks may change. Not sure about the Seed-0 though, might be the same reason.