MC-158203Redstone clock creating a buggy signal
This observer clock that I came up with creates a buggy redstone signal:
The redstone is not getting bright red even when it is active.
First i thought this is a 0-tick pulse but then I found out some other weird things.
- The observer in front of the piston never gets left behind like it would with a 1 tick pulse
- When I ran the signal into other pistons they didn't activate
- Doors/Gates make the opening sound but don't open.
The other redstone components seem to behave normally
This was a very weird behaviour and I believe it is not intended.
I found 2 clock desings that produce this buggy redstone
This bug is (at least) since version 1.14.2
Linked Issues
Attachments2
Created Issue:
Redstone clock creating a buggy signal
This observer clock that I came up with creates a buggy redstone signal:
The redstone is not getting bright red even when it is active.
First i thought this is a 0-tick pulse but then I found out some other weird things.
- The observer in front of the piston never gets left behind like it would with a 1 tick pulse
- When I ran the signal into other pistons they didn't activate
- Doors/Gates make the opening sound but don't open.
The other redstone components seem to behave normally
This was a very weird behaviour and I believe it is not intended.
I found 2 clock desings that produce this buggy redstone
This bug is (at least) since version 1.14.2
Attachments2
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
Low![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
duplicates
duplicates
duplicates
Zero ticking is not confirmed to be intended behavior (see MC-8328). Utilizing emergent behaviors is always likely to produce wierd results. This is normal, in that the redstone doesn’t have time to play the powered animation before being deposited. I imagine any hackfix for this issue would make dust lag even worse.
Yep, this seems to be just zero ticking. However, the redstone dust interacts very weirdly with it. I'm unsure whether we have a fitting parent, or if this is intended behaviour.
Is this still an issue in 1.16.4 or later?
Yeah, this doesnt seem to have changed. It still works in 1.16.4.
I've resolved this as a duplicate since you've already reported the same bug here:
MC-153356Oops,yeah. That makes sense, sorry for the duplicate.
Why was the reporter of the issue changed?
You weren't active and TheGabro requested to be made the owner. We can give the bug report back to you if you want.
Yeah if it is not possible to have multiple non-admins that can modify entries it would be great if i'd 'get it back'.
As per your request, I've handed back ownership of the ticket to you