OBSERVER CLOCK
Two observers facing each other create the fastest possible clock. Each observer detects the other's state change, causing infinite rapid toggling at 1 game tick per pulse.
When to Use
Fastest possible clock for rapid-fire dispensers, bubble column activators, zero-tick farms (if applicable).
Materials
- ▸2 Observers
Overview: what the Observer Clock is and does
Two observers facing each other create the fastest possible clock. Each observer detects the other's state change, causing infinite rapid toggling at 1 game tick per pulse.
As a clock it produces a repeating on/off pulse on its own, driving anything that needs to fire at a steady rhythm.
In practice it is used for fastest possible clock for rapid-fire dispensers, bubble column activators, zero-tick farms (if applicable). The build below targets vanilla Java Edition 1.21.
How it works: the redstone mechanics
Two observers staring at each other toggle every game tick, producing the fastest clock redstone allows. Each one sees the other's state flip and immediately re-fires, so the loop never settles.
It is assembled from 2 Observers, and each of those parts plays a specific timing or logic role in the circuit rather than being interchangeable filler.
Because this is a clock circuit, the thing to watch as you build is the period — the total tick delay around the loop sets how fast it runs.
How to build it
- 1Place one observer facing any direction.
- 2Place a second observer facing the first one (faces pointing at each other).
- 3They immediately start toggling, each detects the other's state change.
- 4Tap the output from the back of either observer.
- 5Warning: This creates extreme lag if overused. Use sparingly.
- 6Power it up and watch one full cycle: confirm it pulses at the rhythm you expected before wiring it into a larger contraption.
Uses & applications
- ▸Fastest possible clock for rapid-fire dispensers, bubble column activators, zero-tick farms (if applicable).
- ▸Direct 2-observer clock (fastest, 1 game tick) — a variant suited to particular space or timing needs.
- ▸Observer + piston clock (slower, more controllable) — a variant suited to particular space or timing needs.
- ▸Observer chain clock (sequential observers for timing) — a variant suited to particular space or timing needs.
Tips & common mistakes
- !It runs at maximum speed permanently and creates serious server lag if left running — gate it behind a lever and switch it off when idle.
- !If the clock will not be running constantly, add a lever in the loop so you can switch it off and spare the server the block updates.
- !Remember that bare redstone dust loses 1 signal strength per block, so insert a repeater before any run exceeds 15 blocks inside this circuit.
Observer Clock FAQ
What is an Observer Clock used for?
A Observer Clock is used for fastest possible clock for rapid-fire dispensers, bubble column activators, zero-tick farms (if applicable). As a clock it produces a repeating on/off pulse on its own, driving anything that needs to fire at a steady rhythm.
What do you need to build an Observer Clock?
You need 2 Observers. Place one observer facing any direction.
How does an Observer Clock work?
Two observers staring at each other toggle every game tick, producing the fastest clock redstone allows. Each one sees the other's state flip and immediately re-fires, so the loop never settles.
Are there different versions of the Observer Clock?
Yes — common variants include direct 2-observer clock (fastest, 1 game tick), observer + piston clock (slower, more controllable), and observer chain clock (sequential observers for timing). Pick the one that fits your available space and timing requirements.
Is an observer clock laggy?
Yes. Two observers facing each other toggle every single game tick, which is extremely fast and produces many block updates per second. It is fine for short bursts but will lag a world if many run continuously, so always add an off switch.