Sprinting Is Incorrectly Canceled by Eating, Using a Bow, or Holding a Shield on All Bedrock Platforms

Summary:
On all Bedrock Edition platforms, sprinting is canceled whenever the player performs certain actions such as eating, drawing a bow, or holding a shield. Java Edition does not cancel sprinting for these actions. This results in inconsistent movement, reduced mobility during combat, and broken parity across platforms.

Observed Behavior:

• Sprinting stops immediately when the player begins eating food.

• Sprinting stops when the player draws a bow.

• Sprinting stops when the player raises or holds a shield.

• Sprinting can also be canceled by other actions that do not cancel sprint in Java.

• This happens on all Bedrock platforms (Windows, consoles, mobile).

Expected Behavior:

• Sprinting should continue while eating, drawing a bow, or holding a shield, matching Java Edition behavior.

• Sprinting should only stop when the player performs actions that intentionally cancel sprint (e.g., crouching, colliding, low hunger, blocking attack).

• Player mobility and combat movement should remain fluid and uninterrupted.

Steps to Reproduce:

1. Open Bedrock Edition on any platform.

2. Begin sprinting.

3. Attempt to eat food, draw a bow, or raise a shield.

4. Observe that the player immediately stops sprinting.

5. Compare the same behavior in Java Edition, where sprinting continues.

Impact:

• PvP movement becomes more restrictive compared to Java Edition, making combat less fluid.

• Players cannot maintain speed while eating or drawing a bow, which makes various combat and PvE strategies significantly harder.

• Shield usage further reduces mobility, especially with the already‑existing shield input issues on Bedrock.

• Introduces inconsistent controls and movement behavior across platforms and between game editions.

• Negatively affects gameplay on all devices: mobile, controller, and keyboard/mouse.

Additional Notes:

• This issue is separate from shield activation bugs, but both contribute to inconsistent combat mechanics on Bedrock.

• None of these actions cancel sprint in Java Edition, confirming this is a parity bug, not an intended design choice.

• The behavior is fully platform‑independent and reproducible everywhere.