-
Bug
-
Resolution: Unresolved
-
None
-
1.20.20.23 Preview, 1.20.20.22 Preview, 1.17.10, 1.16.200.57 Beta, 1.16.100.58 Beta, 1.16.100.56 Beta, 1.16.100.55 Beta, 1.15.0.8 RTX Beta, 1.16.0.63 Beta, 1.16.0.61 Beta, 1.15.0.53 Beta, 1.15.0.51 Beta, 1.14.30.51 Beta, 1.14.2.51 Beta, 1.14.2.50 Beta, 1.14.0.51 Beta, 1.13.3, 1.14.0.4 Beta, 1.13.1, 1.14.1 Hotfix, 1.14.0.3 Beta, 1.14.0.2 Beta, 1.14.0.1 Beta, 1.13.0.18 Beta, 1.13.0.17 Beta, 1.13.0.16 Beta, 1.13.0.15 Beta, 1.13.0.9 Beta, 1.13.0.6 Beta, 1.12.0.2 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, 1.0.0.0, 1.0.0.1, 1.0.0.7, 1.0.0, 1.0.2, 1.0.3, 1.0.4.0, 1.0.4.1, 1.0.4.11, 1.0.5.13, 1.0.6.0, 1.0.5.54, 1.1.0.0, 1.0.6.52, 1.1.0.4, 1.1.0.5, 1.0.7.0, 1.1.0.9, 1.1.0.55, 1.1.1.0, 1.1.1.51, 1.1.2.50, 1.1.3.1, 1.1.5.0, 1.2.0.25, 1.2.0.31, 1.2.3.6, 1.2.5.12, 1.2.6.2, 1.2.5.52, 1.2.6.60, 1.2.9.1, 1.2.10.1, 1.2.10.2, 1.2.15.01, 1.2.16.3, 1.5.0.0, 1.4.0.5, 1.5.0.7, 1.4.2.0, 1.5.0.14, 1.6.0.6, 1.7.0.9 Beta, 1.9.0, 1.10.0.4 Beta, 1.11.0.1 Beta, 1.11.0.3 Beta, 1.11.4, 1.12.1, 1.12.0, 1.13.0, 1.14.1.2 Beta, 1.14.0, 1.14.30 Hotfix, 1.14.60 Hotfix, 1.16.0, 1.16.20, 1.16.50 Hotfix (iOS), 1.16.40 Hotfix, 1.16.100, 1.16.210, 1.16.221 Hotfix, 1.18.2 Hotfix, 1.19.2 Hotfix, 1.19.20, 1.19.21 Hotfix, 1.19.62, 1.20.12 Hotfix, 1.20.81 Hotfix
-
Confirmed
-
Multiple
-
32788, 36225, 176093
What I expected to happen was...
On flicking the power switch in each example, the blue example shown would fire like the red example shown (end repeater lights up).
What actually happened was...
In the blue example, the output repeater doesn't fire. If you rapidly flick the switch back and forth, the blue repeater fires intermittently.
Steps to reproduce:
- 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 nighter
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 talaeus, 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.
- is duplicated by
-
MCPE-17208 Repeaters set to 1-redstone-tick & comparators have no delay compared to redstone dust
- Resolved
-
MCPE-17274 Repeaters add random delay to pistons (but not to other components)
- Resolved
-
MCPE-20762 Piston Retraction
- Resolved
-
MCPE-20859 Repeaters are broken
- Resolved
-
MCPE-20904 Repeater delay bug
- Resolved
-
MCPE-21087 The repater delay changed in mcpe 1.1
- Resolved
-
MCPE-21281 Repeaters don't make signals longer
- Resolved
-
MCPE-24278 inconsistent Redstone/pistons
- Resolved
-
MCPE-25859 Piston timings are glitched
- Resolved
-
MCPE-27516 Incorrect Repeater Timings
- Resolved
-
MCPE-28387 Piston Feedtape Bug
- Resolved
-
MCPE-28623 repeater updates 1 tic early and releases a signal 1 tic late.
- Resolved
-
MCPE-28657 Observers triggered by redstone has inconsistent timing
- Resolved
-
MCPE-28690 Monostable cuircuit only works when powered directly
- Resolved
-
MCPE-29171 Pistons need to have consistant timing
- Resolved
-
MCPE-30678 Piston bug
- Resolved
-
MCPE-30888 T Flip-Flop redstone mechanism
- Resolved
-
MCPE-31399 Monostable circuits aren't working
- Resolved
-
MCPE-31470 Double piston extender not working
- Resolved
-
MCPE-31790 Piston monostable pulse generator not generating pulse when powered by a redstone torch activated by un-powering block its attached to
- Resolved
-
MCPE-33011 Repeater's tick doesn't work correctly.
- Resolved
-
MCPE-33825 Falling edge mono-stable circuit doesn't work
- Resolved
-
MCPE-35543 Redstone not always working properly
- Resolved
-
MCPE-36786 Failure in back-to-back piston monostable circuits
- Resolved
-
MCPE-37625 Sticky Piston is not passing Redstone Ticks to Redstone Repeaters
- Resolved
-
MCPE-41017 Bug with pistons and repeaters
- Resolved
-
MCPE-42968 Piston systems and repeater clock
- Resolved
-
MCPE-60278 Repeaters activate 2 gameticks too early
- Resolved
-
MCPE-75293 Redstone Timing Inaccuracies: Observer and Repeater
- Resolved
-
MCPE-84280 Moving blocks take 1-2 redstone ticks to become movable
- Resolved
-
MCPE-98587 Repeaters changing the way redstone dust interacts with other redstone component
- Resolved
-
MCPE-103691 Repeaters are not applying correct delay and appear as though they do
- Resolved
-
MCPE-103999 Redstone components do not react based on the game tick power is provided
- Resolved
-
MCPE-136762 If a repeater runs into a monostable it won't work
- Resolved
-
MCPE-152120 Redstone Repeaters and Observers programming errors
- Resolved
-
MCPE-161802 Circuit breaker pulse limiter does not function properly when receiving input from repeaters, redstone torches, observers, or comparators
- Resolved
-
MCPE-167483 Disappearing signal delay / repeater affects downstream timings
- Resolved
-
MCPE-173858 Left redstone repeater responds differently
- Resolved
-
MCPE-182268 The redstone-mechanism does not work in Bedrock.
- Resolved
- relates to
-
MCPE-37479 Command blocks fail to recognize their power state changed for 3 ticks
- Open
-
MCPE-12848 Comparators measuring a container take redstone 2 ticks to change their state instead of 1
- Resolved
-
MCPE-15607 Pistons take 3 redstone ticks to extend and 1 tick to retract, which should both take only 1 rs tick
- Resolved
-
MCPE-16371 Multiple mechanism components are ticked in a random order when they are to be ticked in exactly the same rs tick
- Resolved
-
MCPE-34207 Observers have a 3 RS tick delay
- Resolved
-
MCPE-156762 Comparator outputs the power level of moved blocks (and sometimes of placed blocks) before it evaluates container fullness
- Open
-
MCPE-89921 Observers dont activate redstone dust and repeaters when it is pushed by a sticky piston and that sticky piston gets powered by another observer
- Reopened
-
MCPE-22741 Fill command doesn't give repeater the correct delay
- Resolved
-
MCPE-24278 inconsistent Redstone/pistons
- Resolved
-
MCPE-28647 Redstone torch clock behaviour
- Resolved
-
MCPE-116576 Dropper update order is affected by observers
- Resolved