Talk:Commands/locate

Locate command doesn't locate nearest things
In exploring the "Coastal Village" preset seed in Bedrock Edition 1.11, I noticed that the /locate command isn't actually locating the nearest object to you. It appears to be using taxicab distance rather than Euclidean (as the crow flies) distance. Example: The stronghold found by  is clearly farther away. It's the closest only if measured by taxicab distance.
 * 1) Use the seed picker to generate Coastal Village in creative mode. You will spawn at 960,4.
 * 2) From that location, the   command says the nearest stronghold is at 578,882 - about 950 blocks directly south-southwest.
 * 3) However, there is another stronghold at 1489,586 - only 780 blocks southeast.

Can someone confirm this is how the command works? If so, it feels like a bug to me, because the whole reason for using the command is to find something near. ~ Amatulic (talk) 06:08, 29 April 2019 (UTC)
 * Update: I reported this as a bug at https://bugs.mojang.com/browse/MCPE-45526 ~ Amatulic (talk) 06:30, 29 April 2019 (UTC)
 * Another update: I have verified that /locate is correctly calculating Euclidean distance, not taxicab distance. However, /locate completely misses some structures. Even when you are directly overhead the stronghold in step 3 above, the /locate command identifies the stronghold found in step 2 instead. ~ Amatulic (talk) 07:05, 3 May 2019 (UTC)