"/locate" doesn't work correctly in some certain conditions. "/locate"指令在特定情况下出错。

Picture 1 shows a pale garden which “/locate“ leads me in a world updated from 1.20.6. The chunks were already loaded in 1.20.6, so there is no pale garden. But “/locate“ leads me there because there should be a pale garden in the same seed in 1.21.7. Picture 2 shows a new world in the same location in the same seed.

This means the method which “/locate“ uses depends on the world’s seed. It doesn’t directly look for a biome. If a world is updated from an early version and has loaded many chunks, “/locate“ will lead the player to a wrong place.

图一是“/locate”指令在一个从1.20.6升级而来的世界中找到的苍白之园，这里的区块已经在1.20.6中加载过，所以没有生成苍白之园。但是“/locate”指令说这里有苍白之园，因为在1.21.7的相同种子中，这里会生成苍白之园。图二是在1.21.7中用相同种子新生成的世界的相同坐标的位置。

这就意味着，“/locate”指令并非直接搜索生物群系，而是与世界种子有直接关系。如果在一个从早期版本中升级而来且已经加载了很多区块的世界中使用该指令，它就无法找到正确的位置。