-
Bug
-
Resolution: Works As Intended
-
None
-
Minecraft 18w06a, Minecraft 18w07a, Minecraft 18w07c, Minecraft 18w08a, Minecraft 18w08b, Minecraft 18w09a, Minecraft 18w10a, Minecraft 18w10b, Minecraft 18w10c, Minecraft 18w10d, Minecraft 18w11a, Minecraft 18w15a, Minecraft 18w16a, Minecraft 18w19a, Minecraft 1.13-pre1
-
Confirmed
We wanted to do changes to the worldgen system to make it simple/clear and possible to datadrive it in the future.
While doing so we noticed at a certain moment that we generated some areas of the terrain differently than before (not meaning the things placed as decoration, but the actual shape of the land). It took a while to figure out why, but it turned out that in the old code, there had been a bug from the beginning. We forgot to reset the seed of a random when we merged rivers and the biomes.
In the new code there was no way to reproduce this wrong behavior and this is why [this issue] has been resolved as Working as Intended.
We're not happy that we ended up changing the world where the intention was not to. We found no way to keep the bug while also keeping the new functionality we've added. So we chose to keep the new bug-free implementation and hopefully be able to offer datadriven biome definitions in the future because of it.
– grum in this Reddit comment
The new world generator changed some biome and landscape generation compared to 1.12.2. Examples:
- is duplicated by
-
MC-125057 More or less inconsistent terrain generation in comparison between Stable 1.12.2 and Snapshot 18w06a
- Resolved
-
MC-126345 Flower Forests are Erased in Worlds Generated Pre 1.12 in 1.13 Snapshots
- Resolved
-
MC-131025 Terrain generation sometimes generates different land biomes between 1.12.2 and 1.13
- Resolved
-
MC-131986 Terrain generation boundaries
- Resolved
-
MC-133433 World gen Inconsistency
- Resolved
-
MC-137007 Terrain bug in 1.13.1
- Resolved
- relates to
-
MC-124950 Cave generation is different from old generation
- Resolved