Shared Thu, 04 Jun 2026 06:36:16 GMT·Auto-expires 7/4/2026

Watchdog tick timeout

Forge 47.3.0MC 1.20.1

What happened

The MC server's watchdog killed the tick thread after it ran too long.

Try this first

Set max-tick-time=-1 in server.properties (or upgrade RAM tier). Tick lag from a heavy mod is the usual cause — see the Health tab for tick_lag history.

Where we saw it

---- Minecraft Crash Report ----
Description: Watching Server

A single server tick took 60.00 seconds (should be max 0.05)
Considering it to be crashed, server will forcibly shutdown.
Watching Server: kept up to 60 ticks behind

Minecraft Version: 1.20.1
Forge: net.minecraftforge:47.3.0
Watchdog tick timeout — Minecraft crash diagnosis | CoalHosting | CoalHost