> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fourseasonshosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# "Can't Keep Up! Minecraft Server Message"

That console warning — "Can't keep up! Is the server overloaded? Running X ms or Y ticks behind" — means your server can't finish processing a tick before the next one starts. In plain terms: it's lagging. Below is what drives this and the levers you have to pull.

## Understanding TPS

Minecraft servers run on a tick loop, targeting 20 Ticks Per Second (TPS). When a server can't hit that target, every connected player feels it — regardless of their own hardware or connection.

Run `/tps` on Paper or Spigot to check your current rate. Running a modded server instead? TPS alone won't tell you much — install spark to profile exactly where the time is going.

Rough guide to what the numbers mean:

| TPS      | What it means                                                        |
| -------- | -------------------------------------------------------------------- |
| 20       | Healthy — no issues                                                  |
| 19–20    | Slight dip, not noticeable in gameplay                               |
| 17–19    | Early signs of strain, still mostly playable                         |
| Below 17 | Noticeable lag — block breaking, combat, and eating all feel delayed |

## Common Root Causes

### Memory Pressure

If your server is starved for RAM, performance suffers. Every loaded plugin, mod, and connected player takes up memory — run out, and the server has nowhere to put that data, so it stalls.

Check current usage from the **Console** page of your panel. If you're consistently near the ceiling, enabling the [Aikar startup flags](how-to-enable-the-aikar-startup-flags.md) from the **Startup** page can help the JVM manage memory more efficiently.

### World and Entity Load

A handful of in-game conditions tend to be the biggest tick-time offenders:

* **Entity overload** — Dense mob farms or large piles of dropped items pile up entities in one chunk, and the server has to tick each one. Clean up with:
  | Command                               | What it does                                             |
  | ------------------------------------- | -------------------------------------------------------- |
  | `kill @e[type=minecraft:item]`        | Clears dropped items only                                |
  | `kill @e[type=minecraft:ENTITY_NAME]` | Removes a specific entity type (swap in the entity's ID) |
  | `kill @e[type=!player]`               | Wipes every entity except players — use with care        |
* **Hopper spam** — An uncovered hopper continuously scans for nearby item entities even with nothing to collect. Cap it with a chest or any inventory block on top and the scanning stops.
* **Fluid simulation** — Large, actively-flowing bodies of water or lava generate constant block updates, which adds up fast at scale.
* **Chunk generation** — Rendering brand-new terrain on the fly is expensive, and worse with heavier world-gen mods. Pre-generating the map with [Chunky](https://modrinth.com/plugin/chunky) shifts that cost to a controlled batch job instead of live gameplay.

## Quick Wins to Cut Lag

* [Reduce view distance](how-to-change-a-minecraft-servers-view-distance.md)
* [Reduce simulation distance](how-to-change-a-minecraft-servers-simulation-distance.md)
* Pre-generate the world with [Chunky](https://modrinth.com/plugin/chunky)
* [Tune your startup flags](how-to-enable-the-aikar-startup-flags.md)
* [Tune mob spawn rates](how-to-change-minecraft-server-mob-spawn-rates.md) *(Paper/Spigot only)*
* [Trim memory usage](how-to-reduce-minecraft-server-memory-usage.md) *(Paper/Spigot only)*