Affects Version/s: 220.127.116.11 Beta, 0.15.0, 0.15.2, 0.15.4, 0.15.10, 0.15.90.8, 0.16.0, 0.16.1, 0.17.0.1, 0.16.2, 18.104.22.168, 22.214.171.124, 126.96.36.199, 1.0.0, 1.0.2, 1.0.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206 Beta, 1.9.0, 220.127.116.11 Beta, 18.104.22.168 Beta, 22.214.171.124 Beta
Fix Version/s: None
Platform:Tablet - iOS - iPad Air 2
VSO:32788, 36225, 176093
On flicking the power switch in each example, the blue example shown would fire like the red example shown (end repeater lights up).
In the blue example, the output repeater doesn't fire. If you rapidly flick the switch back and forth, the blue repeater fires intermittently.
- Drive redstone current into a block on top of a piston to generate a 1-tick pulse (red example). Position a repeater to pick up the current from the piston block, but the redstone should flow directly from power source to the block.
- Turn on the power source; the piston will fire and the output repeater will light up for its pulse duration.
- Insert a repeater anywhere along the input line and toggle the power source. the output repeater will not fire.
- Rapidly toggle the power source (switch works best). The repeater will occasionally fire.
- replacing the relay with redstone torch inverters shows the same issue (the mechanism will fire when the torch is placed, but not when the mechanism is toggled).
- Using an observer block as the power source showed the same issue.
Minecraft pocket edition 0.15.0 (iOS - replicated on iPhone 6 and iPad air 2)
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Update by [Mojang] Tomas Alaeus, explaining the cause of the bug
Repeaters don't apply the delay properly in all cases. If the repeater was activated by another pure redstone component being ticked, then the delay will be correct. However, if it was activated by a world change (lever, piston modifying a circuit, pressure plates, buttons, etc) then the repeater will output a signal 1 tick too fast. A 1-delay repeater will act as a 0-delay repeater (that is, completely ignored). A 3-delay repeater will act as a 2-delay repeater.