How to Fix Redstone Clock Lag on a Minecraft Server

Direct answer

Locate fast or oversized redstone clocks and measure their real tick cost before changing global gameplay settings.

What it means

Fast or very large redstone circuits schedule repeated block updates and neighbor/tick work. If enough remain loaded, that workload can consume a meaningful share of the server tick budget.

If you are a player

• Check whether the symptom is low FPS on your own computer, high ping/rubber-banding, or the whole server slowing down; these are different problems.
• Note the exact time, world/area, and action that triggers the lag (exploring, a farm running, saving, many players online, and so on).
• Ask another player whether they see the same delay. Give the owner a reproducible location/action instead of only saying “the server is laggy.”

If you run the server

1. Locate the loaded clock or contraption and capture a spark profile with the machine running. Look for block/neighbor updates, pistons and related plugin work.
2. On a test copy, switch that clock off and compare MSPT to the same area with it on. A change only while the machine is loaded points toward that circuit.
3. Reduce unnecessarily fast clock pulses, continuous pistons/observers, and permanently loaded machines. Preserve the behavior required by farms and other redstone systems.
4. Do not switch redstone implementations or change global tick behavior without compatibility tests: updates can change contraption mechanics.
5. Re-enable the redesigned mechanism and verify both correct behavior and measured performance.

Important notes

• More allocated RAM does not make a slow main-thread workload faster. Change heap size only when memory/GC evidence supports it.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

• PaperMC: Profiling with spark
• PaperMC: Basic troubleshooting

Related fixes and guides