Fix: Server Can't Keep Up / Tick Loop Exception
Diagnose and fix 'Can't keep up!' warnings and tick loop crashes on your Minecraft server.
The "Can't keep up! Is the server overloaded?" message means your server is falling behind on processing game ticks. If severe enough, it can cause a tick loop crash.
Diagnosing the Cause
Install Spark
If not already installed, add Spark to your server and run /spark profiler to identify what's consuming the most CPU time.
Check TPS
Run /spark tps in Console on the XGamingServer panel. If TPS is consistently below 15, you have a significant performance issue.
Common Causes and Fixes
Too Many Entities
Farms with hundreds of mobs or large amounts of dropped items. Fix: Install ClearLag or use entity limits in bukkit.yml. See Mob Spawn Rate.
Chunk Generation Lag
New terrain being generated as players explore. Fix: Pre-generate your world with Chunky.
Heavy Redstone
Large redstone machines running every tick. Fix: Use Paper's redstone optimization settings or simplify builds.
Bad Plugins or Mods
A specific plugin or mod taking too much processing time. Fix: Check Spark profiler output for the plugin name, then optimize or remove it.
Insufficient RAM
Server running out of memory causes garbage collection pauses. Fix: Increase RAM in Startup and apply Aikar's Flags.
High View Distance
Large view distance means more chunks loaded per player. Fix: Reduce view-distance and simulation-distance in server.properties.
💡 Tip: Occasional "Can't keep up" messages during world generation or large events are normal. It's only a problem if they happen constantly.
See also: Performance Guide | Types of Server Lag
If you need help, join our Discord.
How is this guide?
