Minecraft view-distance and simulation-distance: how to adjust your server

Two settings with different effects

view-distance controls the range of chunks sent to clients. simulation-distance controls the range of entity simulation. Showing more terrain and sustaining more activity are different tasks.

Server software and plugins may introduce additional settings. Use documentation for your running version; do not paste Paper configuration into a Velocity file or mix keys from different versions.

Plan a comparable test

1. Record current values, software, version and typical load. Back up server.properties.
2. Choose a representative situation: exploration, active bases or the activity associated with your problem. An empty-server test does not represent that load.
3. Stop the server and change one property at a time. Preserve other keys and avoid duplicates.
4. Restart and repeat the situation. Compare tick times, memory and player experience with the same method.
5. Restore the backup if results worsen or a mechanic no longer behaves as expected. Record the result before making another change.

Look beyond the distance value

Determine whether the issue is terrain appearing slowly, activity no longer being simulated or the server taking too long to process ticks. These symptoms require different checks; lowering both values together can hide the cause.

Do not treat max-players as predicted capacity. It only limits accepted connections. CPU, world, mods, plugins and activity affect the load the server can sustain.

Use the configurator as a starting point

The tool generates a five-property snippet, not a complete server.properties file. Use it to prepare a test, but keep your backup and review each key. Aim for a configuration that works for your community, not the highest possible number.