Project Zomboid Server Survival: Admin Tips for B41 & B42

So you've decided to run a Project Zomboid server for you and your friends (or a whole community of survivors). Good choice! Being a server admin in PZ is like being the leader of a ragtag apocalypse camp – it's rewarding, but you'll face some challenges that require creativity and grit. This article is a toolbox of tips for Project Zomboid server administrators on Build 41 and the new Build 42.

We'll start with a Quick-Start setup guide for the impatient, then dive into performance tweaks, mod management, security against griefers, and advanced tricks to keep your server running smoothly. By the end, you'll know how to handle everything from installing mods to stopping a horde of trolls (sometimes literally!). For detailed memory optimization, see our comprehensive server memory guide.

Whether you're hosting a cozy co-op server for a few friends or administering a bustling public server with dozens of players, these tips will help you avoid common pitfalls. We'll cover in-game admin tools, configuration files, hardware advice, and what changes Build 42 brings to the table. Let's turn you from a survivor into the ultimate server Overseer (with admin powers comes great responsibility, after all).

If you're new to hosting, here's a Quick-Start checklist to get your Project Zomboid server up and running fast. This assumes you want a basic server for Build 41 or 42 with default settings:

1. Decide How to Host: For 2-4 friends, using the in-game Host option can be simplest. Launch PZ, click Host, create a server name and admin password, and start the server. The game will auto-handle port forwarding via Steam in many cases (UPnP) and create config files. (Downside: the server only runs when you're in-game and performance may suffer if your PC isn't beefy.) For a more permanent or larger server, use the dedicated server application (either on your own hardware or through a hosting provider). For detailed multiplayer setup guidance, check our Build 41 vs 42 multiplayer comparison.
2. Install Server Files: If going dedicated, install Project Zomboid Dedicated Server via SteamCMD or Steam. On Steam, it's listed under Tools. On SteamCMD, run:

   steamcmd +login anonymous +force_install_dir /pzserver +app_update 380870 validate +quit

   This installs the latest server (Build 41 by default). For Build 42 unstable, use the -beta unstable branch.

3. Configure Ports: Current server options use two UDP ports: DefaultPort=16261 (player data / game) and UDPPort=16262 (Steam section of server options). Forward both on your router when hosting at home, and allow the dedicated server binary through the OS firewall. Older community guides that only list 8766/8767 or omit 16262 are outdated for current builds. If friends cannot join, check ports, firewall, and CGNAT first. For connection troubleshooting, see our server initialization troubleshooting guide.
4. Initial Server Settings: After first launch, config files live under the Zomboid user folder (Windows example: C:\Users\<YourName>\Zomboid\Server\). Open servertest.ini (or your server name). At minimum set:
   • Public=true/false (false if it is just for friends)
   • Password= if you want a join password
   • DefaultPort=16261 and UDPPort=16262 (change both only if you run multiple servers and update port forwarding to match)
   • Map= (commonly Muldraugh, KY for vanilla)
   • Admin access: AdminPassword is not a normal ServerOption in the current options table. Set a strong admin password in the in-game Host flow (or the host/co-op admin password path), then promote your play account with /setaccesslevel from the console if needed.
5. Launch and Test: Start the server. If using the dedicated server, run the ProjectZomboidServer.bat (Windows) or the start script (Linux). Now launch Project Zomboid (game client), go to Join, and input 127.0.0.1 if hosting on the same PC or your server's IP. Use username "admin" and the admin password you set.
6. Invite Friends: Give friends your external IP (Google "my IP" to get it) or use the Invite via Steam feature. Make sure they have the exact same game version (Build 41 or opted into the 42 beta).
7. Set Yourself as Admin: By default, the first account "admin" with the password is the superuser. If you want to make your player account admin, from the server console type:

   setaccesslevel "YourUsername" admin

   In chat or console use the official form with quotes: /setaccesslevel "YourUsername" "admin". Access levels include Admin, Moderator, Overseer, GM, and Observer. /grantadmin "YourUsername" also exists for granting admin.

8. Save Settings and Go: If everything works with default settings, you're good to play. Survivors can join, and zombies await. But you'll likely want to adjust loot, zombies, etc., which we'll cover next.

One of the first decisions is how to host: use the built-in Host feature or set up a standalone dedicated server. Both have pros and cons:

Once the server is up, you'll probably want to adjust gameplay settings: zombie count, loot rarity, PvP on/off, etc. Project Zomboid has two types of settings: core server settings (in servertest.ini) and sandbox settings (in servertest_SandboxVars.lua).

SandboxVars = {
    Version = 6,
    Zombies = 4,
    FoodLootNew = 0.8,
    WeaponLootNew = 0.6,
    StarterKit = false,
    FireSpread = false,
    ZombieLore = {
        Transmission = 4, -- None: blocks new Knox infection from attacks
        Mortality = 5,    -- 2–3 Days if infection is otherwise possible
    },
    ZombieConfig = {
        PopulationMultiplier = 0.65,
        PopulationPeakMultiplier = 1.5,
        PopulationPeakDay = 28,
        RespawnHours = 0.0,
    },
}

Mods are a huge draw for PZ – everything from new guns, maps, to admin tools and gameplay overhauls. But mods on servers can be tricky if not handled correctly. Let's break it down step-by-step, since misconfigured mods are a top cause of server problems.

Installing a New Mod

Suppose you want to add the popular Brita's Weapons mod to your server. Here's what you do:

1. Subscribe and Check Mod ID: Subscribe to the mod in Steam Workshop. In the Workshop page URL you'll see something like ?id=2256623446 – that number is the Workshop ID. The page will also list the "Mod ID".
2. Update Server .ini: Open servertest.ini. Find WorkshopItems= line. Add the workshop ID. For multiple mods, they go separated by a semicolon. Then find Mods= line. Add the mod's name exactly as specified. Example:

   WorkshopItems=2256623446;2256623668
   Mods=Brita;BritaGunFighter

3. Ensure Clients Have It: When players join a modded server, if they are missing mods, the game will show a popup with a list of required mods and offer to enable/download them. It's good practice to announce mods beforehand so they can preload them.
4. Restart the Server: Whenever you change mods, always restart the server fresh. The server on startup will log each Workshop ID and attempt to download/update them. Double-check the console log for any errors.
5. Matching Versions: If a mod updates on Workshop, clients will auto-update but the server only checks for mod updates when it starts. This can lead to "Workshop item version different than server" kicks. The fix is to restart the server so it grabs the latest version.
6. Anti-Cheat Adjustments: Some mods might require turning off specific anti-cheat protections. If players get inexplicable kicks after using a mod item, check the anti-cheat settings.
7. Mod Load Order: PZ loads mods in the order they're listed in the Mods= line. If two mods modify the same thing, the last one in the list wins.
8. Maps Mods: Want to add custom maps? These require a bit more editing. In addition to WorkshopItems/Mods entries, you must edit Map= line to include the map folder names.

Recommended Admin/Utility Mods

There's no quicker way to kill a fun session than server lag or crashes. Project Zomboid can be surprisingly demanding on servers, so let's talk performance optimization and maintenance.

Hardware Considerations

Performance Tips

• Periodic Cleanup: Over time, the world can accumulate a lot of dropped loot. There are sandbox settings to make corpses decay and even disappear after a time – consider enabling corpse removal.
• Backups: Config alone is not enough. Before mods, branch changes, or major patches, stop the server and copy at least:
  • Zomboid/Server/ (INI, sandbox vars, ban/whitelist-related server files)
  • Zomboid/Saves/Multiplayer/<servername>/ (the live multiplayer world—this is the main world data)
  • Related DB / auth files under the Zomboid user directory when present
  Built-in rotating backups (BackupsCount, BackupsOnStart, BackupsPeriod) help day-to-day recovery; keep a full off-box copy before risky changes.
• Monitoring Performance: F11 opens the Lua debugger, not a server FPS panel. For server statistics use /stats help (and related /stats modes such as file/console). Also watch host CPU/RAM, console logs, and player reports of rubber-banding.
• Memory Management: If the server throws an "OutOfMemory" error, the Java heap might need increasing. Look for -Xmx parameter in the start script and increase it (e.g., -Xmx4g for 4GB heap).

Running a server isn't just ticking checkboxes and updating mods – you're also the sheriff of this survivor town. Let's talk about admin powers and how to use them effectively (and fairly).

Banning and Whitelisting

To ban a player, use the official command /banuser "username" (or the admin panel / scoreboard). Optional flags: -ip and -r "reason". Example: /banuser "rj" -ip -r "spawn kill". Related commands include /unbanuser, /kickuser, /banid, and /banip. There is no short /ban alias in the current command set.

For a whitelist model (only accounts you create can join), set Open=false in the server INI. When false, administrators must create username/password combos (for example /adduser "username" "password"; password is optional in the help text). You can also protect accounts with /addusertowhitelist "username".

Fun with Admin Commands

Always balance fun with fairness. Don't abuse powers to give your faction an undue advantage – players will notice. Many admins use a separate account for "playing" as a normal player and only use their admin account when needed.

Build 42 (B42) brings a lot of new content plus server-side changes that admins should plan for before switching.

Staying Updated with B42

B42 unstable will likely receive frequent patches. If you're running it, you must update the server whenever the game updates (or players won't be able to join due to version mismatch).

Subscribe to Project Zomboid dev news, join their Discord or check the official forum News section regularly, so you know when updates hit. And obviously, backup before each update because unstable updates can introduce bugs that corrupt saves.

Being a server admin is a bit of work, but it's also very rewarding to see a thriving community enjoying the world you host. You'll learn a lot as you go – don't be afraid to make mistakes, just communicate and learn from them. Remember that at the end of the day, everyone's here to have fun surviving the zombie apocalypse.

Adminning a PZ server is like running a neighborhood watch in zombie town. You coordinate the block party (server events), make sure no one's wrecking the place (moderation), and occasionally chase a stray dog or zombie off someone's lawn (technical issues or griefers). It's a responsibility, but also a lot of fun.

Further Resources