When non-cave biomes meet, they tend to overlap with each other, meaning that a block at the edge of a taiga could be a taiga at the surface, but be a forest 10 blocks up if the taiga meets a forest.
This is different from the non-cave biome overlap issue found in 21w39a and before. In these versions, the overlapping biomes extended far into the "original" biomes, while in 21w40a, this overlap only occurs at the biomes edges. This means that if you were to walk a few blocks into the aforementioned taiga, it would no longer overlap with any non-cave biomes.
Although this is a relatively small bug, the fact that, according to the patch notes, 21w40a tried to fix non-cave biome overlap leads me to believe that this is unintentional.
To reproduce:
Create a creative default world with the seed -8976640259792665025.
Open F3 menu.
Run "/teleport @s 44 64 470".
Fly upwards until you reach the build limit.
The biome alternates between old growth spruce taiga and beach.
Expected result:
As you fly upwards, the biome stays the same from the ground to built limit.
Linked issues
Attachments
Comments 9
Hmm, this might actually be a different behavior, this can be reproduced very consistently unlike in 1.17 which was pretty rare. This is very noticeable on rivers as can be seen in the attachment. Can confirm here.
[media]
In those river-color spots, there should be plains, but instead there is a river trying to overlap it.
Duplicate of MC-173878?
Yeah, the nether has no special biome behavior, never has; since 1.15 this has happened due to vertical biome blending, caused by the addition of vertical biome support. It is the same "issue".
I was just basing myself on the resolution of that ticket, i'm aware nether biomes weren't any different than overworld biomes. Either way maybe it is a duplicate but i don't think that ticket was resolved correctly.
Thank you for your report!
We're tracking this issue in MC-173878, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Apologies for not responding to your questions. I had forgotten about this bug.
I feel that this bug may have been resolved incorrectly. I looked at MC-173878 and I noticed that the issue mainly pertains to Nether biomes. You clarified here that the bug applies to both the Overworld and the Nether, but since the issue uses pictures of Nether biomes, the moderator who marked it as "works as intended" probably assumed it was referring specifically to Nether biomes.
Additionally, while the Nether's biome behavior is not unique, the patch notes for 21w40a mentioning the removal of height-changing non-cave biomes leads me to believe that even with vertical biome blending, non-cave biomes are not supposed to change with height.
Biomes overlapping at their edges was something that happened even on 1.17, and also on servers (MC-209558), couldn't find a report for this happening on singleplayer though.