-
Bug
-
Resolution: Unresolved
-
None
-
1.19.60.23 Preview, 1.19.30.22 Preview, 1.19.20.20 Preview, 1.19.10.22 Preview, 1.18.30.27 Preview, 1.18.30.26 Beta, 1.18.20.26 Preview, 1.18.20.25 Beta, 1.18.20.24 Preview, 1.18.10.22 Beta, 1.18.10.21 Beta, 1.18.10.20 Beta, 1.17.41 Hotfix, 1.18.0, 1.18.2 Hotfix, 1.18.11 Hotfix, 1.18.10, 1.18.30.30 Beta, 1.18.30.31 Preview, 1.18.12 Hotfix, 1.19.0, 1.19.2 Hotfix, 1.19.10, 1.19.20, 1.19.50
-
None
-
Community Consensus
-
Windows
-
998314, 92043
This is a repost of MCPE-34207. Mega_Spud closed the ticket without realizing that it was his ticket. The issue still happens in the latest build. I was told to open a new ticket, since the original ticket is very old.
Verification builds:
1.7
Summary:
Observers in Bedrock have a 3 redstone tick delay, which is different to the Java version which has a delay of 1 redstone tick.
Steps to Reproduce:
See screenshots for setup
- Run two observers into separate command blocks that run the command time query gametime
- Observe the difference between the command block time output
- Run test to the Java Edition, and observe the timing there
Observed Results:
In Bedrock, there is a 6 game tick (3 rs) tick delay on the observer output. In Java, there is a 2 game tick (1 rs) tick delay.
Expected Results:
The delay should be the same across versions wherever possible, so 1 rs tick.
Screenshots/Videos attached: Yes