NpBlaster36

One temporary solution is to perhaps introduce a setting where you can toggle the camera dead-zone for the interact and destroy action buttons. As a matter of fact, in MCPE-220353, this dead-zone was implemented but then removed again since part of the player base are used to having no dead-zone with these buttons.

So again, a temporary solution is to have this toggle in settings, off by default, but can be toggled if your playstyle triggers camera snapping.

@floufen and as for the camera snapping issue, I believe the bug report you are after is MCPE-173571. I hope that directs you to what you’re after.

And as for the camera snapping issue, the bug report you are after is MCPE-173571.

I think the fact that the action buttons do not have a camera dead-zone is intentional design from my understanding, and as a side-effect, it may trigger situations where 2 camera inputs at once cause the camera to suddenly snap to a random direction.
HOWEVER, I do agree that there should be an option in settings that can toggle this dead-zone to make the action buttons a little more reliable in PvP.

@floufen No, this is not related to MCPE-224290. That is intentional design from my understanding, and as a side-effect, it may trigger situations where 2 camera inputs at once cause the camera to suddenly snap to a random direction.

THIS bug report is an issue where action buttons could get stuck because the game thinks you are still holding them down, when in reality you were just too quick and are instead moving forward with the joystick, or are just looking around.

Additional Notes on Unaffected Buttons:

• Jump and Sneak (Hold to sneak) correctly stop their action under the same conditions.

• Sprint and Sneak (Tap to sneak) are toggle-based so unaffected by release timing.

• Pick Block is a one-time action, so even if affected, it would not result in unintended continuous behavior.

In an earlier comment, I speculated that the issue might be related to the lack of a camera dead zone for the action buttons, since the bug doesn’t occur with the jump or sneak buttons. However, after further testing, I’ve confirmed that both the jump and sneak buttons function normally- even when used with simultaneous camera or joystick input. So the dead zone theory is likely unrelated.

A more plausible explanation is a multi-touch timing issue: the bug occurs when a new touch begins elsewhere on the screen during the release of an action button. This may cause the release event to be missed or overridden, leaving the button stuck in a "pressed" state.

Based on testing, the affected buttons include:

• Destroy (e.g., breaking blocks)

• Interact (e.g., placing blocks, drawing a bow, opening containers)

This updated hypothesis better explains the specific timing required to reproduce the bug, and why it doesn’t affect other buttons under the same conditions.

This is also a separate bug to where the 4-leash-configuration on a Happy Ghast isn't physically attached to the Happy Ghast.

*help.minecraft.net

Okay, well it’s unlikely but good luck anyway. If you really think you should have it on your account, maybe contact Minecraft Support at help.miecraft.net?

Added v1.21.80.

The possible situations are either you did not claim the skin pack and fell victim to the bug mentioned above, or you claimed the skin pack on another account.

Either way, don't feel bad! Mojang are adding more and more free capes to Minecraft to make sure people like you don't feel left out (and devalue them). Since 2024, we've had like 9 capes release. The TikTok Cape, the Twitch Cape, the 15th Anniversary Cape, the MCC cape, the Minecraft Experience Cape, the Menace Cape, the Home Cape, the Yearn Cape, and more recently the Common Cape. Most of these capes are free and just require a bit of participation in various activities. With so many new capes being released, there's always another opportunity to earn one. Don't worry about the ones you’ve lost, worry about the next opportunity to grab one.

Hope this helps: (it's just info)
The Founder's Cape was released as part of a free skin pack during Minecon Live 2019 but it was only available for a limited time. There was a bug that allowed players to receive the Founder's Cape even if they hadn't downloaded the skin pack, meaning some players who were signed in to Minecraft Bedrock at the time received the cape without claiming the skin pack. The issue was later patched. Players who had the cape but hadn't downloaded the skin pack had the cape removed from their accounts. Those who had claimed the skin pack before it was taken down retained their Founder's Cape.

It's worth noting that the issue that caused the leash to render attached to the floor/below the mob is a separate bug… and for that reason, these screenshots were taken in v1.21.72 instead to avoid confusion.

…and 1.21.70 versions.

Fun fact, if the boat is in flowing water, you are able to pull it out of the water just fine. The problem lies with non-flowing water.

Still active in 1.21.70 versions. Considering the Leash rework is still in snapshots and preview, it would be great if they knocked out some old bugs with leads such as this one. I would assume this bug would make it impossible to pull boats out of water with the happy ghast. You’d have to somehow force it onto land first.

If blocks were placed on the sides where the player would get offset, the player physics would push them back into the portal fame. Although, if you had a lavafall on those sides, since you’re sticking out of the frame, its essentially an instant-death scenario unless you have fire resistance or good enough gear.

Walking backwards while eating/drawing bow also seems to snap the player by half a block.