Minecraft Structure Finder

How the coordinates are computed

Nothing here is estimated or approximated. Every structure position is computed offline from a re-implementation of Minecraft’s own world generation, so it matches what actually generates in game. All 4,150 indexed seeds were scanned ahead of time and stored, so the coordinate table on a seed page is a lookup, not a guess.

One common misconception is worth clearing up: the in-game /locate command does not guarantee the nearest match. It searches in region rings and returns the first viable hit in ring iteration order. Separately, we record a structure’s placement chunk corner while /locate reports its jigsaw start piece — for rotated structures like trial chambers the two differ by 16–19 blocks, and the structure itself is 19×19, so both coordinates land on it. A 16-block difference is not an error.

Java and Bedrock place structures differently

This is the easiest mistake to make with any structure finder. Biome generation was unified in 1.18+, so terrain for a given seed is pixel-identical across editions — but structure placement uses per-edition RNG. For seed 8585 the woodland mansion is at (312, 248) on Java and (280, 104) on Bedrock: same seed number, same terrain, structures over 200 blocks apart. Always set the edition before reading coordinates.