How to Fix Entity Lag on a Minecraft Server

Direct answer

Profile the server and identify mobs, item entities, villagers, farms, or modded entities consuming tick time.

What it means

Entity ticking—such as mob AI/pathfinding, item entities, villagers, farm mechanics, or modded entities—is consuming a significant part of the server tick budget.

If you are a player

• Check whether the symptom is low FPS on your own computer, high ping/rubber-banding, or the whole server slowing down; these are different problems.
• Note the exact time, world/area, and action that triggers the lag (exploring, a farm running, saving, many players online, and so on).
• Ask another player whether they see the same delay. Give the owner a reproducible location/action instead of only saying “the server is laggy.”

If you run the server

1. Reproduce the lag while the affected farm or world is loaded, then run /spark profiler start --timeout 600 on Paper with bundled spark (or the applicable profiler for your platform).
2. Confirm that entity ticking, pathfinding, collisions, or a plugin’s entity event listeners are consuming time; do not infer this from entity count alone.
3. Find the entity type and location responsible. Check loaded farms, item drops, villagers, boats/minecarts, and plugins spawning entities continuously.
4. Reduce the source or redesign the farm on a test copy. Avoid blanket entity deletion or globally disabling AI unless the gameplay tradeoff is understood.
5. Repeat the same player/farm workload and compare the relevant profiler branch and MSPT before calling the change successful.

Important notes

• More allocated RAM does not make a slow main-thread workload faster. Change heap size only when memory/GC evidence supports it.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

• PaperMC: Profiling with spark
• PaperMC: Basic troubleshooting

Related fixes and guides