Server Admin Survival: Zombie-Proof Your PZ Server

Server Admin Survival: Zombie-Proof Your PZ Server

Table of Contents

๐Ÿ“‹ Introduction ๐Ÿš€ Quick-Start Guide ๐Ÿ  Choosing Hosting Approach โš™๏ธ Server Settings ๐Ÿงฉ Managing Mods โšก Performance Optimization ๐Ÿ‘‘ Admin Powers ๐Ÿ†• Build 42 Changes ๐Ÿ“ Conclusion & Resources
๐Ÿ“‹

Surviving the Setup: Introduction

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 guide is your comprehensive toolbox for Project Zomboid server administration across both Build 41 and the new Build 42. We'll cover everything from basic setup to advanced techniques, performance tweaks, mod management, security against griefers, and admin tricks to keep your server running smoothly.

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. Let's turn you from a survivor into the ultimate server Overseer.

โ„น๏ธ Note: If you're already eager to get the server up, skip to the Quick-Start section.

๐Ÿš€

Quick-Start Guide to Hosting (B41/B42)

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, the in-game Host option can be simplest. For a more permanent or larger server, use the dedicated server application.
  2. Install Server Files: If going dedicated, install Project Zomboid Dedicated Server via SteamCMD or Steam (under Tools).
    steamcmd +login anonymous +force_install_dir /pzserver +app_update 380870 validate +quit

    For Build 42 unstable, use: app_update 380870 -beta unstable

  3. Configure Ports: Ensure ports 16261 UDP (game port) and 8766/8767 UDP (Steam ports) are forwarded in your router if hosting at home. Also allow ProjectZomboidServer.exe through your firewall.
  4. Initial Server Settings: Locate the server config files. On Windows, after first launch they are in C:\Users\<YourName>\Zomboid\Server\. Open servertest.ini in a text editor and configure basic settings:
    Public=true/false
    Password=yourpassword
    DefaultPort=16261
    DefaultGameMode=Sandbox
    Map=Muldraugh, KY
    AdminPassword=yoursecureadminpassword
  5. Launch and Test: Start the server. If using the dedicated server, run the ProjectZomboidServer.bat (Windows) or the start script (Linux). Launch the game, go to Join, and input your server IP.
  6. Invite Friends: Give friends your external IP or use the Invite via Steam feature. Make sure they have the exact same game version and mods.
  7. Set Yourself as Admin: By default, the "admin" account with the password set is the superuser. To promote your regular player account:
    setaccesslevel "YourUsername" admin

    In-game as admin, use: /setaccesslevel YourName admin

โœ… Success! If everything works with default settings, you're good to play. Survivors can join, and zombies await. The sections below will help you turn this barebones setup into a finely tuned apocalypse experience.

๐Ÿ 

Choosing Your Hosting Approach

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:

๐ŸŽฎ In-Game Host (Co-op mode)

Pros:

  • Easiest setup - click Host from main menu
  • Friends join through Steam's friend list (no IPs needed)
  • Great for quick sessions or casual play

Cons:

  • Your PC's resources are shared between playing and hosting
  • Server shuts down when you exit the game
  • Limited control over advanced settings
  • Not ideal for large groups or 24/7 play

Best for: 2-4 friends who always play together at the same time

๐Ÿ–ฅ๏ธ Dedicated Server

Pros:

  • Runs continuously even when you're offline
  • Players can join on their own schedule
  • More stable for larger groups (5+ players)
  • Won't impact your gameplay performance
  • Full control over all server settings

Cons:

  • More complex setup and maintenance
  • Requires additional hardware or hosting costs
  • More networking knowledge needed

Best for: Larger communities, players in different timezones, or long-term persistent worlds

Hardware Requirements

For a dedicated server, you'll need:

  • CPU: Good single-core performance (PZ server is single-thread heavy)
  • RAM: At least 4GB dedicated, plus ~0.1-0.2GB per player and per big mod
  • Network: Stable connection with ports forwarded (16261, 8766, 8767 UDP)
  • Storage: 10GB minimum, more for many mods or extensive world exploration

Hosting Providers

Not keen on running a server from your home network? Consider using a game server provider like G-Portal, Nitrado, or GTXGaming. They offer PZ servers for a monthly fee and handle the hardware and networking complexities. Benefits include:

  • Web interface for easy management
  • One-click mod installation
  • DDoS protection and guaranteed uptime
  • No need to worry about port forwarding or hardware requirements

The trade-off is cost and sometimes slightly less flexibility than hosting yourself.

๐Ÿ’ก Tip: Many server owners start with an in-game host to test the waters, then migrate to a dedicated server when their community grows or they need 24/7 uptime.

โš™๏ธ

Tweaking Server Settings

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) - server configuration, networking, etc.
  • Sandbox settings (in servertest_SandboxVars.lua) - gameplay tweaks like zombies, loot, etc.

Using the Edit Server Settings UI

If you host via the game menu, there's a handy UI for server options:

  1. On the main menu, click Host > Manage Settings
  2. Choose your server preset (e.g. "servertest")
  3. Click Edit Settings
  4. This brings up a multi-tab interface for all settings
  5. Save when done - it writes to the files for you

For dedicated servers, you edit the files manually. Always stop your server before editing .ini or .lua files, then restart to apply changes.

Key Server Options (servertest.ini)

Setting Description
Public If true, your server appears in public listing. Set false for private friend server.
Password Password required to join. Leave empty for open public access.
MaxPlayers Maximum number of players allowed (default 16). More players means more CPU/bandwidth usage.
PvP Enable/disable player vs. player combat. Set false for cooperative play.
PauseEmpty If true, time stops when no players are online. Recommended for friend servers to avoid "lost days".
SafetySystem Gives players a safety toggle if PvP is enabled. They can opt-in/out of PvP combat.
WorkshopItems Steam Workshop IDs for mods (semicolon separated). Server uses these to download mods.
Mods Mod folder names to load (semicolon separated). Must correspond to Workshop IDs.
AntiCheatProtection Various anti-cheat toggles. Some mods require disabling specific checks (e.g., Brita's Weapon Pack needs AntiCheatProtection12=false).
// Example servertest.ini snippet Public=false Password=friendserver MaxPlayers=8 PvP=false PauseEmpty=true ServerWelcomeMessage=Welcome to our private server! WorkshopItems=2256623446;2392709985 Mods=Brita;BritaGunFighter

โš ๏ธ Important: Always restart the server after changing settings files. This ensures all changes are properly applied.

๐Ÿงฉ

Managing Mods on Your Server

Mods are a huge draw for PZ โ€“ everything from new guns and maps to admin tools and gameplay overhauls. But mods on servers require careful configuration to avoid connection issues and crashes.

How Mods Work in PZ Multiplayer

  • The server dictates which mods are required
  • Clients must have the identical mod files enabled locally
  • The server downloads mods via Steam Workshop IDs
  • Clients must also download the same mods (via Steam or auto-prompt)
  • Both Workshop ID and Mod ID must match between server and clients

Installing a New Mod: Step-by-Step

  1. Subscribe and Check Mod ID:

    On your PC, 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.

    Find the Mod ID from the mod's description, its folder name, or the mod.info file. Example paths:

    C:\Users\\Zomboid\mods\\mod.info
  2. Update Server .ini:

    Open servertest.ini and find/update these lines:

    WorkshopItems=2256623446;2256623668 Mods=Brita;BritaGunFighter

    For multiple mods, separate with semicolons. The Mods names must match exactly (case-sensitive).

  3. Ensure Clients Have Matching Mods:

    When players join, the game should prompt them to download missing mods. You can also provide the Workshop links ahead of time for players to subscribe manually.

  4. Restart the Server:

    Always restart the server after changing mods. On startup, the server will log each Workshop ID and download/update them.

Keeping Mods Updated

When mods update on Steam Workshop, clients will auto-update but the server only checks for updates when it starts. This can lead to "Workshop item version different than server" kicks if a mod updated and the server hasn't caught up.

Update PLZ Mod

Consider using the "Update PLZ" mod which:

  • Automatically checks for outdated Workshop mods
  • Saves the world and shuts down when mods need updating
  • Works with external restart scripts to reboot with updated mods

This is especially useful for public servers with many mods.

Alternatively, you can:

  • Schedule daily server restarts during low-activity hours
  • Use the /checkModsNeedUpdate command to manually check for updates
  • Monitor mod Discord channels or Steam updates for release notices

Special Cases & Common Issues

โญ Recommended Admin/Utility Mods

Cheat Menu / Admin Tools

GUI interface for admin commands - spawn items, toggle god mode, and other administrative functions.

Update PLZ

Automatically manages mod updates, saving and restarting the server when mod updates are detected.

Safehouse Shield

Fixes edge cases and bugs with the safehouse system, ensuring proper protection of player bases.

Map Extensions

Popular maps like Raven Creek, Bedford Falls, or Fort Redstone can add fresh locations for exploration.

โš ๏ธ Warning: The fewer mods, the fewer headaches. Each mod increases complexity and potential for conflicts. Start with essential mods and add gradually.

โšก

Keeping Your Server Running Smoothly

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

๐Ÿ’ป Hardware Considerations

  • CPU: Single-thread performance matters most. High clock speed over many cores.
  • RAM: 4GB baseline + ~100-200MB per player. More for large mod packs.
  • Network: Stable connection, wired preferred over WiFi. ~1Mbps per 10 active players.
  • Storage: SSD recommended for faster world saving and loading.

๐Ÿงน Periodic Cleanup

  • Enable corpse decay and removal settings in sandbox
  • Use /removezombies command for cleaning up large hordes
  • Consider mods like "Incinerator" for burning corpses
  • Ask players to clean up dropped items in bases

๐Ÿ’พ Regular Backups

  • Backup server// folder regularly
  • Create backups before adding new mods
  • Keep rotating backups (last 7 days, etc.)
  • Use automation scripts to schedule backups

๐Ÿ“Š Monitoring Performance

  • Press F11 in-game (if admin) to see performance panel
  • Use /players command to check player ping and IDs
  • Check server logs for errors or exceptions
  • Monitor RAM usage for memory leaks or excessive growth

Troubleshooting Common Performance Issues

Symptom Possible Solutions
Server-wide lag spikes
  • Reduce zombie population density
  • Check for error spam in console (mod issues)
  • Increase server RAM allocation
  • Limit number of active mods
Memory usage growing continuously
  • Schedule regular server restarts
  • Increase Java heap size (edit -Xmx parameter in start script)
  • Limit explored world size or use PauseEmpty=true
Players reporting "rubber-banding"
  • Check player ping (high ping causes desync)
  • Ensure server has sufficient upload bandwidth
  • Lower zombie count in heavily populated areas
Frequent crashes
  • Check server logs for Java exceptions
  • Remove recently added mods one by one to identify culprits
  • Ensure your Java version is compatible with PZ server
  • Consider server hardware upgrades if under-resourced

Watchdog and Auto-Restart

Set up automated restart mechanisms to recover from crashes and apply updates:

  • Windows: Use tools like NSSM (Non-Sucking Service Manager) to run the server as a service that restarts on failure
  • Linux: Create a systemd service with Restart=always or use screen/tmux with a restart script
  • Schedule daily restarts during off-hours to refresh the server and apply mod updates
  • Hosting providers often include built-in watchdog services - check your control panel

๐Ÿ’ก Tip: If you need to increase server memory, edit the start script. Look for -Xmx2g and increase the number (e.g., -Xmx4g for 4GB). Don't allocate more than 75% of your available RAM.

๐Ÿ‘‘

Admin Powers and Keeping Order

Running a server isn't just technical configuration โ€“ you're also the sheriff of this survivor town. Let's explore the admin tools and how to use them effectively.

The Admin Panel

Build 41's multiplayer introduced a robust admin panel UI. Once you're admin, you'll notice a new icon on the left of your screen โ€“ clicking it opens the panel with various tabs:

Players

View online players, their Steam ID, ping, etc. Teleport to them, bring them to you, heal, kick, ban, etc.

Safehouses

Manage claimed safehouses. Remove abandoned ones, transfer ownership, view members, etc.

Items

Spawn any item to your inventory. Search the complete item database and add what you need.

Debug

Access server settings, toggle visibility, god mode, and other advanced functions.

[Admin Console Screenshot]

The in-game admin panel showing player management and server tools

Essential Admin Commands

Even with the graphical panel, knowing these chat commands can be useful:

Command Description
/setaccesslevel "User" admin Promote a player to admin status
/teleport User1 User2 Teleport User1 to User2's location
/invisible Toggle invisibility (zombies and players can't see you)
/god Toggle god mode (invulnerability)
/kick Username "reason" Kick a player from the server
/ban Username "reason" Ban a player permanently
@all Message Broadcast a server message to all players
/createhorde 100 X Y Spawn 100 zombies at coordinates X Y
/additem ItemID Count Add items to your inventory

Preventing Grief and Server Security

Safehouse System

  • Enable safehouse claiming in server settings
  • Set SafehouseAllowLoot=false to prevent theft
  • Use SafeHouseRemovalTime to clean up inactive bases
  • Set SafehouseDaySurvivedToClaim to prevent new players claiming best spots

Anti-Griefing Measures

  • Set FireSpread=false to prevent arson
  • Use whitelisting for private communities
  • Check logs regularly for suspicious activity
  • Establish and communicate clear server rules
  • Consider running a whitelist-only server for better security

Whitelisting vs. Open Access

For tighter control, you can run a whitelisted server:

  1. Set Open=false in servertest.ini
  2. Add users manually with /adduser Username Password
  3. Only whitelisted users can join the server

This creates more administrative work but provides the highest level of security against griefing.

Server Logs for Moderation

The server creates several useful logs in the Logs/ directory:

  • chat.txt - Records all in-game chat messages
  • pvp.txt - Logs PvP hits and kills
  • admin.txt - Tracks admin commands and actions
  • user.txt - Shows logins, disconnects, and connections

Regularly check these logs to investigate reports of griefing or abusive behavior.

Fun with Admin Commands

Don't forget you can use admin powers to create unique events and experiences:

  • Use /createhorde to stage challenging zombie attacks
  • Trigger helicopter events with /heli to spice up a quiet evening
  • Create treasure hunts by hiding special items around the map
  • Build community spaces like trading posts or safe zones
  • Host in-game events like survival contests or base-building competitions

โš ๏ธ Important: With great admin power comes great responsibility. Use your powers fairly and don't give yourself gameplay advantages. Many admins use a separate account for normal play to avoid temptation.

๐Ÿ†•

Build 42: New Challenges and Opportunities

Build 42 (B42) brings exciting new content and under-the-hood changes that server admins should be aware of.

โš ๏ธ Build 42 Migration Warning

You cannot upgrade a Build 41 save to Build 42. The differences in data structures are too significant. Plan for a fresh start when moving to B42.

Key B42 Features & Admin Considerations

Animals & Husbandry

  • Players can find, tame, and breed animals
  • Animals require server resources similar to zombies
  • Watch for performance impact if many players hoard animals
  • Look for new animal-related sandbox settings

Combat Changes

  • Aiming and combat mechanics significantly changed
  • Players may need time to adapt to new systems
  • Consider hosting practice events for players
  • PvP servers may need balance adjustments

Enhanced Server Security

  • More calculations moved server-side
  • Reduced ability for clients to cheat
  • May increase server CPU requirements
  • Improved verification of player actions

Map Expansions

  • New towns and locations added
  • Wilderness generation outside map bounds
  • Consider storage implications for infinite wilderness
  • Players will initially rush to explore new areas

Official Mod Support

B42 includes improved mod management:

  • Official in-game mod manager UI
  • Potentially easier mod installation and updates
  • Better conflict detection

However, B41 mods will need updating for B42 compatibility. Check workshop pages for B42-specific versions.

B42 Migration Plan

  1. Communicate with players - Give advance notice about the upcoming wipe and fresh start
  2. Run a test server - Consider running a B42 test server alongside your main B41 server initially
  3. Start vanilla - Begin with minimal or no mods until the B42 mod ecosystem stabilizes
  4. Monitor performance - B42 may have different hardware demands; watch server load closely
  5. Plan events - Use new features like animals or crafting for server events to engage players

๐Ÿ’ก Tip: Stay connected with other server admins in the PZ Discord or forums to share experiences and solutions for B42-specific challenges.

๐Ÿ“

Conclusion & Resources

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.

A quick story from my own admin adventures: Early on, I hosted a server for some college friends. One night, a stranger found our server (I'd left it Public by accident). This person ended up being super friendly and effectively became another regular. We were wary at first, but he followed our rules and actually helped build our base. This taught me not every "random" is a griefer, and sometimes making a server public can lead to great new friends โ€“ you just need good moderation and clear rules.

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). It's a responsibility, but also a lot of fun.

Action Steps Recap (TL;DR)

  1. Set Up Right: Choose the appropriate hosting method for your needs and properly configure ports and security.
  2. Tune Performance: Adjust zombie count and settings based on your hardware capabilities.
  3. Manage Mods Carefully: Match Workshop IDs and Mod IDs, and have a plan for updates.
  4. Use Admin Tools: Familiarize yourself with commands and the admin panel for effective moderation.
  5. Secure the Server: Enable safehouse protection and implement anti-griefing measures.
  6. Backup Regularly: Create frequent backups to protect against both griefing and technical issues.
  7. Plan for B42: Prepare your community for the transition when you're ready.
  8. Communicate: Keep players informed about changes, issues, and events.
  9. Have Fun: Organize events and create memorable experiences for your community.

Further Resources

  • Project Zomboid Official Wiki - Server Administration: Comprehensive documentation on server settings and commands
  • The Indie Stone Forums - Help Section: Community support for specific issues
  • Project Zomboid Discord: Official channels for server hosting discussion and quick help
  • Steam Community Guides: Many player-created tutorials for specific hosting scenarios

By following this guide and utilizing these resources, you're well on your way to running a top-notch Project Zomboid server. Remember, it's a learning process, but also an integral part of what makes multiplayer Zomboid so engaging โ€“ the unique servers and stories that emerge.

Happy hosting, and remember: When life gives you zombies, make zombie stew! ๐ŸงŸโ€โ™‚๏ธ๐Ÿ”ฅ