HumanitZ Server Password & Whitelist Setup

HumanitZ Server Password & Whitelist Setup

Not every HumanitZ server is meant for the general public. Community groups, private friend groups, and clan servers all need to restrict access to trusted players. HumanitZ provides two tools for this: a server password (simple, shared secret that anyone with the string can use) and a Steam ID whitelist (per-player access control based on Steam accounts). This guide covers both approaches and how to combine them for maximum security.

Setting a Server Password

Open GameServerSettings.ini (located at /TSS/Saved/Config/WindowsServer/GameServerSettings.ini) and add or edit:

[ServerSettings]
# The password players must enter to join
ServerPassword=YourSecurePassword123

# Keep the server in the public browser (password still required to join)
bPublicServer=true

# OR: hide the server from the browser entirely (share IP directly)
# bPublicServer=false

After saving, restart the server for the password to take effect. Players will see a password prompt when they click Join on your server in the browser.

Password Best Practices

• Use at least 10 characters, mixing letters and numbers (avoid special characters — some can break the config parser)
• Rotate the password periodically if you suspect it has leaked beyond your intended players
• Share the password only in private channels — a leaked password shared in a public Discord is effectively no protection
• For maximum security, combine a password with a whitelist — the password stops casual attempts; the whitelist stops anyone who obtained the password

Setting Up a Whitelist

HumanitZ's whitelist is a plain text file where you list permitted Steam64 IDs — one per line. Create or edit the file at:

# Windows:
C:\HumanitZServer\TSS\Saved\Config\WindowsServer\whitelist.txt

# Linux:
/home/steam/humanitz/TSS/Saved/Config/LinuxServer/whitelist.txt

# whitelist.txt
# Lines starting with # are ignored
# Add one Steam64 ID per line

76561198012345678    # GameTag_Alex
76561198087654321    # GameTag_Sarah
76561199001122334    # GameTag_Marcus

Enable the Whitelist in Config

[ServerSettings]
# Enable Steam ID whitelist enforcement
WhitelistEnabled=true

# Path to the whitelist file (relative to server directory or absolute)
WhitelistFile=TSS\Saved\Config\WindowsServer\whitelist.txt

Finding Steam64 IDs

You need each player's 17-digit Steam64 ID (looks like 76561198XXXXXXXXX). Two methods:

• SteamID Finder: Ask the player to share their Steam profile URL, then look it up at steamidfinder.com
• Admin command: Once a player has joined (on a non-whitelisted server temporarily), use the in-game admin command /playerlist to see all connected Steam64 IDs
• Server log: When a player joins, the Steam64 ID is logged in TSS.log — grep for Player connected

# Find Steam64 IDs in server log:
grep "Player connected" /home/steam/humanitz/TSS/Saved/Logs/TSS.log | tail -50

Managing the Ban List

Banned players are stored in a separate file. Banning via admin command auto-populates this file:

# In-game admin command:
/ban [SteamID]          — Bans and immediately kicks the player
/ban [SteamID] "reason" — Ban with a reason logged to the ban file
/unban [SteamID]        — Remove a player from the ban list

The ban list file (banlist.txt) can also be edited manually — same format as the whitelist:

# banlist.txt
76561198099999999    # Banned: griefing and base destruction

Combining Password + Whitelist

For the tightest access control, use both simultaneously:

[ServerSettings]
ServerPassword=ClubhouseKey2026
WhitelistEnabled=true
bPublicServer=false    ; Hidden from browser — players must Direct Connect with IP + password

With this configuration: players must know the server IP, enter the correct password, and have their Steam64 ID in the whitelist. Three independent barriers against unwanted access.

Applying Changes Without Full Restart

You can reload the whitelist and ban list without restarting the server using the admin command:

/reloadwhitelist

This re-reads whitelist.txt and banlist.txt immediately. Useful for adding a player during a session without kicking everyone.

Professional Hosting

Manage whitelists and passwords from a clean web dashboard. Host your HumanitZ server with Supercraft and control server access without editing config files directly.