Direct answer

Exploring new terrain triggers world generation, structure placement, lighting and chunk sending; lag may come from generation CPU or from client/network streaming.

Identify the failing layer

World generation and network chunk delivery happen at different stages; profiling can distinguish them.

First checks and evidence

  • Compare movement inside already generated chunks with a previously unexplored area.
  • Measure MSPT while a player explores and inspect spark for world-generation or chunk-related work.

Admin diagnosis and repair

  1. Check disk throughput, simulation/view distances and whether multiple players explore in separate directions.
  2. If generation is the actual bottleneck, consider pre-generating an appropriate area off-peak and keep a world backup.

Verify the fix: Use the same exploration route and player count to compare spike MSPT and time to receive chunks before and after.

Important safety note

Do not run uncontrolled world pre-generation on a full production server during peak play. Expanding render distance can make chunk demand worse.

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