For structures that always generate on the surface or seafloor, this shouldn't be an issue. The y coordinate isn't shown for every feature. Since those structures are small, often buried, and can be offset 10-20 blocks from the chunk center, you might have to do some searching/digging to find them. Various other structures such as villages and igloos can sometimes fail to generate in-game as well, but this should happen far less frequently than for the features mentioned above.įor some features like fossils, ruined portals and trail ruins the app currently only points to the center of the chunk they're generated in.

Desert & Jungle Temples on Java Edition 1.18+.

Amethyst Geodes (near caves, mineshafts, etc.).

End City Ships, and End Cities in general on Bedrock Edition.

Many features are not 100% accurate, i.e., locations can be wrong or missing. Near coasts, ocean and river biomes often have land, while land biomes can be underwater. This is not a bug, but because the map shows the underlying biomes instead of the exact terrain. The coastlines for versions 1.18 and above don't match up perfectly. Always select the version that was used to generate the chunks you're looking at. If you started your world on an older version, you'll have to switch between the versions in the app.

(for slime chunks) you didn't wait long enough, since they have a very low spawn rate even in slime chunks.

you used mods or resource packs that affect world generation.

you selected the wrong edition or version (the one used to generate the region you look at).

you entered the wrong seed or coordinates.If your in-game world doesn't match the map here at all, it's most likely due to one of the following:

If none of the below helps, please report in the comments and include your seed, platform and version, and coordinates.

Minecraft maps overgrown city