Algi | Stop using locational 0-tick reps @Algi__ | Uploaded 3 years ago | Updated 1 hour ago
READ DESCRIPTION!!!

I find that too many people are using locational 0-tick repeaters over and over again. With the exception of the first 2 reps, everything else shown is locational or directional in some way or another.

This applies to all 0-tick reps in which dust can update the return piston, along with most 3gt clocks and 0-tick smart pistons.

Case 1: Perfectly working 0-tick repeater and non-loc
Case 2: Perfectly working and non-loc upwards 0-tick repeater
Case 3: Output won't always power. You are relying on the dust to update your output before the return piston
Case 4: Dust output won't reliably update the updater and won't work
Case 5: Branching too early. You can't branch from those 0-tick reps from or before a dust that updates the return piston
Case 6: Stray updates, a stray dust update borkes the rep
Case 7: Long pulse case. Its a pretty rare case, but unless you build the reps like in case 1 or case 2, there is a chance that the rep can output a pulse that is 1 block event longer than normal.