X1Crafts

I can also confirm that as well. It seems this is another band-aid fix as the real cause of this issue is a problem with items that have format versions higher than 1.16.100 as mentioned by AkiraYukino.

Can anyone confirm that the fix for this issue also fixed MCPE-172710?

Any hope on this issue being fixed due to the pushback from MCPE-231719?

I’m not sure how this is working as intended? Like clearly mentioned in the details, images can still be attached via workarounds and they continue to be accepted by moderators, so the issue that should addressed is: why the button to directly attach images is missing?

I tested this today on Google Chrome (Version 143.0.7499.150) and the button is still gone despite evidence that it existed early on at some point. I think this issue should be reopened for consideration because clearly, a button used to access a critical feedback tool disappearing randomly some day does not seem normal or intended.

Does anyone have a copy of LightKnight’s behaviour pack fix for testing purposes? I can’t seem to find it as an attachment or link in the Customer Portal (logged in view) or on the Public Issue Navigator (logged out view).

I suspect if it was an attachment (based on the context of the comments above), then it wasn’t transferred over during the bug tracker migration.

Likely related to MCPE-190544.

Clearly as shown through Jenny’s video, the “slight delay” is not as slight as claimed. This issue needs to be completely fixed, not pushed aside or covered up with a band-aid like the pointless server authoritative movement changes from 1.21.60 which we are still suffering from.

All this does is make players want to use the new mounts less and makes horses more useless than they already are by making them basically usable in the early game. I’m not sure what supercomputer the developers are playing on, but when testing on an Xbox One X, a platform officially supported by Bedrock, the delay is makes controlling mounts feel very imprecise and sluggish.

It seems like boats are also affected by the switch to server authoritative movement as well? Because turning left/right is very slow with visual signs of stutter and the feel being completely off from before 1.21.130.

Here’s an example in ibxtoycat’s video at 5:24.

Please reopen this bug report because if you actually play the game, you can clearly see that the delay is far from “slight”. Horses and other mounts are now completely unusable.

Horses float in water while ridden on Java too, how come they were able to implement this feature without compromising input latency and usability?

After testing I can confirm. The Minecraft Launcher has the same issue, but because it has no real dark mode, it isn’t that big of a deal.

The location of the “Trial Chambers” template, can be found at the bottom of the “Seed Templates“ page as shown in the image below (for viewing and ease of use purposes):

I have experienced this as well, its very annoying.

Can confirm. This has been an issue for years even before 1.21.111 (at least for me). I thought I was alone in experiencing this, but I guess not.

If the game needs to load a resource pack in order to function properly, then that loading sequence should be moved into main loading screen that shows when the game launches so that the player has instant access to the main menu without being delayed.

Most likely similar to MCPE-229551.

Strangely, when I was first testing the fix of MCPE-227846 in the 1.21.130.26 Preview to confirm that the issue was actually resolved, one of my tests was to repeatedly change the system theme in Windows 11 while the game was actively running and I did not encounter this issue.

Are you sure that you’re not using a Custom color theme (not exclusively Dark mode or exclusively Light mode)? For example, your default app mode couple be set to “Dark” while the default Windows mode is set to “Light”. Right now, I can’t confirm because the attached screenshot is not translated to English, and I can’t access my game at the moment to try reproducing the issue again, but I really don’t want to see a regression of MCPE-227846, my post, considering all the incomplete fixes being shipped out in recent times.

Likely caused by an incorrect fix to MCPE-227846.

Issue has been fixed as of 1.21.130.26

Issue has been fixed as of 1.21.130.26

Seems to also affect Vibrant Visuals as seen in the image below and in the twitter post here.

Could this issue be reopened please? 1.21.120 only fixed the problem where the arms would clip into the torso (as shown in the comment above). The issue where the head is too big still remains and creates disparity with Java Edition.