How to Reset the Distant Horizons LOD Cache
A stale LOD database can preserve old terrain, show the wrong resource-pack colors, or make a dimension look incomplete. Back up your world first, then remove only the affected DH data rather than deleting the save.
Common symptoms
- old terrain remains after an update
- LOD colors do not match the resource pack
- the Nether or End shows terrain from another profile
- generation works in a new world but not the old one
Step-by-step fix
Back up the world and instance
Close Minecraft completely and make a copy of the save and instance before changing generated data.
Change one cause at a time
If the problem started after a resource pack change, restart Minecraft first. DH may need to rebuild LODs with the new textures.
Find the DH data location
Use the Distant Horizons settings or the official FAQ to identify the LOD data folder for the world or server. Do not delete the Minecraft save folder.
Confirm the world and dimension identity
Record the instance, save name, server address and port, and affected dimension. A changed server identity or reused profile can make valid LOD data appear to belong to the wrong world.
Remove only the affected LOD data
Delete or move the relevant DH database folder, then launch the same profile and allow the area to regenerate.
Verify every dimension
Check the Overworld, Nether, and End separately. Server and Realm identifiers can also affect where LOD data is stored.
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.