☰

Redstone Lag

TPS suffers from heavy redstone activity. Fast clocks and large circuits schedule huge numbers of block updates per tick, and the server spends its time processing them instead of running the game smoothly.

What does this error mean?
Redstone components schedule tile ticks when they change state. Tight clocks and sprawling contraptions can fire thousands of updates every tick. 'Excessive tile ticks' means redstone is dominating the tick budget. 
Excessive tile ticks
Most Common Causes
  • Always-on redstone clocks (especially fast ones).
  • Very large or chained redstone contraptions.
  • Many observers reacting to constant changes.
  • Hopper-clock timers running nonstop.
  • Laggy farm logic built on tight clocks.
How To Diagnose
  1. Use spark to attribute tick time to redstone/block-tick work.
  2. Locate active clocks, look for areas with constant block updates.
  3. Temporarily cut power to suspect contraptions and watch TPS.
  4. Check farm designs for unnecessary fast clocks.
Recommended Fixes
  • Replace fast clocks
    Swap tight clocks for observer-based pulses, daylight sensors, or slower comparator timers.
  • Gate contraptions
    Add on/off switches so circuits only run when actually needed.
  • Simplify designs
    Rebuild laggy farms with more efficient, update-light logic.
  • Limit always-on logic
    Avoid perpetual clocks, trigger redstone on events instead of running it constantly.
Analyze My Log
Frequently Asked Questions

Often yes, an observer only fires on change, whereas a clock fires constantly.

Profile with spark, then toggle suspect contraptions off and watch TPS recover.

Yes, the same tick budget applies, but it is most painful on shared servers.