Affected Seed: -4041799379847770715
While traveling across the Overworld's surface in Survival mode, using Eyes of Ender ("EoE") to locate the nearest Stronghold ("SH"), we were led to location (82, 76, 1362). This location is within a generated NPC Village, as is typical/expected in Bedrock Edition. Throwing an EoE at this location resulted in the EoE traveling straight down, so we began a descending spiral staircase at that location.
Upon descending to y=30, a thrown EoE neither descended, nor travelled laterally, but instead hovered at y=32... since the area was near a pre-existing cave, we figured the cave generation might have overwritten most of the expected SH, so we excavated the area around (82, 32, 1362) extensively, extending several blocks above and below y=30... and after an hour, our frustration compelled us to give up.
We returned the next day, and decided to continue our descending spiral staircase, under the assumption that maybe EoE were not properly handling SH generated between the previous maximum world depth of y=0, and the new maximum world depth of y=-64.
During the descent, we tested additional EoE at (82, 18, 1362), (82, 1, 1362) and (82, -14, 1362); these three EoE behaved identically: they all ascended directly back toward (82, 32, 1362) with no lateral movement.
The first Stone Brick, indicating the presence of the SH we had been looking for, was found at (82, -14, 1362). This was the top corner of the ceiling covering the SH's main staircase; the bottom corner of the staircase was at y=-25. Further exploration revealed a completely generated SH.
Linked issues
is duplicated by 1
Comments 3
Since we were already there in Creative mode, we investigated Seed: 3927442492247705184 further and found a second SH to test with. The ceiling of this SH's main staircase at (-8686, 48, 1774); the bottom of that main staircase was at y=38. On a hunch, we dug under the bottom of that main staircase, and tested an EoE; even though the SH main staircase was now above us, the EoE once again descended to y=31... so, it seems, EoE are either hard-coded to proceed to elevation y=31 at their correct x, z coordinates (in which case they are not bugged, but simply not intended to be indicators of elevation), or perhaps the correct y-coordinate isn't being returned via whatever query is being run, causing the EoE to proceed to a default y-value. Either way, we hope that the intended function of the EoE will be comfirmed soon! 🙂
This issue may be related to MCPE-159971, since that Reporter "Ash2276" listed coordinates at a y-coordinate/elevation nearly identical to the elevation that our EoE led us to... possibly indicating a "depth cap" or "maximum depth" that the EoE may unintentionally have. However, it's difficult to know for sure if it's the same issue, since the author of that ticket did not indicate what steps they took in Creative mode. We will investigate that seed, as well, and report back.
Edit: Upon investigating Seed: 3927442492247705184 in Creative mode, I can confirm that the behavior of EoE appears to have the same issue relative to SH generation. The EoE hovers at (-991, 31, 33) but, as Ash2276 indicated, there is no SH present at those coordinates. Digging straight down from there, we encountered the ceiling of the SH staircase at (-991, 20, 33); the bottom of the staircase is at (-991, 8, 33).
Executing the new command "/locate stronghold" yields the result "The nearest Stronghold is at block -990, (y?), 34 (2 blocks away)" ... it seems strange that the y-coordinate is not being returned with that query, but I can only speculate about whether or not that is merely coincidental.