Clayton de Oliveira Jr

Had this also in MCPE Android. The previous version (1.20.19) ran perfectly, this version is almost unplayable.

Relates to REALMS-9191, REALMS-9223 and REALMS-9231.

Text disappearing or not saving is a new bug, unrelated to the censoring one. Please refer to MCPE-146229, REALMS-9191, REALMS-9223 and REALMS-9231.

This one looks related to this problem, too: MCPE-141539: Projectiles launched by the player fall through blocks, sometimes into the void, when player moves far away.

It's exclusive about projectiles behaviour, but maybe it's also affecting all entities: when the chunk is unloaded, the entities present in it fall to the void because the terrain blocks aren't present.

@@unknown, in fact its getting worser every new update since 1.17.0.

We have now a sister issue to this nightmarish one we're following here... it's:

It was confirmed yesterday, and have an ADO assigned.

@@unknown , great description! Almost funny, if it weren't really sad in the backgroud.

By the way, interesting your note about the bees not disappearing... bees fly, so maybe this is why they were spared. Did you try to find your missing mobs and entities underground? There are more and more reports of people finding them in caves under the place they were before.

This petition was moved to: https://feedback.minecraft.net/hc/en-us/community/posts/360077420452-3rd-party-shader-support-for-render-dragon

I tried recreating this bug on Android (1.17.32), but I lost just some of the mobs and entities, not all of them (normal behaviour for Bedrock under MCPE-21416). I've also tried force-closing the app while it was autosaving, but nothing abnormal occurred.

We have MCPE on my daughter's iPad too, I will try there later.

@Brian Kastel, do you have access to Realms? You could upload your world there, and then download and attach it here on Jira.

I've found this other bug that seems somewhat related to our MCPE-21416:

MCPE-141539: Projectiles launched by the player fall through blocks, sometimes into the void, when player moves far away.

Description: Player-launched projectiles, for example tridents in a trident killer, will fall into the void once the chunk is unloaded.

So... tridents and arrows are entities also, right?

Hope this helps in the debugging!

So, I've did some experiences and managed to create a reproducible realms test world where 50% of the time I lose mobs, more or less.

It's very simple, just create a 16x16 pen inside a chunk, and fill it up with chickens spawned from breaking eggs. 20 chickens will do. Feed or tag them, and sleep in a chunk near there some days, to replenish the mob cap in the near chunks. Them travel to circa 1000 blocks far, sleep there, and travel back. You'll have lost some of your chickens.

Now it appears to me its related to a defective mob cap algorithm, associated to chunk saving.

In 2 days we will have a Minecraft Live event, and a new friendly or tameable mob will be choosen. I hope this bug is resolved before these new tameable mobs arrive, or this bug will be in the spotlight in no time (just imagine thousands of players losing their favorite allays, glares or copper golems...)

@@unknown , you're probably right about the 3 causes, because if we look at this page's details, we see this bug has 3 tickets open in ADO (Azure DevOps).

But the team is very secretive about this, I tried contacting Mojang and even some Bedrock devs to nil results... I have a hunch they tied this bug's resolution to the efforts to increase Java parity.

Until it's resolved, our main world with all our entities and mobs is kept safe as a backup file.

@David Robinson, your proposed theory is very solid. I even did a test and dug under the place where some of my lost entities were standing, but found nothing in the caves underneath. I've lost some armour stands, but found nothing, even digging until bedrock. I don't know if armour stands can "die" from suffocation, maybe thats the case.

If Minecraft Bedrock had the capability to log specific entities, like Minecraft Java, we should have reached a conclusion by now... My best hope is the Bedrock Dev/QA Team have something like a Developer Version with stronger logging/debugging capablities. Me and my kids stopped playing for 2 months now, just waiting for this bug to be repaired.

I know it's confirmed for 1.17.34, unfortunately, but I had to verify it myself... well, verified. I have a test world (a copy of my own play world) in slot #2 of Realms, prepared with some interacted mobs kept in pens (chicken, villagers, axolotl, etc). This world is 64MB. Made a quick trip to a far village, 1800 blocks afar, slept there and returned to my base. Just one chicken was missing.

As no one here in the comments reported confirmation for 1.17.34, but this version still was listed for the issue, I presume the QA team finally have a test world with the conditions to reproduce the bug whenever they want. So, this is good news (if I'm correct 🙂).

@Mods, Helpers and QA Team: maybe you could address this issue's description more globally, because we already have evidence that it occurs with any mob and entity possible, in any situation (crossing chunk borders or not, named or interacted in any form), and it got even worse after 1.17.11 for some reason.

For the players, I would recommend making backups often, and checking your valuable entities for missing ones when possible.

Reply from @unknown: I don't see how the report description could be any more global than it already is.

Looks like MCPE-21416 for me, too. The mods and the Bedrock/Realms QA team have accepted that MCPE-21416 occurs with any mob and entity possible, in any situation (crossing chunk borders or not, named or interacted in any form), and it got even worse after 1.17.30 for some reason. Make backups often, and check your valuable entities for missing ones always.

Looks like everyone's most hated 4-year old bug, MCPE-21416, is plaguing your world.

If I were you, I would stop wasting energy on mobs and entities in Bedrock, until it's fixed,

Please vote for, watch and comment in MCPE-21416, to help the community gather enough support to have it looked upon by the QA team.

@GoldenHelmet, the nearest village from our base (located at 150, -150) is in 168, 152. As I can remember, we spent 3 game sessions (circa 6h of playing) out of the village, maybe less, because my daughter is building a school for the villagers and spend more time there 🙂
We were inside our base, smelting ores, when outside appeared a patrol without a captain, just 2 illagers. Then, in the subsequent playing session, appeared just the captain. It was a looong time since we saw patrols, so I thought the bug was solved in 1.17.11.
Now I upgraded to .30, if more patrols appear I'll post here.

Replaces the word "por" with ### (Pt_BR). Maybe it confuses with "porn".

Patrols restarted to spawn correctly in 1.17.11 realms.

Just noticed I´ve lost 2 named and fed axolotls, wich were kept in an underground aquarium,  full of water, made of glass and glazed terracota blocks, with sand floor and one wood trapdoor for access. Its dimensions are 4x4, it is totally contained in a chunk, and it is underground (4 blocks below sea level). The Axolotls lasted for almost 2 months there.

—

What you were doing leading up to the mobs disappearing

• I´ve been building a castle over a mountain, saving (sleeping) there. The castle is circa 30 blocks horizontally and 50 vertically far from the point where the Axolotls were.

Single vs. multiplayer, local vs server/realm

• Realm, multiplayer (3 players), being played in Android, iOS and Windows 10 devices, 1.17.x clients.

How far you traveled

• The farest we travelled from the Axolotl, since last time I´ve noticed them, was circa 100 blocks. But no player spawn point was created this far.

How long the current or previous play session lasted

• No session lasted more than 2 hours.

Whether the despawns were near a player spawn point or if you had changed your player spawn point during the session,

• Yes, the despawns were near the player spawn points. The spawn places were changed sometimes.

If you experienced lag or anything else abnormal

• No lag or crash noticed, ever.