Etho Hour

If you asked ten Minecraft players how long a minute is, you'd get ten different answers — and none of them would be wrong. The game has no official, reliable unit of time that players can use as a shared reference point. "A minute" in Minecraft means something different on a loaded single-player world, a busy multiplayer server, and a lagging server farm.

This matters more than most players realize. Farm output rates, redstone timing, mob spawning cycles, item despawn windows, potion durations — all of these are measured in time. If your unit of time is unreliable, every measurement you make is unreliable with it.

The root cause is the tick. Minecraft's internal clock runs in ticks, not seconds. And ticks are not guaranteed to line up with real-world time.

Minecraft targets 20 ticks per second (TPS). Under ideal conditions, each tick takes exactly 50 milliseconds to process, and 20 of them add up to one second of real-world time. This is the definition most tutorials assume, and it works fine on a fresh single-player world with nothing loaded.

The moment the game experiences any latency — from chunk loading, from entities, from redstone, from server load — ticks start to fall behind. The server can't make up lost time. A tick that takes 80ms to process is still just one tick, but it consumed 80ms instead of 50ms. The next second of real time might contain only 12 ticks instead of 20.

At 18 TPS, what feels like a minute is actually 66.7 real seconds. At 15 TPS, that "minute" stretches to 80 seconds. At 10 TPS — which is not unusual on a busy public server — your minute is now two real-world minutes long.

Any farm or contraption that was designed and measured at 20 TPS will drift under real conditions. More importantly, any comparison between farms measured under different TPS conditions is meaningless. You're not comparing the farms — you're comparing the server loads they were tested under.

The solution is to stop measuring in real seconds entirely. Measure in ticks. And to do that reliably across all conditions, you need a clock that counts ticks — not wall-clock time.

The Etho Hopper Clock — named after the Minecraft YouTuber Etho, who popularized the design — is one of the most precise timing mechanisms available in vanilla Minecraft. It consists of two hoppers facing each other with items bouncing continuously between them. Each time an item successfully transfers through a hopper, the hopper enters an 8-tick cooldown before it can transfer again.

The result is a clock whose cycle length is directly determined by the number of items inside it. With x items in the clock, each full cycle takes:

The −6 accounts for a small timing offset that occurs at the transition points of the cycle. This formula holds precisely and consistently, tick for tick, regardless of server load — because hopper cooldowns are measured in ticks, not in real-world milliseconds. The clock slows down when the server slows down, and speeds back up when the server recovers. It is, by definition, lag-resistant.

This is exactly the property we need. A clock that runs in lock-step with the game itself, giving us a unit of time that is consistent relative to the game's execution — even when that execution is inconsistent relative to the real world.

The goal is a clock that approximates one minute at 20 TPS and then counts 60 of those minutes to produce one "Etho Hour." We start by choosing the item count for the base clock.

One real minute at 20 TPS = 1,200 ticks. Solving the formula for x:

Those six missing ticks are intentional. 1,194 is a clean, consistent number that we can work with precisely. The definition of an Etho minute is simply 1,194 game ticks — not "approximately 60 seconds."

To build an Etho Hour, attach a 60-item counter to the base clock. The counter increments by one each time the 150-item clock completes a full cycle. When the counter reaches 60, one Etho Hour has elapsed:

The counter itself can be implemented in several ways: a hopper line that fills incrementally, a binary counter for precision, or any redstone circuit that can count 60 pulses from the clock output. The complexity of the counter doesn't affect the accuracy of the measurement — only the base clock determines that.