/locate and /locatebiome does not provide y-values
When you use /locate or /locatebiome, it always shows the x and z positions of a structure, but never the y position. This is important for certain structures, mainly ones that generate underground.
Linked Issues
is duplicated by7
MC-214924/locatebiome command has no y coordinate setDuplicateMC-239009Y coordinates not given by /locatebiome when finding a cave biomeDuplicateMC-243023When teleporting to a mountian you spawn inside of itDuplicateMC-249880/locate command coordinates teleports underground in the right placeDuplicateMC-252757/locate says ancient city is where one isntDuplicateMC-259298If you teleport to a location without the chunks generated already, you are teleported to a strange areaDuplicateMC-267131The position of Trial Chambers found using locate does not have y-coordinatesDuplicate
Created Issue:
/locate cannot specify y-values
When you use /locate, it always shows the x and z positions of a structure, but never the y position. This is important for certain structures, mainly ones that generate underground.
![[Helper] Jack McKalling](../../../data/avatars/users/92859.png){kind=small}
/locate and /locatebiome cannot specify y-values
When you use /locate or /locatebiome, it always shows the x and z positions of a structure, but never the y position. This is important for certain structures, mainly ones that generate underground.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
is duplicated by
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
is duplicated by
![[Mojang] Moesh](../../../data/avatars/users/10122.svg){kind=small}
is duplicated by
is duplicated by
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
is duplicated by
/locate and /locatebiomecannot specifyy-values/locate and /locatebiome does not provide y-values
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is duplicated by
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
You are correct, this is actually a duplicate of MC-206286
This happens because the command only searches for biomes relative to your current height position, which is tracked in MC-206286 already.
As we know, /locatebiome command doesn't specify y-value, which is intended (see MC-206286). However, the command doesn't correctly find the new introduced cave biomes (as they are 3D biomes distributed underground). This doesn't happen with the regular surface biomes.
This leads to a number of issues where the command doesn't search accurately for the nearest biome when the player is on different height levels, and is inconsistent with how /locate works, as that command successfully finds a structure independent of your Y position.
Note that this report is not implying the command should specify the Y coordinate, but to locate the nearest biome regardless of your Y position. Similar to /locate.
Expected result
/locatebiome command would find the nearest biome, regardless of the player's Y-position, like how /locate works.
Observed result
The command doesn't always find the nearest 3D biome, instead it searches horizontally depending of the Y-level the player is at, leading to situations where the command locates the biome very far away or can't locate it at all.
How to reproduce
- Create a world, search for a lush caves or dripstone caves biomes on your current level.
- Now fly to a really high Y-level (i.e. above 180) and search again.
- On most cases, the command locates a different cave biome, or is unable to locate one.
Thank you for your report!
We're tracking this issue in MC-206286, 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've read every duplicate of that issue before making this report, that one is implying what the original ticket was about, which is y-position not specified, except maybe MC-238479 which will be more accurate for this one.
MC-206286 didn't really add more info, just a comment about how it could cause problems with 3D biomes. Those duplicates were related to how the command doesn't search for different height levels and were made before the original got closed, so i've waited until it got either triaged or resolved and then created a new one worded differently.
Thank you for your report!
We're tracking this issue in MC-206286, 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
Please don't submit multiple issues in one report.
The second issue that you are describing is MC-206286, but I'm not sure about the first one.
I took a look at the issue you linked and it is totally different
Even though the issue describes being unable to specify a height, the fact that biomes can only be located at the player's height is considered to be a symptom of that same issue. See MC-236680, which describes your exact issue - it got merged into MC-206286.
It uses ~ for y, pal, no y coordinate is returned by locate. It's your own y coordinate.
Duplicate of MC-206286.
Thank you for your report!
We're tracking this issue in MC-206286, 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.
Thank you for your report!
We're tracking this issue in MC-206286, 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.
Duplicate of MC-206286.
Thank you for your report!
We're tracking this issue in MC-206286, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
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.
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
Thank you for your report!
However, this issue is Working as Intended.
See MC-206286.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Does MC-206286 describe your issue?
Duplicate of MC-206286, no structure returns a y coordinate.
Thank you for your report!
We're tracking this issue in MC-206286, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
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 (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 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.
This has been around since /locate was added, as well.
Can reproduce
this is intended behavior. How high it is generated is based on terrain (indirectly via world seed), not directly by world seed.
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Can confirm in 21w37a
Now that 3D biomes are a thing in 21w37a, this can lead to a number of issues where locating cave biomes might not send you to the nearby one (or even, fail to locate it) depending on your y-position.
And due to
MC-236619, the command can send you to "floating" biomes that don't correspond to the surface.Affects 21w39a
Can confirm in 21w40a.
This is still an issue in 21w41a
This got marked as Works As Intended.