mojira.dev
MCPE-13983

Delay of repeaters can be ignored in some cases

When i was working on my note block song (slowest setting, 3 minecraft ticks.), i pressed the button to chevk my progress. And then, at one point in the song, the redstone repeaters bugged out on me and went on the fastest speed. (1 minecraft tick) and when i checked on the setting of the redstone repeaters at the point where it went bugged out, it was on the slowest (3 ticks), setting. When i pressed the button again, it still went fast. Do you know why it's doing this? (The system is Amazon's newest kindle, Fire 5th generation)

Update by @unknown
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.

Linked issues

Comments 22

scottrueschtech

I can confirm this.

I can also confirm this for MCPE 0.14.0. This happens for me when a large amount of redone has been placed but not necessarily being used.

Confirmed for 0.15.0, this bug has broken nearly everything I have made at some point. Relogging useually changes the repeater length again.

This is a video demonstrating this bug : https://youtu.be/e-eI1FBWM8g

And here is another video: https://youtu.be/6Mlf1OZsI9s

12 more comments

Problem still exists in 0.15.10. Wow this one is an important one.

Should the confirmation status be changed to confirmed on this one?

This is a bulk resolve of issues that haven't been updated to 0.16.0+ yet. Please comment below (To open the ticket) and update your affected versions. If you cannot reproduce the bug, please write in the comments so we can resolve it as "Cannot Reproduce". Thank You!

[Mojang] Tomas Alaeus

Added a more detailed description of the actual bug.

SuperGeniusZeb

Resolving as fixed, as this was accidentally confused with MCPE-15793, which was a separate bug. I have copied over the information provided by @unknown relating to MCPE-15793 and added it to the description of that bug. I have reverted the changes to this report, to bring it back to its state prior the change, and as I am unable to reproduce this bug after extensive testing, I am closing it as fixed as of 1.0.2. (I think it was probably fixed back in 0.16, though I don't know for sure.)

Kayli Pinola

(Unassigned)

32788

Confirmed

Tablet - Android - Amazon Kindle Fire

Kindle (aka fire) 5th generation

0.14.0, 0.15.0, 0.15.1, 0.15.6, 0.15.9, 0.15.10

1.0.2

Retrieved