Sometimes a Minecraft server crashes shortly after someone entered a command or changed a file. The console then often shows:
A single server tick took 60.00 seconds (should be max 0.05)
That's the watchdog: Minecraft stops the server when it hangs on a single calculation for a minute. More RAM does not help.
Common causes
- Huge values via commands, e.g. hundreds of millions of XP levels (
/xp), enchantments far beyond the game limit or stacks of thousands of items (/give). Some mods keep calculating with them – Waystones, for example, computes travel costs from XP levels – and get stuck. - Many entities or blocks at once, e.g.
/summonloops or huge/fillcommands. - Your own changes to files, mods or configs shortly before the crash.
How to undo it
- Think about what changed right before the first crash. For a command: set the value back to normal once the server runs, e.g.
/xp set PlayerName 0 levelsin the Console. - If the server no longer starts or crashes right away: restore a backup from before the change under Backups.
- For a changed file or new mod: undo the change under Files or remove the mod.
Only give commands like /xp, /give or /gamemode to players you trust. If you can't find the cause, open a ticket with the time of the crash.