HumanitZ · Troubleshooting

HumanitZ server not working?
Start here.

Most HumanitZ trouble is one setting doing more than its name says: the server pool that hides you from the browser, the save name that decides which world loads, and the RCON switch that the listing, the Players tab and the save before every stop all hang off.

humanitz — the three checks
# what fixes most HumanitZ problems
1  Not in the server browser
   → Server pool back to HumanitZ_Dedicated
2  World reset after a change
   → Check Save name in Settings
3  Unban says Player not found
   → Lift it from the ban list instead
Each one is written out below, with the panel tab you fix it on.
🔧

My HumanitZ server isn't in the server browser

Don't judge it with a Steam server checker. HumanitZ's query port never answers a Steam server query, so those tools time out on a perfectly healthy server.
1

Check the server pool

Settings → Identity & Access → Server pool. HumanitZ_Dedicated is the public pool. Anything else drops you out of the default browser, and players only find you by typing that exact ID into the search. Put it back unless you are hiding on purpose.

2

Take “Official” out of the name

The developers warn that the word Official in Server name can stop a server listing, or starting at all. Pick anything else.

3

Leave RCON on

Settings → RCON & Chat Feedback → Enable RCON. The game ships it off and we default it on: the game ties browser listing and the ping display to it, and our Players tab, the Console and the save before every stop all run through it. The port is never published and the password is generated for you.

4

Apply & restart

HumanitZ reads its settings only at boot. Hit Apply & restart, then search again.

Why: HumanitZ finds servers through Epic's online services, not Steam's server list, and Server pool decides which pool you sit in.

🔧

Our world reset, or we lost the last few minutes after a restart

Autosave interval 0 turns autosaving off entirely. Leave it at 300 unless you have a reason.
1

Check Save name first

Settings → Identity & Access → Save name picks which save loads. Change it and the server starts a fresh world; the old one stays on disk under the old name. Set it back, Apply & restart, and the old world loads again.

2

Make sure RCON is on

A stop, a restart or a settings change saves the world first, over RCON: the game answers Game saved! and only then do we stop it. With Enable RCON off that save is skipped and you lose up to the last autosave — 5 minutes at the default Autosave interval of 300.

3

Save by hand before anything risky

Console → Save world now sends the same save. Force stop sends nothing: it cuts the power, so keep it for a server that will not answer the normal stop.

4

Roll back if you need to

Worlds & backups keeps three nights of restore points plus your own saved copies. Pick one and type RESTORE. Download the current world first if there is anything in it you want.

Why: Left to itself, a HumanitZ stop is a clean exit that writes nothing — we measured it. That is why our stop asks for the save over RCON first, and why RCON off costs you the minutes since the last autosave.

🔧

I changed a setting and it went back after a restart

1

Change it on the Settings tab

GameServerSettings.ini is written from the Settings tab every time the server starts. A value typed straight into the file is replaced by the field's value at the next boot. Change the field, then Apply & restart.

2

Bringing a config from somewhere else?

Settings → Already have a config? Paste or upload it → Fill the fields. It matches what it recognises onto the fields and lists what it did not. Nothing is saved until you hit Apply & restart.

3

Console changes last until the next restart

The Console's world commands — zombie, animal and bandit multipliers, respawn times, weather, season, time of day — apply instantly and are gone after a restart. The Settings field of the same name is the one that sticks.

4

In-game admin changes too

Anything changed through in-game admin is overwritten the same way at the next start, because the file is rebuilt from your fields every boot.

Why: The game reads the file only at boot and writes nothing back when it stops — we compared it byte for byte across a stop. What replaces a hand edit is our generator writing the file from your fields.

🔧

I installed a mod and nothing changed, or players can't join with it

After a game update, a mod built for the old build usually does not crash anything — it just stops applying, on a server that looks healthy. Your build stays pinned until you press Update now on the Mods tab; check the mod count there afterwards. And Turn mods off hides our mod folder only: a .pak you put in Saved/Paks by hand still loads. More in modding your server.
1

Turn mods on

Mods tab → Turn mods on. HumanitZ loads .pak mods itself, so there is no loader to install: this switches the mod folder on and pins your game build so an update cannot land under your mods.

2

Install the file

Install a mod file takes a .pak, or a .zip with one inside, and puts it in humanitz/PakMods, the folder the game reads. Mods load at boot, so restart after adding or changing one.

3

Give every player the same pak

A server-side pak that changes content is not enough on its own. Everyone joining needs the same file in their own game.

4

Only the .pak half reaches the server

A lot of the HumanitZ scene on Nexus is UE4SS mods, which inject into the Windows game client. Our server is the native Linux build, so they do nothing there. You want the .pak.

Why: Unreal is the mod loader here. It mounts every .pak it finds under the game's Paks folder, and PakMods is mounted inside it.

🔧

How do I make myself admin on my HumanitZ server?

The admin password and the RCON password are different things. Ours generates the RCON one and never publishes its port; don't reuse either as the other.
1

Set an admin password

Settings → Identity & Access → Admin password. It ships empty, and while it is empty nobody can promote themselves. Apply & restart.

2

Claim it in chat

Join and type /AdminAccess <password> in chat. That makes you admin for the session; type it again next time you join.

3

Or don't bother for moderation

Kick, ban, announcements, heals, unsticking a player and the rest run from the panel over RCON — the Players tab and the Console — with nobody in game.

4

Bans end up in one list

Ban someone from in game and they land in the same ban list the Players tab reads, so you can lift it from the panel later.

🔧

A player can't get in: it says they're banned, or the server is full

Running a whitelist on purpose? Put yourself in F_ReservedSlots.txt first. With Reserve slots equal to Max players and you off the list, you are locked out of your own server — we did exactly that testing it. An empty list switches the whole feature off, whatever the number says.
1

Read the reason

The Console tab shows the server's own refusal: PreLogin failure: Player banned! or Server full! Not in reserved slot list. They need different fixes.

2

Banned: lift it from the list

Players tab → ban list → Lift on that row. Don't type the ID yourself: the list matches the exact string it stored, and an ID one character out answers Player not found! and leaves the ban where it was.

3

Not in the reserved list: you built a whitelist

Settings → Reserve slots. Set equal to Max players, only the NetIDs in F_ReservedSlots.txt get in. Put it back to 0 and Apply & restart, or add the player to humanitz/F_ReservedSlots.txt in the Files tab, one NetID per line. PlayerIDMapped.txt beside it maps NetIDs to names.

Why: HumanitZ writes bans to F_BannedPlayers.txt, which we keep on your volume, so they survive restarts and settings changes; the game refuses a banned account before it loads in. The HWID in the logs is no use for a ban: it changes on every connection attempt.

🔧

Zombies go down fast but hit far too hard. Is this default difficulty?

1

Know what ships

The config HumanitZ ships is not the game's own middle setting: Zombie health is 1, a notch under the scale's default of 2, and Zombie damage is 3, a notch over it, on a 0–5 ladder. Our panel starts from those same shipped values.

2

Set both to 2

Settings → Zombies, Bandits & Animals → Zombie health and Zombie damage both to 2 · Default, then Apply & restart.

Why: Every config copied from the shipped file inherits the same 1 and 3, and nothing tells you.

🔧

I typed RestartNow in the console, it said a restart was requested, and nothing happened

Same story for overridexpmulti: it answers Malformed command whatever value you give it. Use the XP rate field in Settings.
1

Use the panel's Restart

Restart at the top of the panel restarts the server for real, and saves the world first.

2

Schedule it instead

Schedule tab → Scheduled restart → pick the interval and the hour → Save.

Why: RestartNow and QuickRestart answer with success text on the Linux dedicated server and the server never goes down — we watched uptime keep climbing and the restart count stay at zero. A HumanitZ reply proves a command exists, not that it worked, and a command the game does not know comes back empty, not as an error.

💬

None of these, or still stuck?

1

Check the problems every game shares

Connections, settings that will not take, where your world is, lag: the answers that hold on every game are on the support page.

2

Write to us

The form arrives with HumanitZ already set; tell us what you tried and it saves a round trip. Pressing Need help? in your panel does the same and attaches your server, so there is nothing to look up.