HumanitZ Server Password & Whitelist Setup
Community groups, friend groups and clan servers all need to keep strangers out. HumanitZ gives you a server password, a whitelist built from reserved slots, a private search ID, and ban and admin lists kept in plain text files. This guide covers each one as the dedicated server implements it.
Everything here comes from the files the developers ship with the dedicated server, REF_GameServerSettings.ini, ReadMe.txt and RCONCommands.txt, checked against the 1.1A build of 20 October 2026. There is no whitelist.txt, no WhitelistEnabled key and no command that reloads a whitelist: guides that show them describe a different game.
🔑 Password
One string in the settings file. Anyone who knows it can join. Good for semi-private servers where the password lives in a private Discord channel.
📋 Whitelist
Reserve every slot and list the allowed players' Steam IDs. Only those accounts can take a slot, whether or not they know a password.
Where the Files Live
All the access files sit in the HumanitZServer folder of the server installation, next to GameServerSettings.ini. The server writes some of them itself, such as F_ConnectedPlayers.txt; you create the others. A player's ID in all of them is the Steam ID, which the server calls the NetID.
Setting a Server Password
[Host Settings]
Password="YourSecurePassword123"
Restart the server for the password to take effect. Players see a password prompt when they join from the server browser.
Password Best Practices
- Use at least 10 characters mixing letters and numbers, and keep it inside the double quotes.
- Change it if it has leaked beyond your group.
- Share it only in private channels. A password posted in a public Discord protects nothing.
- For a closed group, combine it with the reserved-slot whitelist below.
Making a Whitelist With Reserved Slots
HumanitZ has no separate whitelist switch. The developers' readme describes the method instead: reserve as many slots as the server has, and list the players who may use them.
[Host Settings]
MaxPlayers=8
; Slots kept for players listed in F_ReservedSlots.txt. 0 disables.
ReserveSlots=8
Then create F_ReservedSlots.txt with one Steam ID per line:
76561198012345678
76561198087654321
76561199001122334
With every slot reserved, only the listed players can take one, so the server works as a whitelist. Reserve half the slots instead and your regulars always get in while the rest stay open to the public. Edit the file while the server is stopped, then start it.
Hiding the Server With a Search ID
[Host Settings]
SearchID="HumanitZ_Dedicated"
HumanitZ_Dedicated is the public pool. Change it to your own value and the server disappears from the default list; players then find it by searching for your search ID. It is not a lock on its own, but together with a password it keeps random players from even seeing the server.
Finding Steam IDs
- RCON: the
Playerscommand returns every connected player's name and Steam ID. - PlayerIDMapped.txt: the server maps each ID it has seen to the player's name.
- PlayerConnectedLog.txt: a log of connects and disconnects with the time, Steam name and ID.
- F_ConnectedPlayers.txt: the players connected right now.
Managing the Ban List
Bans are stored in F_BannedPlayers.txt, one Steam ID per line. An admin who bans in game adds the player to it automatically, and you can edit it by hand. Over RCON:
ban 76561198099999999 ; bans and kicks the player if connected
unban 76561198099999999
kick 76561198099999999
fetchbanned ; lists the banned Steam IDs
For a ban that survives a new Steam account, use the hardware ID. HWIDLog.txt records each player as NetID@HWID; copy the part after the @ into F_BannedPlayersHWID.txt.
[Host Settings]
; Reject players banned on the official servers.
UseGlobalBanList=true
; false = players on a family-shared copy of the game cannot join.
AllowFamilySharing=true
The server log flags players who join through family sharing, so turn sharing off if a banned player keeps coming back on a borrowed copy.
Permanent Admins
Players listed in AdminList.txt, one Steam ID per line, are always admin. Anyone else becomes admin for the session by typing /AdminAccess with the AdminPass from the settings file:
[Host Settings]
AdminPass="ChangeThisAdminPassword"
Test it: after setting up the whitelist, try to join from a Steam account that is not in F_ReservedSlots.txt. If it gets in, check that ReserveSlots equals MaxPlayers.
Professional Hosting
On Supercraft the password, admin password, reserved slots, global ban list and family sharing are fields in the server's configuration screen, the player count comes from your plan, and the access files go in the file manager's Config folder. Host your HumanitZ server with Supercraft and control access without a command line.