Direct answer

Profile villager-heavy areas and reduce excessive AI, pathfinding, workstations, farms, or loaded populations.

What it means

Large or badly designed villager setups can add tick cost through AI, pathfinding, points-of-interest, trading/workstation behavior, and the other entities or redstone around the farm.

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. Use a profiler while the villager trading hall or breeder is loaded. Confirm whether villager AI, pathfinding, POI/workstation lookups, collisions, or a nearby machine dominates tick time.
  2. Compare the same area with the relevant villagers or associated machines inactive on a test server. Identify what actually reduces MSPT before changing a server-wide value.
  3. Reduce excessive loaded villager populations and repeated pathfinding caused by blocked beds, workstations, or overcrowded layouts; ensure farms still work as intended.
  4. If testing villager AI optimizations in Paper-derived software, consult the exact fork/version configuration and document trading, breeding or iron-farm behavior changes.
  5. Re-test under the same chunk loading and player count, and compare profiler results rather than relying on total entity count.

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.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000