I've create a data pack which uses advancements to detect when a player is in a certain biome, and perform certain actions if they are. Recently while testing however, I found that the data pack will not trigger any actions if the player is above the build limit or below the bedrock layer (bottom build limit).
After checking on the f3 debug screen, I realized that there are no biomes listed when you are above y=319 or below y=-63 in the overworld. I also decided to check if the same occurs in the nether and end, and it does (only difference is that it occurs above y=255 and below y=0)
What I expected to happen:
Biome below build limit/ above bedrock would extend past build limit/ bedrock layer
What actually happened:
Biomes extend from y= -63 to y=319 in the overworld, but cut off outside of this range. Biomes extend from y=0 to y=255 in the nether/ end, but cut off outside of this range
Steps to Reproduce:
No Biome at Height Limit (overworld) **
Create a new Minecraft world in 1.18.1
Fly or build up to y= 319
Jump on top of the block at y= 319
Biome in f3 debug screen does not show any biome
No Biome Below Bedrock (overworld)
Create a new Minecraft world in 1.18.1
Fly or dig down to y= -63
Go below y= -63
Biome in f3 debug screen does not show any biome
No Biome at Height Limit (nether/ end) **
Create a new Minecraft world in 1.18.1
Go to the nether/ end
Fly or build up to y= 255
Jump on top of the block at y= 255
Biome in f3 debug screen does not show any biome
No Biome Below Bedrock (nether/ end)
Create a new Minecraft world in 1.18.1
Go to the nether/ end
Fly or dig down to y= 0
Go below y= 0
Biome in f3 debug screen does not show any biome
Linked issues
relates to 1
Attachments
Comments 4
Um, that report is different...
That says "the void biome is not used below the world", this says "when above/below the world build limit (eg walking on the top blocks in the world) you are not considered to be in ANY biome, and won't trigger advancements for entering biomes that are right below/above you".
The former is a change request, the latter seems an actual issue.
Thank you for your report!
We're tracking this issue in MC-214855, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-214855) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.
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