Distant Horizons Server Commands and Distant Generation
Server-side Distant Horizons behavior is different from a client-only installation. Server owners need a compatible server setup, matching client expectations, and the correct generation settings before players can receive distant LOD data.
Common symptoms
- players see no server LODs
- the /dh command is unavailable
- generation causes timeouts
- server and client show different terrain
Step-by-step fix
Use a matching build
The official server guidance strongly prefers the same Distant Horizons version and build on the server and client.
Enable Distant Generation where required
Distant Generation must be enabled on both sides when the server is responsible for generating or sending LOD data.
Use /dh only on a supported server setup
Distant Horizons commands are server-side. Use /help dh or tab completion to inspect the commands available in your exact plugin or mod environment.
Pre-generate carefully
Pre-generation can improve the experience for players, but it also consumes CPU, storage, and bandwidth. Start with a bounded area and monitor the server.
Lower bandwidth or request distance if needed
Timeouts and connection lag can require lower server or client request settings. Change one limit at a time and test with a second player.
Sources and verification scope
Reviewed by the DistantHorizonsGuide Editorial Team against the public release listing and project distribution page. These instructions are conservative troubleshooting steps, not a guarantee for every modpack. Exact menu names and compatibility can change by Minecraft, loader, and DH build.
Still stuck?
Record your Minecraft version, DH version, loader, shader pack, GPU, and crash log before asking the community. That information makes compatibility problems much easier to diagnose.