Minecraft Server Lag Checklist

Use this checklist when players report lag and you need a fast, organized triage path.

#1. Identify the Lag Type

| Symptom | Likely type | | --- | --- | | Blocks reappear | TPS or server delay | | Client stutters | FPS or rendering | | Chat delayed for one player | Ping or packet loss | | Terrain missing | Chunk send, client render, or server chunk load | | Everyone freezes | TPS spike, GC, storage, or host stall |

Read TPS vs FPS if reports are mixed.

#2. Capture Minimum Evidence

Record:

1. Time and timezone.
2. Player count.
3. TPS and MSPT.
4. Affected world and location.
5. What players were doing.
6. Recent plugin, config, or world changes.
7. Spark profile link if possible.

Use Spark profiler while the problem is active.

#3. Check Common Hotspots

| Hotspot | Guide | | --- | --- | | Plugins | Find laggy plugins | | Entities | Entity lag | | Chunks | Chunk lag | | Hoppers | Hopper lag | | Villagers | Villager lag | | CPU | High CPU usage | | RAM myths | More RAM does not always fix lag |

#4. Avoid Panic Fixes

Do not immediately:

1. Delete all entities.
2. Lower every setting.
3. Remove random plugins live.
4. Disable saving.
5. Allocate all machine memory to Java.

Those actions can break gameplay and hide evidence.

#5. Decide the Next Move

If the cause is obvious and reversible, fix it. If not, run the performance audit guide. For recurring lag, create an incident note so future staff can see what changed and why.