Desert Prince

After a bit of testing, it is almost as if the UI is trying to return all uncraftable inventory in the background even when the toggle is set to craftable or even filtered to a specific search. Any changes do not result in quicker opening in the inventory, either in personal or crafting table UI. This only started happening during the last few updates. Makes the game dangerous to play especially when in combat with mobs when you need to quickly open inventory.

Android 13 / LG V60 ThinQ / Realms and Local World Play

Also confirmed for Android 13 on LG V60 ThinQ.

After opting into Realms Stories, any attempt to open the Play screen will result in game app minimizing / exiting. Cannot click any of the settings buttons or start play on a world / realm before the game does this. Force exiting the app and restarting the phone has not effect on this behavior.

UPDATE AND WORKAROUND:
I WAS able to quickly click the CREATE world button and create a local world without experiencing a crash, so this definitely is an issue involving the app's ability to communicate with realms after opting into the Realms Stories feature.

Once I exited the local world game, again, I did not experience the crash. I immediately tested to see if I could enter my realm world and had no issues joining that world. When I exited that realm, I also did not get the crash. I only happens when you open the app fresh and click on the Play button.

If you click to play a local world (really fast), you can successfully open that world and avoid the crash. This is the only workaround that I can offer players to get into their actual realm worlds.

Once you are actually joined to one of your realm worlds, you can successfully OPT OUT of Realms Stories, thus temporarily fixing the issue until the Realms Team issues a bug fix.

This bug needs investigation. I have a zombie spawner within a deep dark / abandoned mineshaft that is Y -30. It should be virtually impossible for any cured villager to detect any profession block that is not the one I place beside the curing area. However, every villager that I cure is a different profession than the block placed. If a matching block to that profession is placed, the cured villager does not link to it / lose profession when the block is broken.

This is so far away from the only village that it is on a completely different 3/4 zoomed map. I wish there were more debugging information available to players / realm owners to confirm exactly where it thinks it is linking to for a workstation block.

This is a single player world that I run on a 2 person realm for convenience of backups. So I know nobody has other villagers anywhere nearby.

Confirmed that there are no issues testing resource and behavior packs locally on 1.19.20 Bedrock on PC, but the Owner gets stuck in the loop described above when trying to apply packs to a realm slot world. Even closing and exiting the app after the upload message is complete does not result in successful application of the pack.

Recommend this be escalated to Cornerhard and the Realms Team. This is a new bug that wasn't happening previously in the last update. I know the realms team made changes to rendering distance, so this may or may not be related to any changes made on the backend.

Affects 1.19.10.

Just went through a lot of hassle trying to configure a wandering trader to buy illager banners just to discover that he won't accept those from the creative inventory while testing.

Glad to know now that this is a bug and not something that I am doing wrong.
(attached capture).

See: minecraft bug - illager banners not stackable.png

On my realm, I have a long-time player who can suddenly not see my messages, but I can see his.

Only if I use /tell to whisper to him or all players can he see my messages.

I will test with /me , etc., to see if that also works until a fix is put into place.

I am playing on Android Bedrock and the other player on PC Bedrock.

On Realms+, another workaround that sometimes works is to have the player in the spawner chunks log out and back in. That sometimes performs a temporary fix. Noticed that this bug seems to occur more often in chunk areas where spawners are close enough to be set up as a double farm.

Sometimes the logging out/in trick only causes the spawn cages to re-ignite, showing the spinning mob inside and the flames, but still does not generate spawns.

This also affects mobile users for 1.17.11 on Android 11 as well as Windows 10 users not using full screen modes. This bug has been persistent for quite a while. Users on mobile should expect to be able to toggle apps without being kicked from the game.

Confirmed that this is affecting 1.17.11 on Android 11 and Windows 10 Bedrock. Must log out and in to be able to remove boots.

This issue is currently affecting 1.17.11 on Android 11 and PC Windows 10 Bedrock. If a turtle egg is placed down within line of sight for a zombie or zombified piglin, it completely ignores it. Difficulty is set to Hard on the realm with no cheats activated or add-ons.

Still affects regular release 1.17.11 (android). Surprised this was not resolved in this update. Accessibility issue bugs should always have top priority.

Confirmed that TTS for UI and for Chat Messages have been fixed in the current Beta 1.17.30.20.
Tested on Android 8.1 on LG Q6.

See the other new tab on the 3 slot view that says manage realm. That is where backups are shown.

As of the 1.17.10 minecraft bedrock update, the chat text to speech accessibility setting appears to be broken on Android 11 LG V60 also tested on Android 10 LG GX8 with same results of text to speech not working.

All was fine before the update. All setting toggles and volume levels have been confirmed to not have changed only the functionality has stopped in the app.

Tested on windows 10 as well. Only if Text to Speech for UI is active will the app read chat text on windows pc bedrock. If just turned on for chat text, it will not read the chat feed. Same results when texted on Android 11 on Samsung Galaxy Tab S5e.

Hope this is addressed ASAP with a hotfix. As a special needs user, this feature is VITAL.

This change is as bad if not worse than the sim distance change forced on realms. Give the OP the ability to control this from a pre-populated list of options on the game settings. This goes against the premise of taking away mechanics / undoing features that Mojang has always upheld. Mob caps do not need to be the same on Bedrock as Java. Bedrock has often been developed to make it MORE challenging than Java. I hope this change is undone. How it got recommended by anybody is mind-boggling. This was a non-issue that they were trying to fix.

The proposed fix will NOT work on realms. This was a huge issue when they tried to increase the sim distance and had to walk that change back. Realms infrastructure needs to be addressed before that can be done. It also broke a lot of farms.

DON'T LET THIS BUG GET INTO PRODUCTION RELEASE!

I am experiencing this exact bug when in the newest beta on Bedrock Windows 10 - Beta 1.17.10.22.

I am completely unable to create a world with the exact same valid seed that is from our current bedrock world.

Instead, it generates a random seed ID. I have tried multiple times. This is very repeatable in the beta version.

Really frustrating for us who are trying to test if diamond ore generation has in fact been fixed in the newest beta.

This was not a problem at all with the 1.17.0 initial public release from June 8, 2021. It must have slipped in during the beta development phase.

I was able to recreate the seed in the non-beta version 1.17.0 with no issues.

Note that on PC Bedrock in the mojang games folder, the snapshots and the .mc files are being generated, they just aren't being posted to the feed. So at least part of the process is working, just not completely.

Probably more feature request, but the Vanilla game / realms console needs to include support for pruning world chunks across each dimension. As not being able to prune is the cause of large world file sizes that are the root cause of performance and world corruption issues.

Mojang needs to be the source of supported tools. I am sure that I am not the first person to mention this type of request. Community Managers should be looking into these types of tool development and recommend they be pushed higher up for development.

Confirmed that after 1.16.100 update on Bedrock android, ghasts can still blast basalt blocks causing them to break when hit by a ghast fireball. Tested on both local gameplay and on realms.

A short time after my comment post, Mojang announced a new beta release where this behavior is apparently fixed. We'll have to check again after next full release/hotfix, whichever route they go on this item.

A similar issue of mobs flying out of mob farms when hit by other mobs falling down upon them is occurring. They glitch out visually from the confines of the 1x1 chute area and then will bounce back when the player walks into them and sometimes will just bounce back on their own as more mobs fall down into the chute. The glitched mobs have no hitbox. Striking them with an arrow just passes through them. I've witnessed this happening to both skeleton and zombie farms. This only began with the Bedrock 1.16.100 release.

The Villager glitch is also happening. One appeared to be buried under the floor blocks, but did not suffocate and was fine in the morning when they woke up.