HumanitZ Dedicated Server Troubleshooting Guide

HumanitZ Dedicated Server Troubleshooting Guide

Most HumanitZ server problems are one of a few things: a version mismatch after an update, a setting the server does not read, a port the browser cannot reach, or a missing file. This guide covers the common cases with the diagnostic step and the fix for each. Paths, keys and commands are taken from the files shipped with the dedicated server and checked against the 1.1A build of 20 October 2026.

Issue: Players Cannot Join After an Update

Symptoms: the server runs, but players who updated their game cannot join it, or it disappears from their browser.

• Update the server. HumanitZ 1.1 shipped on 19 October 2026, followed by the 1.1A hotfix on 20 October and 1.1B on 23 October; for each hotfix the developers asked every server owner to restart to pull the patch. A client on 1.1 needs a server on 1.1.
• No wipe is required. Existing saves load on 1.1. The developers do recommend a full wipe to pick up the server-side changes, so plan one for a quiet moment rather than rushing it.
• Leave the experimental branch. Experimental 1.1 is retired and will not receive updates. A server still installed from it must move back to the default branch.

Issue: Server Not Showing in the Browser

Symptoms: the server starts but players cannot find it in the in-game browser.

• Ports: the game port defaults to 7777 UDP and the Steam query port to 27015 UDP. Open both, and forward both on a home router:

  # Linux (ufw):
  sudo ufw allow 7777/udp
  sudo ufw allow 27015/udp

• Check which port it bound to: the developers' readme says to look in the log for the port the server actually uses, and to force it with -port=7777 on the command line if needed.
• Search ID: SearchID="HumanitZ_Dedicated" is the public pool. Any other value hides the server from the default list; players must search for that ID.
• Server name: do not use the word "Official" in ServerName. The developers warn that such a server may not start or show up in the list.
• Give it a few minutes: a freshly started server can take a few minutes to appear in the Steam list.

Issue: Admin Commands Not Working

Symptoms: typing /god, /spawn or other commands in chat does nothing.

1. Check the admin password in GameServerSettings.ini; it is case-sensitive and sits in quotes:

   [Host Settings]
   AdminPass="MySecurePass123"

2. In game, type /AdminAccess MySecurePass123 in chat. This grants admin for the session.
3. For admin that survives reconnects, add your Steam ID to AdminList.txt in the HumanitZServer folder, one ID per line.
4. Check the spelling of the command against our admin commands list, which follows the server's own readme.

Issue: Loot Not Respawning

Symptoms: buildings stay empty and searched containers never refill.

• Check that loot respawn is on and the timers are sensible. Both timers are in real minutes:

  [World Settings]
  LootRespawn=true
  LootRespawnTimer=60
  PickupRespawnTimer=90

• Check the spelling: PickupRespawnTime without the final r is ignored.
• Check the Rarity keys. Each item category goes from 0 (scarce) to 4 (abundant), so a whole category set to 0 makes that loot rare everywhere.
• To restock the whole map at once, the RCON command resetspawners true resets every spawner as if the game had just started.

The loot configuration guide covers every loot key.

Issue: Server Crash on Startup

Symptoms: the server process exits immediately or within seconds of launch.

1. Read the end of HumanitZServer.log. A port already in use, a damaged save or a broken settings line usually shows there. On Linux, ss -ulpn | grep 7777 shows what holds the game port.
2. Run SteamCMD validate on the server files.
3. Check free disk space. A full disk makes Unreal Engine servers fail during saves.
4. If the server will not start on Linux at all, see the steamclient.so fix.

Issue: Server Lag

Symptoms: rubber-banding, delayed actions, or high ping for everyone.

• AI load: sustained high CPU on a busy server usually means too much AI. Lower ZombieAmountMulti and HumanAmountMulti, or test values live with the RCON commands overridezeekmulti and overridebanditmulti.
• Rhythmic hitches: a short freeze on a fixed rhythm matches the autosave. The interval is SaveIntervalSec, 300 seconds by default; on slow storage, move the server to SSD rather than disabling saves.
• Memory: an empty 1.1 server held about 3.3 GB of RAM on our test node. A host that starts swapping lags badly; restart at a quiet hour or give the server more memory.

The performance guide covers each lever.

Issue: Progress Lost on Disconnect or Restart

Symptoms: players rejoin and find recent progress gone.

• Update to 1.1. Its patch notes list a fix to the async save system, which had caused loss of server-side game progress and local saves.
• Check SaveIntervalSec. It must not be 0, which disables autosave.
• Before a planned restart, save over RCON with save, or use QuickRestart, which saves and restarts in one minute. A killed process cannot save.

Professional Hosting

On Supercraft the server updates itself from Steam when it restarts with auto-update on, which is the default, the ports are set up for you, and the loot, AI and save settings on this page are fields in the configuration screen. Host your HumanitZ server with Supercraft and our support team handles the rest.