Redstone Lag and How to Avoid It

Redstone lag occurs when complex circuits, uncovered hoppers, and excessive block updates push a Minecraft server's computation time beyond 50 milliseconds per tick (MSPT). When the game cannot finish processing a tick within that 50 ms budget, the simulation slows down below the standard 20 ticks per second (TPS). You can prevent lag by covering open hoppers, reducing redstone dust updates, and turning off clocks when they are not needed.

World & PerformanceIntermediateClocks & timingSignal strength

What Is Redstone Lag?

Minecraft runs on a central game loop where every cycle is called a game tick. Normally, the game processes 20 game ticks per second (TPS). Because most redstone components take a multiple of 2 game ticks to change state, the community uses the term redstone tick to describe a 2-game-tick interval (0.1 seconds).

Server-side redstone lag happens when your computer or server takes too long to calculate everything happening during a single game tick. Because actions in Minecraft are timed by tick counts rather than real-world clock time, a drop in TPS causes redstone circuits, mob movement, and machines to run noticeably slower.

The Numbers Behind Lag: TPS and MSPT

To diagnose redstone lag, players measure two core statistics:

  • TPS (Ticks Per Second): The number of game loops completed each second. The target rate is a constant 20.
  • MSPT (Milliseconds Per Tick): The actual time the server spends computing a single game tick.

Because there are 1,000 milliseconds in a second, the server has an exact budget of 50 milliseconds per tick (1000 / 20 = 50) to maintain 20 TPS. So long as your MSPT stays at or below 50, the game runs at full speed. As soon as redstone machinery, hoppers, or mob AI push MSPT above 50, TPS drops below 20 and the world lags.

In singleplayer or when hosting multiplayer, you can check your MSPT on the F3 debug screen under ms ticks, and view the TPS on the frame time graph.

Main Causes of Redstone Lag

During every game tick, the server processes scheduled block ticks, fluid ticks, entity ticks, and block entities in a strict sequence. Three major factors related to redstone contraptions consume the most MSPT:

  • Uncovered Hoppers: Hoppers are block entities that constantly search the space above them for free-floating items to pick up. Large hopper chains or sorting systems checking for items every tick add significant load.
  • Redstone Dust Block Updates: Redstone components—and especially redstone dust—generate excessive amounts of block updates whenever their power level (0 to 15) changes.
  • Always-On Clocks and Machinery: Circuits and clocks that run continuously keep scheduling block ticks and triggering updates even when no items or farms are actively being processed.
  • Mob AI in Farms: Large concentrations of animals or hostile mobs inside redstone farms add heavy entity-ticking costs on top of your circuit calculations.

Step-by-Step Build: Lag-Friendly Item Transport

One of the easiest ways to reduce MSPT in a storage system or farm is to optimize how items move. Follow these steps to convert a laggy hopper line into a low-lag transport system:

  1. Replace long hopper chains with water streams: Whenever you need to move items in bulk across a distance, use water flow instead of a long row of hoppers. Water transport is faster for bulk items and eliminates dozens of ticking block entities.
  2. Place hoppers only where items enter containers: Use hoppers only at the end of the water stream or directly beneath chests and machines where item collection is required.
  3. Cover exposed hoppers: For any hopper that pulls from another container rather than the open air, place a block with an inventory slot or a composter directly on top of it.
  4. Verify the setup: Covering a hopper with a composter or inventory block disables its constant search for floating items above it, immediately saving server processing time.

How Players Minimize Redstone Lag

Technical players design contraptions around the game loop to keep MSPT well under the 50 ms ceiling:

  • Master On/Off Switches: Add a lever to disable redstone contraptions and clocks whenever a farm is not actively in use.
  • Cutting Down Redstone Dust: Where possible, use repeaters, comparators, or opaque powered blocks instead of long, branching lines of redstone dust that step down through 15 signal strength changes.
  • Controlling Mob Spawns Around Builds: Place torches around redstone farms to prevent unwanted hostile mob spawning, and build efficient animal farms so fewer entity AI calculations compete with your circuits.

Common Mistakes

  • Leaving clocks running in loaded chunks: Leaving a fast redstone clock running continuously inside ticking chunks forces the server to process scheduled block ticks and dust updates 20 times a second forever.
  • Leaving hopper tops exposed: Building massive item sorters without placing composters or inventory blocks on top of the hoppers forces every single hopper to scan for dropped items every tick.
  • Confusing FPS with TPS: Low frame rate (rendering lag) is separate from server MSPT/TPS lag. Check ms ticks on the F3 screen when playing singleplayer or hosting to see if your redstone is actually slowing down the integrated server.

Frequently asked questions

What is a good MSPT for a redstone world?
Any MSPT (milliseconds per tick) of 50 or lower allows Minecraft to run at its full speed of 20 ticks per second (TPS). The lower your MSPT, the more headroom you have before lag starts.
Why do players put composters on top of hoppers?
Hoppers constantly search the space above them for dropped items. Placing a composter or any block with an inventory slot on top of a hopper stops it from performing those searches, which reduces server lag.
Why does redstone dust cause so much lag?
When redstone dust changes state or signal strength (from 0 to 15), it causes excessive amounts of block updates to surrounding blocks. Replacing unnecessary dust or turning off clocks stops these constant updates.
What is the difference between a game tick and a redstone tick?
A game tick is one cycle of Minecraft's main game loop (0.05 seconds at 20 TPS). A redstone tick is a community term equal to 2 game ticks (0.1 seconds), because most redstone components take multiples of 2 game ticks to change state.

Components involved

More redstone mechanics