Menu
 

HumanitZ Server Maintenance: Updates, Wipes & Performance

HumanitZ Server Maintenance: Updates, Wipes & Performance

HumanitZ left Early Access with the 1.0 release in February 2026 and keeps shipping patches: the 1.09 patch series in the summer, an experimental 1.1 branch from late August, 1.1 itself on 19 October 2026 and the 1.1A hotfix a day later. A server that is not updated stops accepting players on the new version, and a server that never restarts carries a long session's memory with it. A light routine prevents both. Paths and commands below are checked against the 1.1A build.

🔄 Updates

Players on a newer game version cannot join an older server. When a patch lands, update the server the same day; the 1.1A hotfix notes asked every server owner to restart to pull it.

🧹 Restarts

Like most Unreal Engine survival servers, a long-running HumanitZ server is healthier after a regular restart at a quiet hour.

Updating the Server via SteamCMD

The dedicated server's Steam app ID is 2728330. The Linux build is the linuxbranch beta of that app. Stop the server before updating.

Linux update script (update-humanitz.sh):

#!/bin/bash
echo "[$(date)] Stopping HumanitZ server..."
sudo systemctl stop humanitz.service

echo "[$(date)] Updating via SteamCMD..."
/usr/games/steamcmd \
  +login anonymous \
  +force_install_dir /home/steam/humanitz \
  +app_update 2728330 -beta linuxbranch validate \
  +quit

echo "[$(date)] Starting HumanitZ server..."
sudo systemctl start humanitz.service
echo "[$(date)] Update complete."
chmod +x update-humanitz.sh

Windows update command:

C:\steamcmd\steamcmd.exe +login anonymous ^
  +force_install_dir "C:\HumanitZServer" ^
  +app_update 2728330 validate ^
  +quit

After an update, compare HumanitZServer/REF_GameServerSettings.ini with your own GameServerSettings.ini. The update refreshes the reference file, so new settings show up there first: 1.1 added WeaponDurabilityMulti, HeadshotOnlyMode, BackpackCleanup and a new meaning for RecycleCar.

Scheduled Daily Restarts (Linux systemd)

# /etc/systemd/system/humanitz.service
[Unit]
Description=HumanitZ Dedicated Server
After=network.target

[Service]
User=steam
WorkingDirectory=/home/steam/humanitz
ExecStart=/home/steam/humanitz/HumanitZServer.sh -log -port=7777 -queryport=27015
Restart=on-failure
RestartSec=15s

[Install]
WantedBy=multi-user.target
# /etc/systemd/system/humanitz-restart.service
[Unit]
Description=Restart the HumanitZ server

[Service]
Type=oneshot
ExecStart=/bin/systemctl restart humanitz.service
# /etc/systemd/system/humanitz-restart.timer
[Unit]
Description=Daily HumanitZ restart

[Timer]
OnCalendar=*-*-* 05:00:00
Persistent=true

[Install]
WantedBy=timers.target
sudo systemctl daemon-reload
sudo systemctl enable --now humanitz.service humanitz-restart.timer

If you run RCON, send save a minute before the timer fires, so the restart never costs players the minutes since the last autosave.

World Wipe: Fresh Start

To generate a completely new world, which removes all player structures, vehicles and loot state:

  1. Stop the server.
  2. Back up the existing save: cp -r /home/steam/humanitz/HumanitZServer/Saved/SaveGames ~/backups/
  3. Delete the save contents: rm -rf /home/steam/humanitz/HumanitZServer/Saved/SaveGames/*
  4. Start the server. A fresh world generates on first load.

1.0 required a new save. 1.1 does not, but the developers recommend a full wipe when updating to it so the world picks up the server-side changes.

Config-Only Change (No World Wipe)

To change settings such as loot, the player cap or PvP without touching the world:

  1. Stop the server.
  2. Edit HumanitZServer/GameServerSettings.ini.
  3. Start the server. Settings are read at launch and the world data is untouched.

Performance Monitoring

Warning signs worth acting on:

  • Memory close to the machine's limit: restart at a quiet hour, and lower ZombieAmountMulti and HumanAmountMulti if it keeps climbing. An empty 1.1 server held about 3.3 GB on our test node, so measure from that floor.
  • Rubber-banding on a fixed rhythm: it matches the autosave, SaveIntervalSec, 300 seconds by default. Move the server to SSD or NVMe rather than disabling saves.
  • A setting that does not seem to apply: the server log lists the values it loaded at start. A key it does not recognise is ignored without an error.
# Linux: memory of the server process, every 10 seconds
watch -n 10 "ps -o rss= -p \$(pgrep -f HumanitZServer-Linux-Shipping | head -1) | awk '{print \$1/1024 \" MB RAM\"}'"

Pre-Update Checklist

  • ☑️ Announce the update window to players (Discord, welcome message).
  • ☑️ Back up HumanitZServer/Saved and GameServerSettings.ini.
  • ☑️ Stop the server.
  • ☑️ Run SteamCMD with the validate flag.
  • ☑️ Read the patch notes for save and settings changes, and diff the reference settings file.
  • ☑️ Start the server and check that the log reaches Session created! and the world loads.

Save compatibility: major HumanitZ updates have changed what a save needs. Before applying one, read the official Steam patch notes for whether a wipe is required or recommended, and keep the backup until the new version has run for a few days.

Professional Hosting

On Supercraft the server updates from Steam when it restarts with auto-update on, the default; restart schedules and daily backups are built in. Host your HumanitZ server and let us handle the maintenance so you can focus on your community.

Tired of fighting this issue every patch?

Run a managed Humanitz server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Humanitz hosting plans →
Top