All Server Settings
Server settings decide how your world behaves when nobody is online, how mods load, how passwords work, and how forgiving the server is when something goes wrong. Treat them like operations policy, not just a wall of toggles.
The Major Settings Areas
| Security and access | Passwords, whitelist choices, anti-cheat posture, and who gets elevated permissions. |
|---|---|
| World behavior | Pause rules, sleep handling, corpse cleanup, and other settings that change the server's rhythm. |
| Networking | Connection limits, voice options, and how tolerant the server is of bad client conditions. |
| Mods and map stack | Workshop IDs, map order, and any setting that determines how clients sync with the server. |
Order To Tune Them
- Lock down access and backups first so mistakes are survivable.
- Configure map and mods before inviting players, because later changes are much more expensive.
- Tune world-behavior settings after a short live test, not before.
- Review networking and restart policy once the server sees real traffic.
What Causes Most Admin Pain
- Changing map order after the world already has active players.
- Giving moderators broad powers without an agreed process.
- Letting the config drift over time until nobody remembers why a value changed.
Verified 2026 Detail
The official stable-versus-unstable split matters here because server settings often outlive the branch they were created on. A config that was sensible on one branch can become confusing on another, especially once map order, workshop content, and multiplayer defaults have drifted for months.
Current Official Note
The official Project Zomboid site still presents stable and unstable as separate release tracks. When you review server settings, keep that split in mind because defaults, new options, and multiplayer assumptions can differ between the established stable branch and current Build 42 testing.
Need a stable place to test changes before you touch a live world? Launch your Project Zomboid server with Supercraft.