How Eye of Ender triangulation works
One Eye of Ender gives you a heading but not a distance. The calculator treats that heading as a ray starting at your X and Z position. A second throw from another position creates another ray, and the forward point where the two rays meet is the estimated target of the eye.
Minecraft yaw does not use the usual compass convention: 0 points south along positive Z, -90 points east along positive X, 90 points west and ±180 points north. The calculator converts each yaw to a direction vector with dx = -sin(yaw) and dz = cos(yaw), then solves the two-ray intersection.
The result is an estimate of the stronghold location targeted by the eyes, not a promise that the End Portal room is directly below that block. Strongholds cover a wide underground area, and small aiming errors can move a distant intersection. Confirm with another throw near the result before digging.
Reading X, Z and yaw correctly
On Java Edition, stand still, center the crosshair on the floating eye and open F3. Read X and Z from the XYZ line and use the first rotation number on the Facing line as yaw. Record it while the eye is still traveling horizontally, not after it begins to sink. On Bedrock, use the coordinate and rotation display while aiming at the eye, following the same yaw convention shown above.
Check the result before digging
Distance from the world origin can be a useful sanity check because current Java strongholds are distributed in rings, but it is not a universal validity rule: outer rings, Bedrock generation and older versions differ. If the result looks implausible, lies behind a throw or comes from a very narrow crossing angle, recheck the signs and take another measurement. Near the estimate, an Eye that turns back or dives downward is stronger evidence than the calculator alone.
How to triangulate a stronghold
- Stand in an open area, throw an Eye of Ender, center your crosshair on its travel direction, then record X, Z and the first rotation value shown on the Java F3 screen.
- Move at least 100 to 200 blocks sideways, not straight along the first eye path. Throw again and record the second position and yaw. Highly precise speedrun measurements can use a shorter baseline.
- Enter both readings above. The calculator treats each throw as a ray and finds their intersection. Dig safely near the estimated X and Z rather than straight down.
Why the angle between throws matters
Tiny reading errors grow over long distances. A crossing angle around 5 degrees or more is useful with a carefully read decimal F3 yaw; below 2 degrees the estimate becomes sensitive to aiming and rounding. For a final check, take a third reading closer to the estimate.
Java and Bedrock support
The geometry works in both editions. Java exposes yaw directly on the F3 screen. On Bedrock, use any coordinate and facing display that gives a numeric yaw, keeping the same Minecraft convention shown beside the inputs.
Stronghold triangulation FAQ
Where do I find the Eye of Ender angle in Java Edition?
Open F3 while standing still and looking directly at the floating eye. Use the first number on the Facing line, not the second pitch value. Read X and Z from the XYZ line.
Why are two Eye of Ender throws required?
A single throw defines only a direction and could point to any distance along that ray. A second direction from another position provides the intersection needed to estimate a location.
How far should I move between Eye of Ender throws?
For an ordinary F3 reading, move roughly 100 to 200 blocks sideways. Precise speedrun methods can use about 17.5 blocks, but they require much more careful angle measurement. Angular separation matters more than distance alone.
Why is the estimated point behind me?
One yaw sign is probably reversed, a coordinate was mistyped, or the eye direction was recorded while the crosshair was not aligned with its flight.
Is the result the exact portal room?
No. It estimates where the two eye paths converge on the stronghold. Terrain, measurement error and the size of the structure mean you should search around the result.
Does this work in Minecraft 26.x and older versions?
Yes. The line-intersection calculation is version independent and remains useful in current 26.x releases and older Java or Bedrock worlds.