mojira.dev

NPB36

Assigned

No issues.

Comments

Things were changed during the leash overhaul in Chase the Skies (v1.21.90) so the length of which leads stretch by has increased.

HOWEVER at some point, mobs no longer consistently jump up blocks when pulled by a leash (the “get stuck in single-level blocks” issue mentioned). Here are a couple examples from v26.33:

[media: leash_failjump-2.mov]
[media: leash_failjump-1.mov]

Still occurring in 26.33. This is also a Java Parity issue. In Java, they only spawn on light level 0 live every other mob.

[media: zombiehorseman_lightL6-2.jpeg]
[media: zombiehorseman_lightL6-1.PNG]

This bug is reproducible even in a fresh world. No lag required.

And same for Pillagers, as well as a recording:

[media: pillager_case1_MCPE-234076.jpeg]
[media: compressedrecording_pillager_case_MCPE-234076.mov]

Guardians spawning in old chunks where the mentioned conditions apply:

[media: guardian_case1_MCPE-234076.PNG]
[media: guardian_case2_MCPE-234076.jpeg]

Unsure if that’s what this report is about though.

I’ve had 2 zombie horses disappear on separate occasions after capturing one, armouring it, and naming it. It’s funny because the horse and skeleton horse in the same place are still there. v1.21.30

Still reproduceable in v1.21.30.

In v1.21.111, the transition from walking to idle is still a sharp snap.

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.

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?

Load more comments