Redstone Lag Explained

Redstone lag comes from block updates, scheduled ticks, pistons, observers, comparators, hoppers, and farm designs that keep doing work even when nobody is actively using them.

#What Makes Redstone Expensive

| Pattern | Why it hurts | | --- | --- | | Always-on clocks | Runs every tick or every few ticks forever | | Observer chains | Trigger many updates quickly | | Piston arrays | Move blocks and entities repeatedly | | Comparator storage | Checks inventory states often | | Farm automation | Combines redstone, mobs, hoppers, and chunks |

The worst redstone is not always the biggest build. A small badly designed clock in a loaded chunk can run all day.

#How to Identify It

Redstone lag is likely when TPS drops near a machine, stops when the chunk unloads, or appears in profiles around block updates, pistons, hoppers, or world ticking.

Ask:

1. Is the machine always loaded?
2. Does it have an off switch?
3. Does it run when storage is full?
4. Does it rely on rapid clocks?
5. Does it push entities or items?

If the answer is yes, review the build before changing global settings.

#Better Server Rules

Good public SMP rules are specific:

1. Large farms need an off switch.
2. No needless always-on clocks.
3. Storage overflow must be handled.
4. Farms near spawn need staff approval.
5. Chunk loaders are restricted or banned unless intentional.

These rules are easier to enforce than "no laggy farms" because players know what to build.

#Practical Fixes

For existing machines:

| Problem | Fix | | --- | --- | | Clock runs constantly | Add player-controlled switch or sensor | | Storage backs up | Add overflow disposal or larger buffer | | Many hoppers | Use water streams where appropriate | | Farm in spawn chunks | Move it or unload it when idle | | Repeated complaints | Profile near the build, then document changes |

If hoppers are part of the problem, continue with hopper lag explained and how to optimize hoppers.