[MC-9955] Repeater locks incorrectly pulse under certain conditions (due to inconsistent block updates)

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.

Linked issues

relates to 2

MC-11193 The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions Open

MC-8328 Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update 'algorithm') Reopened

Attachments

Comments 17

Dean Baset 2013-02-21T19:54:21Z

Confirmed in the snapshot

Tails 2013-03-18T22:57:15Z

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

galaxy_2alex 2014-10-25T11:06:22Z

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.

user-f2760 2016-03-17T15:57:57Z

No response for over a year.

Vincent Wiltschek 2016-03-17T20:14:36Z

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

7 more comments

user-f2760 2016-03-17T21:19:07Z

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?

Vincent Wiltschek 2016-03-17T21:22:01Z

It is.

user-f2760 2016-03-17T21:49:20Z

Then keep the affected versions up to date

Vincent Wiltschek 2016-03-17T22:30:29Z

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

user-f2760 2016-03-18T06:08:35Z

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

Vincent Wiltschek 2016-03-18T19:36:13Z

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

user-f2760 2016-03-18T23:34:11Z

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

bob 2016-11-06T01:03:37Z

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

Oval 2018-11-24T14:14:56Z

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.

Carretero Martínez 2020-05-27T21:06:20Z

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

pulpetti 2020-07-21T21:28:32Z

In 1.16.1

pulpetti 2020-08-07T19:55:49Z

In 1.16.2 RC-1