Henrik Lindström

Well, just edited my whole last comment.. xD
They are both from the same issue as i wrote now that i thought about it so staying merged is probably a good idea. I just have to update the main post...

I added the new versions.

Explanation to the leftover of this bug:
Also.. i completely edited this comment because i just thought about it, and the repeater bugs are caused by the same problem that causes torches to act weird. the only difference is that with torches it's about them checking if they shoyuld schedule an update for themselves and with repeaters it's about them checking if they are powered or not.

The actual problem in both cases is how the game updates things one at a time in some order.
This causes these weird behaviours.

Examples:
Bug with a torch(One RedStoneTick at a time):

RSTick 0: The torch's input changes causing it to schedule an update.
RSTick 1: In the same tick but before the scheduled update arrives we update the torch causing it to schedule another update. Then it gets updated from the last tick's schedule and changes state.
RSTick 2: The torch's input changes again(scheduling another update). The scheduled update from last tick arrives and the torch changes state.
RSTick 3: The scheduled update the torch is supposed to change state too arrives but the torch is already in the correct state so nothing happens.

This is what happens in the torch monostable picture.

Bug with a repeater:

The fact that repeater's input need to be off for 1 RSTick before it changes state causes problems here.

Shortly, the repeater's input turns off, one RSTick later IF the input is powered tick AND is updated before the repeater, the repeater will never turn off because it made the "1 RSTick off" check just after the input had already turned on again.

Sorry if i suck at explaining..

But the problem lies in that even though two things happen in the same tick, one of them will still happen before the other.

This is just how redstone stuff works so i wouldn't expect this to ever be fixed as that would probably require a big rewrite of the whole redstone code. (As far as i can tell).

Anyway, i feel pretty sure that this is the cause for both bugs though i could be wrong.
I might update the whole post to explain this so it would include your repeater bugs aswell..

But not feeling like it right now 😛

Only the second video actually contains this bug. Repeater problems are because of something else.
And i quickly updated the post 🙂

Seems like the comparator part of this issue is fixed again in Snapshot 13w09a 🙂
Edit:
It still exists in a few cases.. Il update the post when i have time..

This is the same bug as: https://mojang.atlassian.net/browse/MC-2340

Redownloaded it, bug is still there.

This bug is back in snapshot 13w06a. Can a mod or someone reopen maybe?

No, when i said "idle", i meant that nothing is changing around them and their state isn't chaning. They can be idle in their on state aswell.

This was not fixed in Snapshot 13w05a.
The actual bug that is causing this is: https://mojang.atlassian.net/browse/MC-2340

Hi dico 😛
A 0 tick pulse would be a signal that turns on and off in the same tick.
And as dico said, it depends on if the repeater or the torch updates first.

Very annoying though as it breaks alot of instant piston logic 😞

Edit:
Actually, this is the bug i was experiencing:
https://mojang.atlassian.net/browse/MC-8328

I had changing signal strength aswell, so got confused 🙂

I added that it updates blocks behind it aswell to the description 🙂

You're thinking of something different 😉

Well that doesn't have with this glitch to do.
It's still not completely fixed in the 1.5 snapshot, if you have two output torches one of them will give a 1 tick pulse, the other a 2 tick one.
Updated the description 🙂