The Physics of Redstone: How to Prevent Redstone Lag From Crashing Your Server
It always starts the same way. A new player joins, says nothing for two days, then suddenly your TPS drops from 20 to 3 and one region of the map shows 100% CPU load. You teleport to the co-ordinates and find the most intricate redstone contraption you have ever seen — thousands of comparators, pistons, and hoppers running at maximum speed, 24 hours a day.
Redstone lag is the most common and most preventable form of server performance degradation. Here is how it works and how to fight it.
How Redstone Consumes CPU
Every redstone component is a tile entity or a block update event. When a comparator changes state, it schedules a block update. That update propagates to adjacent components, which schedule their own updates, which propagate further. In a complex contraption, a single clock cycle can generate thousands of block update events per second.
Your server processes these on the main game thread — the same thread handling player movement, mob AI, and chunk loading. When redstone floods this thread with events, everything else stalls.
| Contraption Type | Block Updates/tick (est.) | TPS Impact on 20-player server | |---|---|---| | Simple door button | ~10 | None | | Compact storage sorter | ~200 | Minimal | | Zero-tick clock (patched) | ~10,000+ | Server crash | | Active hopper network (large) | ~500–2,000 | Noticeable | | Flying machine (large) | ~1,000–5,000 | Significant |
Plugins That Protect Against Redstone Abuse
Spark — The performance profiling tool. Run /spark profiler during a lag event and it will show you exactly which operations are consuming CPU. Redstone-related operations appear under tile entity processing.
RedstoneLimit (or CraftBook RedstoneGates) — Allows per-block rate limiting of redstone signals. Set a maximum of N updates per second per contraption. Most legitimate uses stay well under the limit; griefing machines do not.
Pipe / ClearLag — These plugins provide visibility into slow tile entities and allow targeted removal without needing to TP to the location.
Server Configuration to Reduce Redstone Exposure
In paper.yml (Paper 1.19+):
tick-rates:
sensor:
villager:
secondarypoisensor: 40
behavior:
villager:
validatenearbypoi: 60
redstone-implementation: EIGENCRAFT
The EIGENCRAFT redstone implementation significantly reduces the block update cost of complex circuits by batching updates more intelligently. Switching to it is a free performance gain on any Paper server.
Setting Community Rules
Technical rules are only as effective as enforcement. Post clear guidelines in your server's /rules:
- No active clocks running while offline
- Hopper networks must be enclosed and limited to 64-hopper chains
- Flying machines must be tested in the creative world first
Pair these rules with the Spark profiler running on a scheduled task (hourly profiler reports logged to a channel in your admin Discord), so you catch misbehaving contraptions before they cause a visible lag event.
Space-Node's Ryzen 9 hardware handles redstone more gracefully than older processors due to the massive L3 cache advantage — but no hardware is immune to a zero-tick machine. The best protection is a combination of smart plugins and a vigilant admin team.