MultiThreading Problems

Minecraft Bedrock appears to process certain game logic across multiple threads. Because these threads do not always finish their tasks at the same time, the resulting update order becomes inconsistent and unreliable. This directly affects systems that depend on strict tick‑accurate behavior, such as complex Redstone mechanisms.

As server or client lag increases, the update order becomes even less predictable. This makes reliable Redstone behavior extremely difficult and, in many cases, practically impossible.

Impact on Gameplay:

• Redstone circuits that depend on consistent timing fail unpredictably due to desynchronized updates between threads.

• Falling block entities (e.g., sand, gravel) sometimes fail to update when landing on a block.

  • They remain as entities for a short period instead of converting to solid blocks immediately.

  • This can cause the falling block to break unintentionally, which disrupts designs that rely on stable falling‑block behavior.

• When large numbers of falling blocks are present some of them will still be in the air for a short time after the other one landed (can be an intentional game performance design)
  
  Why This Is a Bug: The inconsistent update order is not expected behavior and breaks core mechanics that normally rely on deterministic tick processing. The issue is not about adding a new feature; it is about restoring reliable, predictable game logic.
  
  Additional Note: I previously attempted to report this issue, but it was flagged as a “solution” or “suggestion.” This report is intended strictly as a bug description, not a feature request. A performance setting or other internal fix would simply be one possible way to address the underlying problem. (for lower end devices)

Thank you for taking the time to review this report. I hope this information helps clarify the issue, and I’m available for any further details if needed.