Steele

This issue continues to persist in hotfix 1.19.21 

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.

I am also having this exact issue, as originally reported by Speedy, as of v1.19.2 on Windows 10 Home edition (OS Build 19043.1766, for what it's worth).  IMO, MCPE-154319 does not describe the issue. 

There are no pop-ups containing an error message.  There are also no apparent error messages related to the Marketplace, nor related to ownership of the affected resource packs.

All Marketplace-sourced resource packs stay Active until, at a minimum, the Minecraft client is closed.  Upon closing and restarting Minecraft, regardless of whether launched via the Minecraft Launcher, or from the Minecraft Bedrock shortcut:

• all mods obtained via the Marketplace lose their Active status and may be found in Settings > Global Resources > My Packs, where they need to be individually re-set to Active status

• all non-Marketplace mods in Settings > Global Resources > Active, such as from bedrocktweaks, appear to perform as expected and their Active status correctly persists between Bedrock client sessions

This issue is incredibly frustrating, and would likely be confounding to newer users with Marketplace purchases since their resource packs would simply appear to stop working without warning, with no obvious (pop-up) error messages. 

Is there a .log file (or something in a similar vein) that we can enable, which would use to help further inform the troubleshooting process?

I'm on PC... wonder if you're seeing a different symptom on PS4.  Hrm.

Update:

Okay, I shut down and restarted the server, and waited until another day cycle, and the villagers have ALL returned (unnamed & those with prior name tags applied)... so perhaps this is indeed related to MCPE-101202; it did not seem that way initially.

Waited for another night cycle, and watched roughly 20 villagers slingshot themselves out through a wall, literally into the sunset (it appears related to whichever direction they are going to try to get into the bed - if they enter from the east side, and thus move west when they adopt the sleeping position, they accelerate toward the west).  I guess that confirms it as 101202, though when I slept in a bed to force time advance to day, the villagers in question did NOT reappear.  I had to log out, and then rejoin the server (which I left running) in order to make the villagers reappear in the village.

Another Update:

After going through another natural day/night cycle, I am now hearing villager job block sounds even when the villagers do not show up for my client, and I can not interact with them.

No, Umija... MCPE-101202 does not describe the issue as I saw it, because the NPCs, what were left of them anyway, were stable in their beds while asleep.  I also did wait for a full day cycle to see if they reappeared, and kept my character near their job blocks hoping to observe the sound of invisible villagers accessing them, all to no avail. 

However, if you look at the bottom row in the pic I've attached, the first and second villagers from the left are not centered on their beds, and in the top row there appear to be two instances of "couples" who have somehow taken up residence in the same bed.  I've never seen either of those behaviors before, prior to firing up the server after patching to 1.16.100

I also walked outside our villager compound, which is fully lit up, checked underground and aboveground in case they had somehow been teleported, and I could find no sign of them.  I will try to check with a world editor to see if there's any trace of them at all; perhaps I'm missing something obscure, but I believe that I've searched the surrounding chunks (with my character, in game) fairly thoroughly.

Now having the same issue on a self-hosted family server, since updating to 1.16.100.  We have (had) a village of 30 beds and 30 villagers.  Now over half the villagers are missing, and I noticed some are trying to sleep in the same bed (pic included, notice there are two in the top row trying to sleep together).  This was not an issue prior to the patch; they all identified, claimed, and pathed to their own beds.

I would appreciate if you guys looked into the problem because this is a mistake on your part, not ours. Nothing is wrong with my world and so many other people have the same problem. This makes the game unplayable and lots of time wasted, plz fix your bug.

Yes I’m sorry I don’t have a realm subscription

Will I need a realm for that?

And what would I be investigating or what should I investigate?

Same Leonardo