Compatibility with Distant Horizons

[tesseract-two]

As of Distant Horizons 2.3, Distant Horizons will generate LODs on the server and send them to clients. However, it stores the LODs in SQLite databases in the data folders of the world (worldname/data/DistantHorizons.sqlite, worldname/DIM-1/data/DistantHorizons.sqlite, worldname/DIM1/data/DistantHorizons.sqlite). These LOD databases can be quite large (my world's is 3.2gb) and git can't version them, leading to large backup sizes. For example, my world is 4gb, and the corresponding FastBack backup (with a fixed retention of 7) is 54gb.

I'm not sure how FastBack could properly version the Distant Horizons database, so maybe FastBack could exclude those files from backups? Maybe with a setting to re-enable, with a warning about large backups?

[pcal43]

You can easily do this by configure the .gitignore file:

https://git-scm.com/docs/gitignore

[0ctoqus]

I put this here if someone needs it. If FastBack isn't ignoring Distant Horizons files (DistantHorizons.sqlite*, lod/) even with a .gitignore in world_save/data/, it's likely because those files were already tracked by Git.

1. Configure world_save/data/.gitignore:

Make sure your world_save/data/.gitignore file (and other dimension folders) contains:

lod/
DistantHorizons.sqlite
DistantHorizons.sqlite-shm
DistantHorizons.sqlite-wal

2. Untrack Files from Git (via Terminal):

• Close Minecraft / Server
• Navigate to your world's root directory (where the .git folder is).
• Run these commands:

git rm -r --cached .  # Untrack all files, keep on disk
git add .             # Re-add, respecting .gitignore rules
git commit -m "Untracked Distant Horizons files now ignored"

Restart Minecraft / Server. FastBack will now ignore these files. If using remote backups, you may git push manually to sync the change.

3. Restart the game or the server and do a new backup, it should be ok