HumanitZ Server Backup Guide
A single unexpected crash, failed update, or corrupted autosave can erase weeks of community progress on your HumanitZ server. A regular backup routine is the simplest insurance policy available to server operators. This guide covers the exact files that need backing up, a manual procedure, and automated scripts for both Windows and Linux that run on a schedule without any intervention.
๐ What to Back Up
Two folders contain everything that matters: SaveGames/ (world state, vehicle positions, loot) and Config/ (all your GameServerSettings.ini customisations).
โน๏ธ Stop First
Always stop the server before copying save files. HumanitZ holds open file handles on active saves โ copying while running can produce incomplete or corrupted backups.
Save File Locations
Windows:
C:\HumanitZServer\TSS\Saved\SaveGames\ โ World data
C:\HumanitZServer\TSS\Saved\Config\ โ Server configuration
Linux:
/home/steam/humanitz/TSS/Saved/SaveGames/
/home/steam/humanitz/TSS/Saved/Config/
Manual Backup Procedure
- Stop the server โ do not skip this step
- Navigate to
/TSS/Saved/ - Copy both
SaveGames/andConfig/to a dated backup folder:# Example target: /home/steam/backups/humanitz/2026-02-27/ - Restart the server
Automated Backup Script (Linux)
Save this as /home/steam/backup-humanitz.sh and make it executable:
#!/bin/bash
# backup-humanitz.sh โ automated HumanitZ backup
SERVER_DIR="/home/steam/humanitz/TSS/Saved"
BACKUP_ROOT="/home/steam/backups/humanitz"
DATE=$(date +%Y-%m-%d_%H-%M)
DEST="$BACKUP_ROOT/$DATE"
# Create timestamped backup folder
mkdir -p "$DEST"
# Copy world saves and config
cp -r "$SERVER_DIR/SaveGames" "$DEST/"
cp -r "$SERVER_DIR/Config" "$DEST/"
echo "[$(date)] Backup complete: $DEST"
# Keep only the last 7 days of backups:
find "$BACKUP_ROOT" -maxdepth 1 -type d -mtime +7 -exec rm -rf {} +
echo "[$(date)] Old backups cleaned."
chmod +x /home/steam/backup-humanitz.sh
Schedule it with cron to run every 6 hours:
crontab -e
# Add this line:
0 */6 * * * /home/steam/backup-humanitz.sh >> /home/steam/backups/backup.log 2>&1
Automated Backup Script (Windows โ PowerShell)
# backup-humanitz.ps1
$src = "C:\HumanitZServer\TSS\Saved"
$root = "D:\Backups\HumanitZ"
$stamp = Get-Date -Format "yyyy-MM-dd_HH-mm"
$dest = "$root\$stamp"
New-Item -ItemType Directory -Path $dest -Force | Out-Null
Copy-Item -Recurse "$src\SaveGames" $dest
Copy-Item -Recurse "$src\Config" $dest
Write-Host "Backup saved: $dest"
# Remove backups older than 7 days
Get-ChildItem $root -Directory |
Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-7) } |
Remove-Item -Recurse -Force
Schedule via Task Scheduler: Create a Basic Task โ Daily โ repeat every 6 hours โ Action: powershell.exe -File D:\Scripts\backup-humanitz.ps1
Restoring from Backup
- Stop the server completely
- Rename the current
SaveGames/folder toSaveGames_corrupt/(don't delete yet) - Copy your chosen backup's
SaveGames/into place:cp -r /home/steam/backups/humanitz/2026-02-27_04-00/SaveGames/ \ /home/steam/humanitz/TSS/Saved/SaveGames/ - Start the server and verify the world loaded correctly
- Once confirmed, delete
SaveGames_corrupt/
What Gets Preserved vs. Lost on Restore
| Data Type | Preserved by Backup? |
|---|---|
| World structures and bases | โ Yes (in SaveGames) |
| Vehicle positions and fuel | โ Yes (in SaveGames) |
| Player inventory on death | โ Yes |
| Server config (loot rates, decay, etc.) | โ Yes (in Config) |
| In-progress player sessions at backup time | โ ๏ธ Lost since last save tick |
Before Updates: Always run a manual backup immediately before applying a HumanitZ server update. Early Access updates occasionally change save formats, and rolling back to a pre-update binary may require a matching pre-update save file.
Professional Hosting
Backups handled for you, automatically, every day. Host your HumanitZ server with Supercraft and restore any previous save with a single click from our control panel.