Crossbows Automatically Load in Bedrock Instead of Requiring Full Draw and Release Like Java Edition

Summary:
On all Bedrock Edition platforms, crossbows automatically load as soon as the player holds the use‑item button long enough. In Java Edition, loading a crossbow requires the player to fully draw the bolt and then release the input to complete the loading process. This difference causes inconsistent control behavior and breaks parity between editions.

Observed Behavior:

• Holding the use‑item input on Bedrock causes the crossbow to auto‑load as soon as the draw animation finishes.

• The player does not need to release the button to confirm the load.

• The loading action completes automatically, even if the player continues holding the input.

• Java Edition requires a deliberate release of use‑item after reaching full draw.

• This makes Bedrock’s crossbow handling feel less precise and inconsistent with Java mechanics.

Expected Behavior:

• Crossbows should load only when the player releases the use‑item button after reaching maximum draw strength, matching Java Edition.

• Holding the use‑item button should draw the crossbow, but not complete the loading action until released.

• Crossbow usage should have consistent timing and control across platforms and editions.

Steps to Reproduce:

1. Open Bedrock Edition and equip a crossbow.

2. Hold the use‑item input (right‑click, trigger, or mobile button).

3. Observe that the crossbow automatically loads as soon as it finishes drawing, without needing to release the button.

4. Compare to Java Edition, where loading only completes after the player releases the use‑item input.

Impact:

• Removes player control over the exact moment the crossbow is loaded.

• Affects PvP timing, reaction patterns, and pre‑loading strategies compared to Java.

• Produces inconsistent behavior across editions, making combat skills non‑transferable.

• Affects aiming consistency because Bedrock auto‑loads even if the player is still holding the button for a different action.

Additional Notes:

• This behavior affects all input devices (keyboard/mouse, controller, touch).

• The issue is unrelated to latency or performance; it is the result of different input handling logic.

• This is part of a wider set of combat and input parity differences between Bedrock and Java.