mojira.dev

Yonas K

Assigned

No issues.

Reported

MC-195092 Nether biome generation scrambles biomes in older worlds Duplicate

Comments

Noah
not that I know of, and generally speaking you should be fine with resetting the nether to a pre 20w28a version of it. If you built anything in the nether during 20w28a and 20w29a, that work will be undone, unfortunately. It Might be possible to look for biome data within a backup file of an older version, but I have no idea how to access that, and even then, I'd want to be extremely careful with those types of files. In summary, you ((might)) be able to transfer older biome data to a newer version, but i don't know how it would be done, and toying around with the files of a survival world you invested a ton of time into can be very risky. 

Alright. Firstly, a huge thanks to the mojang staff and Jacob Smith for listening to and helping fix this bug. 20w30a does not appear to be experiencing the problem anymore. However, many people reporting this bug believe that they may have lost their nether forever when updating to 20w28a. I want to offer a solution for them. Provided you haven't built anything in your corrupted nether, there is a way to undo the biome update. Go to your minecraft backups file and find a world save from 20w27a or earlier, and copy the DIM-1 file from it. That is the nether terrain for your minecraft world, old biome data included. take it and replace the DIM-1 file on your current world and you should have your nether before it was corrupted. (Note that it MUST be DIM-1, not DIM1, because that's your data for the End in your minecraft world)

So, if the bug works by the biome distribution info not being saved when updating, does that mean you could fix the bug by copying that information from an earlier version pre 20w28a, saving it, and replacing the rewritten biome data with the older biome data? 

I'm just asking, bc I genuinely don't know too well how this stuff works

Ok. Here's some extra info I have on the bug. It only happens when opening worlds in 20w28a or above so far. So for now, just run a backup of your nether save and play in 20w27a or earlier. 20w29a still expeiriences the bug, and from what it looks like, the issue might not end up getting fixed. Best option, I suppose is to learn how to use WorldEdit tools to change biomes around again, at least to preserve some builds.