Backups

Backups

All mod data lives in one SQLite file, claims.db. The mod copies it on a schedule and on demand.

Automatic backups

Key	Default	Meaning
DAYTIME_MAKE_BACKUP	["6:00","12:00","18:00","0:00"]	Server clock times (H:MM) of backups. A time that is not a time is skipped with a log line.
FULL_BACKUP_FOLDER	""	Where to put them. Empty = claims_backups in the game's data folder.
BACKUP_FOLDER_NAME_IN_DATA_FOLDER	claims_backups	Name of that folder.
BACKUP_KEEP_COUNT	0	How many automatic backups to keep; older ones are deleted. 0 keeps all.

Automatic copies are named by time, claims_2026-10-21_18-00-00.db, so they sort in order. Only files with exactly that name pattern are ever deleted by BACKUP_KEEP_COUNT; anything else in the folder is left alone.

Manual backups

/cadmin backup makes a copy right now, backup_manually_claims.db, and reports whether it worked. It is never deleted automatically, but the next manual backup overwrites it. Make one before risky changes: editing levels, mass deletions, updating the mod.

Restoring

1. Stop the server. The mod keeps data in memory and writes it back, so a database swapped on a running server gets overwritten.
2. Move the current claims.db aside.
3. Copy the backup into its place and name it claims.db (or whatever DB_NAME says).
4. Start the server and check the log for load errors.

Damaged rows are skipped on load with a log message, so the server still starts.

⚠️ Never edit the database while the server is running.

See also

• Installation