mojira.dev
MCPE-235969

Non-Instant-Mineable Blocks Experience Excessive Delay When Mined in Sequence in Bedrock Edition

Description:
In Bedrock Edition, blocks that cannot be mined instantly (in 1 game tick, or gt) exhibit abnormally long mining delays when multiple such blocks are mined in a sequence. While instant-mine blocks (like leaves) incur a predictable 1-tick selection delay and thus require 2 gt total per block in sequence, blocks with a base mining time of 2 gt (e.g., cobwebs with Efficiency V shears and Haste II) should theoretically be mined in 3 gt each when sequenced. However, when arranged in a line and mined one after another, the total time far exceeds the expected 24 gt for 8 blocks (3 gt × 8), reaching up to 56 gt—more than double the expected time. This severe delay does not occur when mining a single cobweb, indicating a compounding penalty specific to sequential mining of non-instant blocks.

How to Reproduce:

  1. Setup A (Control – Instant-Mine Blocks):

    • Place 8 leaves in a straight line.

    • Use a 16-gt clock to repeatedly reset and mine them in sequence.

    • Observe that all 8 leaves are consistently mined within the expected time (~16 gt for the sequence).

  2. Setup B (Non-Instant-Mine Blocks):

    • Place 8 cobwebs in a straight line.

    • Equip Efficiency V shears and apply Haste II effect.

    • Mine the cobwebs one after another in sequence (without stopping).

    • Measure the total time to destroy all 8 cobwebs.

  3. Setup C (Single Block Test):

    • Mine a single cobweb under the same conditions (Efficiency V + Haste II).

    • Confirm it breaks in approximately 2 gt.

Observed Result:

  • Leaves (Instant-Mine): 8 blocks mined in ~16 gt (as expected with 1-tick delay).

  • Single Cobweb: Mined in ~2 gt (as expected).

  • 8 Cobwebs in Sequence: Total mining time reaches ~56 gt (averaging ~7 gt per block), far exceeding the expected ~3 gt per block.

  • The delay appears to compound with each successive block, suggesting a broken reset or cooldown mechanism in the mining logic for non-instant blocks.

Expected Result:

  • Sequentially mining non-instant blocks should incur only a fixed, consistent delay per block (e.g., base mining time + 1-tick selection delay).

  • For cobwebs with Efficiency V + Haste II (2 gt base), each block in a sequence should take ~3 gt, resulting in ~24 gt for 8 blocks.

  • Behavior should be predictable and consistent, similar to instant-mine blocks, without compounding penalties.

Additional Notes:
This bug severely impacts the efficiency of farms that rely on fast mining of non-instant blocks (e.g., cobweb-based item collection systems). The excessive delay suggests a flaw in how Bedrock Edition handles mining state reset or player interaction cooldown for blocks that require multiple ticks to break. This is likely a deep-rooted issue in the client-side mining prediction or server-side validation logic. Fixing this is critical for technical gameplay parity and farm design viability.

Linked issues

Attachments

Comments 2

Hi!
Thank you for your report! 

  • Could you try to reproduce the issue without any add-ons?

  • Could you please provide a world where issue occurs? (If the file is to big to upload it here please upload it to One Drive and post the link to it here)

  • Did this issue occur on a LAN or on a multiplayer server?

Quick Links
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

[media]

Here is the world file that has the issue. Although practically any world has this problem. Here's how to reproduce it: once you're inside, turn on the clock, then start mining the cobwebs and observe the mining speed.

LiShang

(Unassigned)

1568144

Confirmed

Multiple

26.10.21

26.10.21 Preview, 26.0, 26.10.24 Preview, 26.1

Retrieved