Your own Project Zomboid server is worth it if you want to manage the sandbox rules, mod list, and admin rights in a controlled way. A clean start is important: first test vanilla, then change settings, then add mods. This lets you spot configuration errors faster and run your multiplayer session in a traceable way.
Requirements and Server Choice
To get started, go to game-serverhosting and choose at least 4 GB RAM for Project Zomboid, as intended in the initial setup. This figure is not a guarantee for every mod collection or player count, but a sensible minimum for a manageable session. Large maps, many Workshop mods, and permanently active players increase the requirements.
Project Zomboid is especially configuration-heavy. So before the first game night, plan three things: a clear sandbox setup, a tested mod list, and at least one admin account. If your group is also comparing other survival or co-op servers, the Valheim Co-op Guide 2026 and the 7 Days to Die Multiplayer Guide 2026 will help you classify similar server workflows.
Order the Server and Check the Base Installation
Deliberately start without mods. After the automatic setup, the server should be reachable before you change sandbox or Workshop values. Connect once with a client, create a character, and check whether the world loads. This short baseline test separates hosting, connection, and game configuration problems from each other.
Specific process:
- Open game-serverhosting.
- Choose at least 4 GB RAM.
- Wait until the server has been set up automatically.
- Start the server without mods.
- Connect once for testing and then stop the server for configuration.
Set Sandbox Settings Cleanly
Project Zomboid offers very detailed sandbox options. The values belong in the sandbox configuration, often as sandboxvars.lua or a server-specific sandbox file. Always change only a few values at once and document the decision for your group so later adjustments remain traceable.
# sandboxvars.lua
SandboxVars.ZombieLore.Speed = 2 # 1=Sprinter, 2=Fast, 3=Shambler
SandboxVars.ZombieLore.Strength = 2 # 1=Superhuman, 2=Normal, 3=Weak
SandboxVars.ZombieLore.Toughness = 2 # 1=Tough, 2=Normal, 3=Fragile
SandboxVars.Zombies = 3 # 1=Insane, 2=Very High, 3=Normal, 4=Low
SandboxVars.XPMultiplier = 2.0
SandboxVars.LootRespawn = 2 # Days until loot respawns (0=never)
SandboxVars.NatureAbundance = 3 # Plant spawn
Zombie Presets
| Preset | Speed | Strength | Amount | For whom |
|---|---|---|---|---|
| Apocalypse | Sprinter | Strong | High | Hardcore |
| Survival | Fast | Normal | Normal | Standard |
| Builder | Shambler | Weak | Low | Beginners |
| Custom | Selectable | Selectable | Selectable | Individual |
Use presets as a basis for discussion, not as a rigid rule. A new group often benefits from slower zombies and less pressure, while experienced players prefer tougher settings. What matters is that everyone knows whether the server is meant to support roleplay, long-term base building, or tough survival runs.
Install Mods
For Workshop mods, you usually need two pieces of information: the Steam Workshop ID and the internal mod ID. The official Steam discussion with a developer response describes the basic principle of entering the desired Workshop items in the WorkshopItems= line of the server INI: Project Zomboid on Steam. The mod ID usually comes from the Workshop description or from the respective mod file.
- Enter Workshop IDs in
server.ini:
WorkshopItems=2392987599;2778576730;2169435993
Mods=Arsenal(26)GunFighter;tsarslib;Brita
- Restart the server – mods are downloaded automatically
- Players download mods automatically when connecting
Pay attention to semicolons between entries. Workshop ID and mod ID are not the same thing; if one of the two lists is incomplete, the server may download a mod but not activate it correctly. For mod dependencies, the required library should come before the dependent mod. Typical examples are:
- Arsenal(26) GunFighter – weapon overhaul
- Brita's Weapon Pack – hundreds of weapons
- Hydrocraft – crafting expansion
- Expanded Helicopter Events – more events
Test new mods on a fresh or backed-up save first. World, map, and item mods can affect existing saves, so back up the world files before making major changes.
Admin Rights and Commands
Admins should only be assigned to trusted people. Create at least one admin login, test the rights, and avoid unnecessarily many accounts with full access.
/adduser <name> <pw> # Add player
/setadmin <name> # Give admin rights
/teleport <name> # Teleport to player
/noclip # Fly through walls
/godmod <name> # Invulnerable
Use commands like /godmod or /noclip mainly for support cases, such as when a player is stuck or a configuration error needs to be checked. For normal gameplay, admin interventions should remain transparent.
Check the Result
After every change, restart the server and check three layers: connection setup, game world, and logs. A player should be able to join without an error message. The sandbox values should be recognizable in gameplay behavior, such as zombie speed or loot respawn. Mods should be synchronized automatically during the connection attempt.
If you also run other complex mod or survival setups, the Satisfactory Dedicated Server Guide is a good comparison for structured multiplayer configurations with long-term world operation.
Troubleshooting
If players cannot connect, first check whether the client and server are using the same game version and whether all Workshop mods are available. Temporarily remove the most recently added mods and start again. If zombies, loot, or XP do not behave as expected, you probably edited the wrong sandbox file or the server was not restarted cleanly after the change.
For mod problems, pay particular attention to WorkshopItems= and Mods=. The first line downloads Workshop content, the second activates the internal mod IDs. Typos, missing semicolons, or swapped IDs are common causes. For map mods, you also need the correct map entries in the server configuration; only change such setups with a backup.
Testing, Limits, and a Safe Way Back
The guide “Rent a Project Zomboid Server – Multiplayer Guide” applies to the server type described in the article and the version state visible at the time of testing. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. So do not transfer any values to another game, loader, or server version without checking them first.
Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step at a time and test it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Abort and Way Back |
|---|---|---|
| Server start | The server reaches the ready-to-run state without any new error message. | If startup errors occur, revert the change and restore the latest backup. |
| Connection test | A test account can connect via the address shown in the panel. | For version or connection errors, compare the version, port, and permissions again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore backed-up files. |
A successful individual test is not a performance or availability guarantee. World size, mods, plugins, player count, network route, and simultaneous load can change the result. Document the version, change, and test result so you can trace later deviations.
FAQ
How much RAM do I need for a Project Zomboid server?
The initial guide specifies at least 4 GB RAM. For small groups, that is a sensible starting point. Many mods, large maps, or more simultaneous players may require more resources.
Do I have to install mods before the first start?
No. It is better to start without mods first and check whether the server is reachable. After that, add Workshop mods step by step so you can identify errors faster.
What is the difference between WorkshopItems and Mods?
WorkshopItems= contains the Steam Workshop IDs for downloading. Mods= contains the internal mod IDs that the server actually loads. Both entries must match the respective mod.
Why are my sandbox settings not applying?
Often the wrong file was edited, the server was not restarted, or a value was overwritten. Check the server-specific sandbox file and change only a few values per test run.
Should I make a backup before mod changes?
Yes. Map, world, and item mods in particular can affect saves. Back up the world before larger changes so you can go back if problems occur.