Minecraft: Server crashes after a command or a change

"A single server tick took 60 seconds": when a command or your own change freezes the server – and how to undo it yourself.

2 minute read Updated 19.11.2026
Rent your own Minecraft Java Edition server – from 4,99 €/month Online within minutes, servers in Germany, cancel monthly. free 24-hour trial Early Black Week −15 %

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. /summon loops or huge /fill commands.
  • Your own changes to files, mods or configs shortly before the crash.

How to undo it

  1. 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 levels in the Console.
  2. If the server no longer starts or crashes right away: restore a backup from before the change under Backups.
  3. 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.

No Minecraft Java Edition server yet? Online within minutes – this guide works exactly the same with us.
Rent a Minecraft Java Edition server
Was this helpful?