-
Bug
-
Resolution: Unresolved
-
None
-
1.20.20.20 Preview, 1.13.0.1 Beta, 1.18.10.26 Beta, 1.17.40.23 Beta, 1.17.40.21 Beta, 1.17.20.20 Beta, 1.17.0.50 Beta, 1.16.210.56 Beta, 1.16.0.61 Beta, 1.16.0.60 Beta, 1.16.0.51 Beta, 1.14.0.2 Beta, 1.13.0.9 Beta, 1.12.0.11 Beta, 1.12.0.2 Beta, 1.11.0.10 Beta, 1.9.0.0 Beta, 1.6.0, 1.7.0.5 Beta, 1.7.1, 1.7.0, 1.8.1, 1.9.0, 1.10.0, 1.14.0, 1.14.60 Hotfix, 1.16.100, 1.16.201 Hotfix, 1.17.2 Hotfix, 1.17.30, 1.17.32, 1.18.2 Hotfix, 1.18.31
-
None
-
Confirmed
-
Multiple
-
89588 / 95402
The bug
When any command block receives power, three ticks pass before it finally runs its command. When a repeating command block loses power, it continues to run commands for three ticks!
How to reproduce
- Place a repeating command block: /setblock ~ ~1 ~ air
- Place a chain command block following it: /say running
- Place a redstone block on top
→ After a three ticks delay, "running" is printed three times.
Correct behavior: "running" should print once on the exact subsequent tick after the redstone block is placed.
- relates to
-
MCPE-15044 Redstone lamps do not turn off immediately when unpowered
- Reopened
-
MCPE-15793 Redstone components don't apply the correct amount of delay when activated by world changes
- Reopened