This is a duplicate of MC-138887 and can be marked as such.
Playing on a windows computer, version 1.20.5 with experimental features enabled.
Using the /locate command to find structures does not always reveal the nearest one (see images below). In multiple instances, moving only one block (or less) will cause the command to find a structure that is hundreds of blocks further away.
Steps to replicate: Repeatedly use /locate while moving around. At some point, the distance to the nearest structure may jump up/down, indicating that a structure other than the nearest one is being returned (for example, in the third set of images, the player should only be 469+1=470 blocks away from the nearest ruined portal, not 1520).
Expected behavior: Using the /locate command would return the nearest structure.
Seed: 898702134
Linked issues
Attachments
Comments
COMETC2021A1
kelianor
Duplicate of MC-138887
DrD314
Ah, thank you for pointing that out. I can't believe I didn't see it!
Arisa Bot
Thank you for your report!
We're tracking this issue in MC-138887, 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.
Can confirm!