Controlling Which Worlds Synchronize LOD Chunks to Players

On multiplayer servers with multiple worlds or dimensions, you may want distant terrain synchronization active in your main survival world while turning it off in compact lobbies or minigame arenas. The Distant Horizons Plugin controls per-world synchronization through player permissions rather than requiring client-side changes.

How World Permissions Work

The plugin uses the permission node distant_horizons.worlds.<world name> to determine whether a player is allowed to make LOD requests in a specific world. Because this permission is granted by default, players joining with the Distant Horizons mod will automatically receive synchronized LOD chunks across your server's worlds out of the box.

Restricting or Restoring Access Per World

To control which worlds answer client LOD requests, update your server's permission rules:

1. Check your server directory to find the exact folder name of the target world (such as world, world_nether, or world_the_end).

2. Open your server's permission manager and revoke or negate distant_horizons.worlds.<world name> for your default player group, replacing <world name> with that exact world name.

3. Grant the permission node to specific groups if you want certain players to keep requesting LOD chunks in restricted worlds.

4. Enter the world on a non-admin account with the Distant Horizons mod active to confirm that LOD synchronization behaves as intended.