Skip to content

Fix "A single server tick took 60.00 seconds"

The server runs 20 ticks a second. A watchdog thread checks that ticks keep finishing, and when one runs for too long it stops the server on purpose:

A single server tick took 60.00 seconds (should be max 0.05)
Considering it to be crashed, server will forcibly shutdown.

This happens in singleplayer too, because a singleplayer world runs on a built-in server.

The crash report’s description is Watching Server. Below it is the stack of the server thread at the moment the watchdog gave up. Read it from the top: the first frames in a mod’s package are where it was stuck. For a mod that slept for 15 seconds inside a server tick event, a NeoForge 1.21.1 server, set to max-tick-time=5000, wrote:

[Server Watchdog/ERROR] [minecraft/ServerWatchdog]: A single server tick took 5.00 seconds (should be max 0.05)
[Server Watchdog/ERROR] [minecraft/ServerWatchdog]: Considering it to be crashed, server will forcibly shutdown.

and a crash report that starts:

Description: Watching Server
java.lang.Error: ServerHangWatchdog detected that a single server tick took 5000834.00 seconds (should be max 0.05)
at java.base/java.lang.Thread.sleep0(Native Method)
at java.base/java.lang.Thread.sleep(Thread.java:509)
at com.example.examplemod.ExampleMod.lambda$new$0(ExampleMod.java:26)
at net.neoforged.bus.ConsumerEventHandler.invoke(ConsumerEventHandler.java:27)
...
at net.neoforged.neoforge.event.EventHooks.fireServerTickPost(EventHooks.java:1033)
at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:958)

ExampleMod.java:26 is the stuck line. The number of seconds in the crash report’s first line was wrong in this run (5000834.00 for a 5-second tick), so take the time from the log line instead.

Checked on 19 November 2026 on a NeoForge 1.21.1 server. The frames above are shortened.

  • A loop that never ends, such as a while that waits for a value nothing changes during the tick.
  • Waiting on the main thread for a file, a web request or another thread (future.join(), Thread.sleep).
  • Too much work in one tick, such as scanning or changing thousands of blocks at once, or loading chunks in a loop. Spread the work over several ticks.
  • A breakpoint in a dev run. A paused debugger stops the tick too, which is harmless.

The limit is max-tick-time in server.properties, in milliseconds (60000 by default). -1 turns the watchdog off. A higher limit only gives the stuck code more time. It helps while you debug a slow tick on a test server.

Crash Doctor in Linen reads the crash report and the log next to it, then names the mod, the line and what to change. It’s free. Run code every tick shows where per-tick code belongs.