/locate: finding structures, biomes and why it sometimes says nothing is nearby
locate searches a bounded radius and gives up rather than looking forever. Here is the difference between structure, biome and poi, and what to do when it fails.
/locate has three forms that behave differently, and one shared limitation people read as a bug.
Three subcommands
/locate structure minecraft:village_plains
/locate biome minecraft:mushroom_fields
/locate poi minecraft:bee_neststructurefinds generated structures. Works on unloaded chunks — it queries the worldgen algorithm rather than the world.biomefinds a biome. Also worldgen-based, but the search is coarser and slower.poifinds points of interest — beds, job sites, bee nests, portals. Unlike the other two, poi only sees loaded and previously-generated chunks, because points of interest are recorded as the world generates, not predicted.
That last distinction is the one that catches people: /locate poi minecraft:home finds nothing in a fresh direction because no beds exist out there yet.
Biome searches give up; structure searches barely do
Both searches are bounded, but the bounds are nothing alike. structure searches 100 placement cells out, and a cell is the structure's own spacing — for a mansion, 80 chunks — so the search reaches about 128,000 blocks. A structure "Could not find" almost always means it cannot generate in this dimension or this world, not that it is too far away.
biome stops at 6,400 blocks. For a rare biome like mushroom fields, the answer often really is that you are too far away: travel a few thousand blocks and run it again, rather than concluding the world does not have one.
Tags work and are usually what you want
/locate structure #minecraft:villageThe # prefix searches a tag — any village type rather than specifically plains. Useful tags include #minecraft:village, #minecraft:ruined_portal, #minecraft:ocean_ruin and #minecraft:mineshaft. Searching a tag is also faster, because any match ends the search.
Reading the output
The result is a clickable coordinate that puts a ready /tp command into your chat box. The Y value is often ~ — structures do not have a meaningful single height, so the command gives you X and Z and leaves Y to you.
Distance shown is in blocks — measured horizontally for structures and points of interest, and as a straight 3D line for biomes.
Dimension matters
/locate searches the dimension you are in. Looking for a Nether Fortress from the Overworld returns the same "could not find" error as a distant search, with nothing explaining why. Same for End Cities.
Structures that cannot be located
A few things generate as part of another structure rather than independently — a trial chamber's vaults, an ancient city's shriekers — and have no locate entry of their own. Every registered structure, including all seven ruined-portal variants, can be located. If a name is rejected as unknown, it is almost always a misspelling of the namespaced id.
Browse every generated structure with its biome and ready /locate command, plus a full Overworld/Nether/End comparison, in the Structures & Dimensions Browser.