Redstone is one of Minecraft's most powerful features and one of the biggest sources of server lag. A single player building an unoptimized sorting system can drop your entire server's TPS to single digits.
Understanding why redstone causes lag helps you set the right limits without frustrating builders.
Why Redstone Is Expensive
Every redstone component update triggers a block update. A simple repeater clock fires 10 updates per second. A flying machine with observers can cascade hundreds of updates per tick. The server processes each update sequentially on the main thread.
A single 20-component redstone circuit is fine. But when a player builds a 500-piston door or a city-scale sorting system, you're looking at thousands of block updates per tick, and the main thread can't keep up.
Measuring Redstone Impact
Use Spark profiler to see exactly how much time redstone consumes:
/spark profiler start --timeout 120
Look for ServerLevel.tick and specifically BlockEvent entries. If block events are consuming more than 30% of your tick time, redstone is your problem.
Setting Limits Without Killing Fun
Paper Configuration
In paper-global.yml:
chunk-system:
gen-parallelism: default
redstone-implementation: ALTERNATE_CURRENT
ALTERNATE_CURRENT replaces the vanilla redstone engine with a much faster implementation. It produces identical behavior for 99% of redstone builds but processes updates significantly faster. This alone can cut redstone lag by 40-60%.
Piston Limits
In paper-world-defaults.yml, set piston push limits:
pistons:
max-pushable-entities: 12
This prevents pistons from moving more than 12 entities at once, which eliminates the worst lag machines.
Redstone Per-Chunk Limits
Plugins like RedstoneLimiter or LagAssist let you set limits per chunk:
- Maximum redstone components per chunk: 256
- Maximum hopper transfers per tick: 8
- Maximum observer updates per chunk per tick: 64
These numbers allow complex builds but prevent the mega-machines that destroy server performance.
Common Lag Machines
Hopper Sorting Systems
Hoppers check for items to transfer every tick. A wall of 200 hoppers looking for specific items generates 200 item-matching operations every tick. Use hopper optimization plugins and set transfer cooldowns.
Repeater Clocks
Infinite redstone clocks with no output are pure waste. Plugins can detect and break looping circuits automatically.
Observer Chains
Observers looking at each other create update cascades. A single pair of facing observers fires 20 updates per second indefinitely. Set observer rate limits or ban facing observer pairs.
The Right Hardware for Redstone Servers
Redstone processing is entirely single-threaded. A server with heavy redstone usage needs the fastest possible single-core performance. The Ryzen 9 7950X3D handles redstone better than any other processor because its 5.7GHz clock speed processes block updates faster.
| Hardware | Max Redstone Components (20 TPS) | |----------|----------------------------------| | Xeon E-2388G | ~800 | | Ryzen 5 5600X | ~1,200 | | Ryzen 9 7950X3D | ~2,000+ |
If your community loves redstone, invest in hardware that can handle it rather than setting overly restrictive limits.
