Sarah Tennyson
Comments
Some testing with quickcarpet seems to indicate that the timing on observer/observer is still 1 every 3 and my screenshots above are more a symptom of MC-151057; however that issue doesn't in any way explain observer/hopper clock behavior or lack thereof.
observer/observer in 1.14
observer/observer in 1.14.1 pre 1
observer/dropper clock (works in 1.14 after powering the dropper and then unpowering it), does not function in 1.14.1 pre 1
For an example of the "duplicate" bug that was previously mentioned, it is really easy to replicate and seems to be based on a repeater receiving an input signal of exactly the same length that it is set to... so a repeater set to 2 ticks receiving a 2 tick pulse will lock on until updated, a 3 tick receiving a 3 tick pulse... this can be seen pretty easily as shown:
Half of this is not a duplicate as noted in my previous comment and I have confirmed it is still a problem in 1.14.1 pre 2 despite MC-151057 being fixed.