Delay of repeaters can be ignored in some cases

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

Can confirm for 0.15.0. (Tested on Windows 10.) Happened while I was playing with a quasi-connectivity-less Jeb door. The door failed to work because the repeaters became instant instead of delaying the signal. Breaking and placing the repeaters fixed it.

Affects 0.15.1 tested on Windows 10 PC.

yep, this is a bug in MCPE0.15.0 on iOS on ipad air too - though i have only experienced it when rejoining a world after having quit the world

Why is no one from Mojang even assigned to resolve this issue? it's really annoying. If you need steps to enable you to re-produce the issue...all you need to do is build some fairly complex redstone, log out of the world and the game, and then log back in again a while later - leave it a couple of hours and then log back in. you will see that the redstone doesn't work as it did when you built it.

One of the examples i can give of a redstone contraption is one where I set a group of lights off flashing (by using repeaters between lights to delay the signal as it passess from light to light), then I delay the signal with a string of repeaters, and then I set off a few note blocks (the lights are still flashing. Then I send the signal back round to give the lights loop another surge of energy so they stop flashing but stay on. then the signal goes back to the note block and turns of the cylcical circuit that keeps them going. then the signal goes back to the lights and turns them off, then it goes out to some dispensers to fire them. in between each transition I have delays by many repeaters. the lights and note blocks are kept on with a loop-circuit and they are tuned off using a comparitor. It is a farily simple on, delay, off circuit but with all the delays in it (to keep things on for as long as i want) there are quite a few repeaters and a few comparitors too.

But, when I log back into the game, the circuit has lost all the timing I set with the repeaters. though nothing has visibly changed; the repeaters are all in the position i set them when i built it.

to reset the circuit so it works properly, i have to go round all the repeaters and re-position them. then it works again.

but when i log off and then back on, it is messed up again.
it is a real pain having to reset everything all the time.

why is no-one looking at this issue - it's totally annoying! 🙂

"Bugs are no longer assigned to specific developers in this tracker."

@unknown - Please don't worry, just because they aren't assigned to specific developers doesn't mean that this issue has gone unnoticed.

Still an issue in 0.15.6 - In this case the repeaters stopped working (even though set to 4 tick delay) after somebody joined my game via LAN.

Also noticed this bug, and weird thing with machines, where repeater delay set to not overlap pistons, moving only after other one turned off. And when bug occurs (repeaters start working as it was 1 tick, but visually stays as you set them) pistons just break all machine by moving block than they should not move... Just stopped playing MCPE until this bug fixed - it ruins all my machines with pistons

Reproduced on MCPE Realms after somebody joined my server few times (not every time, but repeaters droped to 1 tick after other player reloged few times to chage skin)

Mostly Affects realms, LAN worlds, and Xbox live, does not affect single player as much.

really annoying as I and my friend play together and everything breaks randomly.

0.15.9, not fixed yet, mechanisms accidentally gets broken after trying to play with my friends on realm

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).

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!

Added a more detailed description of the actual bug.

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.)