[MC-9955] Repeater locks incorrectly pulse under certain conditions (due to inconsistent block updates) Created: 17/Feb/13  Updated: 20/Aug/24

Status: Reopened
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w07a, Minecraft 1.5, Snapshot 13w11a, Minecraft 1.7.4, Minecraft 14w08a, Minecraft 1.9, Minecraft 1.9.1 Pre-Release 3, Minecraft 16w20a, Minecraft 1.10, 20w21a, 1.16 Pre-release 8, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w29a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 3, 1.16.2 Release Candidate 1, 1.16.2, 1.16.3, 21w03a, 1.17, 1.17.1, 1.18.2, 1.19.2, 1.19.3, 1.20, 1.20.4, 24w33a, 1.21.1
Fix Version/s: None

Type: Bug
Reporter: Sanyeki Assignee: Unassigned
Resolution: Unresolved Votes: 20
Labels: None

Attachments: PNG File 1.png     PNG File 2.png     PNG File 3.png     PNG File 4.png    
Issue Links:
Relates
relates to MC-11193 The order in which powerable blocks (... Open
relates to MC-8328 Powered mechanisms react when receivi... Reopened
CHK:
Confirmation Status: Confirmed
Category:
Redstone
Mojang Priority: Low
Area: Platform

 Description   

When the input of a repeater and the repeater that is locking the first repeater are turned off at the same time, the first repeater will pulse on for a time period equal to it's delay creating a falling edge monostable circuit which should not be possible.



 Comments   
Comment by pulpetti [ 07/Aug/20 ]

In 1.16.2 RC-1

Comment by pulpetti [ 21/Jul/20 ]

In 1.16.1

Comment by Sanyeki [ 27/May/20 ]

Can confirm on 20w21a https://youtu.be/xIEg8dmaJ2g

Comment by Oval [ 24/Nov/18 ]

Is this still an issue in the Minecraft version 1.13.2, or the latest snapshot (currently 18w47b)? If so, please add it to the affected versions.

Comment by bob [ 06/Nov/16 ]

Is this still an issue in the latest snapshot 16w44a?

Comment by user-f2760 (Inactive) [ 18/Mar/16 ]

Still, you need to keep the affected versions up to date

Comment by Vincent Wiltschek [ 18/Mar/16 ]

Ok, this bug is an exception then because it is most probably caused by MC-8328 (0-tick pulses) that in turn seems to be caused by the fundamentally illogical block update 'algorithm' of Minecraft that is unable to properly handle simultaneity.
If there is one bug that won't get fixed 'accidentally' it's MC-8328 (and therefore MC-9955, too).

Comment by user-f2760 (Inactive) [ 18/Mar/16 ]

Because very, VERY often issues get fixed without the issue being assigned to anybody, simply because the ticket cannot be found or a similar issue got fixed which causes other issues to be fixed

Comment by Vincent Wiltschek [ 17/Mar/16 ]

Why? It affects every version until it gets resolved. Simple logic.
No point in creating a list of 20 different versions.

Comment by user-f2760 (Inactive) [ 17/Mar/16 ]

Then keep the affected versions up to date

Comment by Vincent Wiltschek [ 17/Mar/16 ]

It is.

Comment by user-f2760 (Inactive) [ 17/Mar/16 ]

Because a year ago it was asked if it was still an issue, and nobody replied until today :|

So, before I reopen this, is this still an issue in 1.9 or 1.9.1-pre3?

Comment by Vincent Wiltschek [ 17/Mar/16 ]

Why is it marked as resolved? Could you reopen it?
Not that the bug is that important, I'd rather see MC-8328 fixed.

Comment by user-f2760 (Inactive) [ 17/Mar/16 ]

No response for over a year.

Comment by Galaxy_2Alex [ 25/Oct/14 ]

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by Tails [ 18/Mar/13 ]

Confirmed in 13w11a, might be same issue as MC-8328.

Comment by Dean Baset [ 21/Feb/13 ]

Confirmed in the snapshot

Generated at Sun Jan 12 12:22:47 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.