The distribution of biomes in the Nether changes everytime the game is loaded.
SatDog92 opened this issue ยท 5 comments
**Versions: Minecraft 1.16.5, byg-1.1.10, Forge 36.0.15. EDIT: Also on Forge 36:0.42 **
**EDIT: Fabric is also affected: Fabric 0.11.1 (with Fabric API 0.30.3), byg-1.1.5 **
**EDIT2: This still happens on byg-1.1.11, Forge 36.0-58, LOL! **
Describe the bug
The distribution of Nether biomes changes everytime the GAME, not the world, is loaded. This doesn't happen in the Overworld and in the End, as their biome distribution is determined by the seed as intended. This happens with no other mod installed. On Fabric, this is less erratic: for example, i noticed that on seed "-4984821034741306506", the spawn Nether biome can be either Glowstone Gardens or Subzero Hypogeal, while on Forge, the biome always changes.
To Reproduce
- create a new world, go into the nether and quit the game (exiting the Nether doesn't make a difference).
- open the game again, open the same world, travel to unloaded chunks in the Nether (or create a new world with the same seed), and witness the change to the distribution of the biomes.
Obviously, to make an example: i created different worlds in order to find a seed with a spawn that suited my preferences, and eventually found one with the witchhazel tree biomes and the Subzero Hypogeal one. When i went, recreated the world on Survival, and finally got access to the Nether, the biome was Magma Wastes instead. At first, i thought it was a problem of seed or mod conflict, but eventually found out that, in fact, the biome distribution changed everytime i deleted all the chunks i generated previously, even if no other mod (including optifine, so only the byg mod file in the mod folder) is installed. As seen in the screenshots, this is kind of game breaking and makes the Nether almost unexplorable.
Expected behavior
The biome distribution should be fixed and determined by the seed, as anyone would expect.
Screenshots/Videos
The screenshots below show the effect of this bug: basically, it's as if terrain was sliced through the horizontal axes.
2021-02-17_22 50 25
2021-02-17_22 51 01
2021-02-17_22 51 14
2021-02-17_22 51 28
2021-02-17_23 17 22
2021-02-17_23 17 37
2021-02-17_22 49 13
2021-02-17_22 49 23
2021-02-17_22 50 17
Additional context
None
Logs
Forge:
Logs after entering the Nether with no chunks generated and closing the game afterwards.
latest1.log
debug1.log
EDIT: Recent Forge version log:
debug-2.log
2021-02-20-2.log
EDIT2 : Forge 36.0-58 log:
before.log
Logs after opening the game again, and travelling to ungenerated chunks in the Nether of the same world (or after creating a world with the same seed).
latest2.log
debug2.log
EDIT: Recent Forge version log:
2021-02-20-1.log
debug-1.log
EDIT2 : Forge 36.0-58 log:
after.log
Fabric:
Logs after entering the Nether with no chunks generated and closing the game afterwards.
latest1.log
Logs after opening the game again, and travelling to ungenerated chunks in the Nether of the same world.
latest2.log
What a bummer, i just started a new world finally but i can't play this if the Nether changes biome distribution everytime i open the game.
Same happening on my end ... and, I was going to say how very much I love the music you have added to the nether, or, at least I am assuming it is you. WOW, very temple of Time esk! LOVE
Anyways, to add to the above, this happens on both dedicated server and single player worlds, with only byg 1.1.1.0, and forge 1.16.5-36.0.42.
