Running your own HumanitZ dedicated server gives you full control over the survival experience, from how aggressive the Zeeks are to whether bandits roam, how often airdrops fall, and how punishing death really is. All of that lives in a single configuration file, and once you understand its structure, tuning your world becomes straightforward. This guide walks through exactly where the file lives, how to launch the server, the verified Host Settings and World Settings keys, and the edit-and-restart loop that applies every change.
A quick note before we start: HumanitZ left Early Access on February 6, 2026, and is now on the full 1.0 release branch. The game is developed by Yodubzz Studios and published by indie.io. Everything below targets that 1.0 build. We won’t quote a specific patch number here because builds change frequently, so check the Steam news feed or the in-game version string if you need the exact current build. If you’d rather skip the manual setup entirely, you can spin up a ready-to-go HumanitZ server with XGamingServer and edit these same settings from a clean control panel.
Installing the dedicated server with SteamCMD
The HumanitZ dedicated server is a separate Steam application from the game itself. The game’s App ID is 1766060, but the server you install through SteamCMD uses dedicated-server App ID 2728330. The standard anonymous install command looks like this:
+login anonymous +force_install_dir +app_update 2728330 validate +quit Replace validate flag verifies file integrity, which is worth keeping every time you update so a partial download doesn’t corrupt your install.
Where the config file lives: GameServerSettings.ini
HumanitZ reads all of its server configuration from a single file named GameServerSettings.ini, located in the .\TSSGame subfolder of your server install. Alongside it you’ll find a reference template called REF_GameServerSettings.ini. The reference template is your safety net: it shows every key with its default value, so if you ever break your active config, you can copy keys back from the REF_ file. You can edit the live file with any plain-text editor (Notepad, Notepad++, nano, or your host’s built-in file editor).
One caveat for Linux self-hosters: LinuxGSM has historically had a bug where the wrong settings file was referenced, so if your changes don’t seem to apply on a LinuxGSM install, confirm you’re editing the file the server actually loads from the TSSGame directory rather than a stale copy elsewhere.
The start command and port forwarding
On Windows, the server is launched with the executable and a few flags. The default start command is:
HumanitZServer.exe -log -port=7777 queryport=27015The -log flag opens a console window so you can watch the server output, -port=7777 sets the game port, and queryport=27015 sets the Steam query port used by the server browser. For players to find and connect to your server, you must forward both of these as UDP in your router or firewall:
- UDP 7777 — game traffic
- UDP 27015 — Steam query / server browser
If you also enable RCON (covered below), you’ll forward that port too. On a managed host these ports are handled for you, which is one of the reasons many admins skip self-hosting.
Host Settings: the core identity of your server
Host Settings define who can join, how the server presents itself, and how you administer it. These are the first keys most admins touch. Here are the verified Host Settings keys from GameServerSettings.ini:
| Key | Purpose |
|---|---|
ServerName | The name shown in the in-game server browser |
Password | Join password (leave blank for a public server) |
SaveName | Save file identifier / server bucket — names the world your server loads |
SearchID | Custom search-pool identifier for grouping or finding your server |
AdminPass | Password used with the /AdminAccess command to gain admin rights |
MaxPlayers | Player cap — default 16 per the official wiki |
ReserveSlots | Reserved slots (requires an F_ReservedSlots.txt file) |
RCONEnabled | Toggles RCON remote administration on/off |
RConPort | RCON port (default 8888) |
RCONPass | RCON connection password |
NoDeathFeedback | Suppresses death messages in chat |
NoJoinFeedback | Suppresses join/leave messages in chat |
LimitedSpawns | Restricts player spawns to the coast |
UseGlobalBanList | Honors the official global ban list |
A common point of confusion is the maximum player count. The official wiki lists a default of 16, while some early host summaries cited “up to 24.” Treat 16 as the authoritative default; the actual practical ceiling isn’t firmly confirmed, so if you want to push higher, raise the value and verify the limit holds in-game before advertising more slots.
Setting up an admin password and RCON
Two of those keys deserve special attention because they control how you run the server day to day. Set AdminPass to a strong password; in-game you then type /AdminAccess in chat to unlock admin commands. If you want remote administration without being in-game, enable RCON by setting RCONEnabled to true, choosing a port (default 8888), and setting RCONPass. RCON exposes a separate, powerful command set for restarts, bans, spawning, and live difficulty tuning. For the full walkthrough of granting admin rights and every command, see our dedicated HumanitZ admin commands guide.
World Settings: shaping the survival experience
The second and much larger block in GameServerSettings.ini is World Settings. These keys control gameplay tuning: difficulty, loot, time, seasons, death penalties, building rules, and dynamic events. Rather than list all of them flat, it helps to group them by category.
Difficulty and threats
- Zombies (Zeeks):
ZombieDiffHealth,ZombieDiffSpeed, andZombieDiffDamageeach use a 0–5 scale.ZombieAmountMultisets population density,ZombieRespawnTimersets how quickly they return, andZombieDogMultitunes zombie dogs. - Bandits (humans):
HumanHealth,HumanSpeed, andHumanDamage(0–5), plusHumanAmountMultiandHumanRespawnTimer. Note that one host (Pingperfect) documents a singleHumanDifficultykey instead — naming differs between sources, so check which keys actually appear in your REF_ template. - Animals:
AnimalMultiandAnimalRespawnTimercontrol wildlife density and recovery.
Loot scarcity
Loot is governed by LootRespawn (on/off), LootRespawnTimer, and PickupRespawnTimer. The official wiki then splits rarity into per-category keys, each on a 0–4 scale (scarce to abundant): RarityFood, RarityDrink, RarityMelee, RarityRanged, RarityAmmo, RarityArmor, RarityResources, and RarityOther. Some hosts expose a single combined LootRarity key instead, but the per-category split is the more granular, authoritative version — it lets you make ammo scarce while keeping food plentiful, for example.
Survival pressure, time, and seasons
VitalDraincontrols how fast hunger and thirst deplete. The wiki frames this as a 0–2 scale while Pingperfect treats it as on/off — verify the behavior in-game before relying on a specific value.FoodDecayandGenFueltune food spoilage and generator fuel consumption.DayDurandNightDurset the length of day and night in minutes;DaysPerSeasonsets season length.StartingSeasonpicks the opening season — but the value mapping is disputed between sources (the wiki and Pingperfect list different orderings), so set it, load in, and confirm which season you actually get rather than trusting a number.
Death stakes, building, and events
- Death:
PermaDeath,OnDeath,RespawnTimer, andWeaponBreak. TheOnDeathkey controls what you drop on death — the wiki lists a 0–3 range (backpack/weapons up through everything), though the exact meaning of the highest value is unconfirmed. - Building:
BuildingHealth,Decay,BuildingDecay,Territory,FreeBuild,NoBuildZone,AllowDismantle, andAllowHouseDismantle. - Events:
AIEvent(0–4) sets the frequency of dynamic AI events.AirDropandAirDropIntervalcontrol airdrops, which are also tied into the Radio Tower progression system covered in our Radio Tower location and repair guide.
Other notable World Settings include XpMultiplier, SaveIntervalSec, PVP, LogoutTimer, MaxOwnedCars, MultiplayerSleep, DogEnabled/RecruitDog/DogNum, CompanionHealth/CompanionDmg, Voip for proximity voice chat, and a set of Weather_* weight keys. For a focused walkthrough of balancing all of these into a coherent difficulty curve, read our guide to optimizing HumanitZ server difficulty.
Editing and applying changes: the restart loop
HumanitZ loads GameServerSettings.ini at startup, so the workflow for any configuration change is consistent:
- Stop the server so it isn’t actively writing or locking the file.
- Open
GameServerSettings.iniin the.\TSSGamefolder with a text editor. - Edit the key you want, keeping the exact spelling and the file’s existing format. If you’re unsure of a default, check
REF_GameServerSettings.ini. - Save the file.
- Restart the server. The new values are read on launch.
There’s an important exception: many threat-density values can be changed live without editing the INI or restarting. Through RCON, admins can use commands like overridezeekmulti, overrideanimalmulti, overridebanditmulti, and the matching override*respawntime commands to retune density mid-session. This is ideal for reacting to a session that’s too easy or too brutal without kicking everyone offline. For panel-based hosting, our HumanitZ server documentation shows exactly where to find and edit these settings in the control panel.
A sane starter configuration
If you just want a balanced co-op PvE server to begin with, a reasonable starting point is a named server with a join password, a 16-player cap, RCON enabled for remote management, and PvP off. Conceptually:
ServerName=My HumanitZ Survival
Password=changeme
MaxPlayers=16
AdminPass=strong-admin-pass
RCONEnabled=true
RConPort=8888
RCONPass=strong-rcon-pass
PVP=0
SaveName=MainWorldTreat the snippet above as a template of which keys to set rather than copy-paste-ready values, since your REF_ file is the source of truth for exact formatting and defaults on your build. New to the game itself? Our ultimate HumanitZ beginner guide covers the survival fundamentals your players will need once they’re on the server.
Frequently asked questions
What is the SteamCMD App ID for the HumanitZ dedicated server?
The dedicated server uses App ID 2728330, which is different from the game’s own App ID of 1766060. Install it anonymously with +app_update 2728330 validate.
Where is the HumanitZ config file located?
It’s named GameServerSettings.ini and sits in the .\TSSGame subfolder of your server install. A reference copy, REF_GameServerSettings.ini, lives in the same place and shows every key with its default value.
Which ports does a HumanitZ server need?
Forward UDP 7777 (game) and UDP 27015 (Steam query) so players can find and join. If you enable RCON, also forward its port (default 8888).
What is the default max player count?
The official wiki lists a default of 16 via the MaxPlayers key. Some hosts have mentioned higher figures like 24, but the practical ceiling isn’t firmly confirmed, so test any increase in-game before relying on it.
Do I need to restart the server after changing settings?
Yes for INI edits — the file is read at startup, so stop the server, edit, save, and restart. However, many density values (zombies, animals, bandits) can be adjusted live through RCON override* commands without a restart.
Is HumanitZ still in Early Access?
No. HumanitZ left Early Access and released its full 1.0 build on February 6, 2026. It’s developed by Yodubzz Studios. Configure your server against the 1.0 branch, and check the Steam news feed for the current patch.
Ready to play?
Run your own HumanitZ server with XGamingServer
Spin up an always-on HumanitZ server your friends can join in minutes — no port-forwarding, no tech headaches.
