When multiple repeaters are serially connected, and immediately adjacent (i.e., have no space between them,) several things go wrong:
1) Delayed "lock"
-----------------
In version 1.7.10, the "lock" signal on a repeater locks the output with a delay of exactly one redstone tick from the point of view of the input of the laterally connected repeater. See `expected_repeater_lock_delay.png`.
In version 1.8-pre1 and 1.8-pre2, the lock signal is sometimes delayed by exactly one additional redstone tick.
This seems a lot like a bug, because it only occurs on repeaters in certain configurations, and in some configurations, only occasionally. And most importantly, it significantly reduces the set of redstone circuits with well-defined/intelligible behavior.
I have observed this only in connection with multiple serially connected, and immediately adjacent repeaters. Indeed, `expected_repeater_lock_delay.png` always looks the same, and always looks as as expected, in both version 1.7 and 1.8.
In circuits where the lock signal is synchronous, the bug appears to happen every time, and in a completely consistent way (see `bug-synchronous-1.png` and `bug-synchronous-2.png`.)
In circuits where the lock signal is produced by a manually activated switch, the bug happens roughly 1 out of 5 times. In most of those cases, the extra delay affects all but the last repeater in the adjacent series (see bug-asynchronous-1.png,) however, in roughly 1 out of 25 times, the first repeater in the adjacent series has the expected delay, i.e., is not affected by the bug (see bug-asynchronous-2.png.)
2) Loosing 1-tick off
---------------------
The last repeater in a series of immediately adjacent repeaters fails to respond to a 1-tick *off* pulse even when all the repeaters are set to the minimum delay (i.e., ...1110111... becomes ...1111111...). This was not the case in version 1.7.10.
Linked issues
Attachments
Comments 7
Yes, MC-54711 appears to coincide with my item 2 "Loosing 1-tick off". Also, it could be that my item 1 "Delayed lock" is just a different aspect of the same underlying bug, but maybe it is not.
This collage hopefully helps to show exactly what I am talking about. Note that the bug occurs only in the preview versions of 1.8, and only to a repeater in an immediately adjacent series, and only when it is neither the first, nor the last repeater in that series. Note that this only addresses the synchronous aspects of this bug. By "synchronous" I mean that the timing of the "lock" signal is coupled strongly to the timing of the main input signal.
Still not resolved in version 1.8 (the version released today). All issues mentioned above are still present.
Is this still an issue in the current Minecraft Snapshot 15w47c 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.
This is a duplicate bug for: MC-54711
and as you can see in the above link, in the comments section, as of 12/Nov/15 the bug is still present in 15w46a .
but ill check it for 15w47c asap and report back here.
Could this be MC-54711?