PZ Server Nightmares? Keep Calm and Admin On
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 toolbox for success.
Quick-Start Guide to Hosting
If you're new to hosting, here's a Quick-Start checklist to get your Project Zomboid server up and running fast:
- Decide How to Host: For 2-4 friends, using the in-game Host option can be simplest. For a more permanent or larger server, use the dedicated server application. Either way, you'll need proper port forwarding setup for external players to connect.
-
Install Server Files: If going dedicated, install Project Zomboid Dedicated Server via SteamCMD or Steam. On Steam, it's listed under Tools.
steamcmd +login anonymous +force_install_dir /pzserver +app_update 380870 validate +quit
- Configure Ports: Ensure ports 16261 UDP (game port) and 8766/8767 UDP (Steam ports) are forwarded in your router if hosting at home.
-
Initial Server Settings: Locate and edit the server config files. Key settings:
Public=true/false
Password=yourpassword
DefaultPort=16261
DefaultGameMode=Sandbox
AdminPassword=youradminpassword - Launch and Test: Start the server. If using the dedicated server, run the ProjectZomboidServer.bat (Windows) or the start script (Linux).
- Invite Friends: Give friends your external IP or use the Invite via Steam feature.
-
Set Yourself as Admin: By default, the account "admin" with the password is the superuser. To set yourself as admin:
setaccesslevel "YourUsername" admin
Once you're admin, you can press ESC → Admin Panel to access admin commands easily.
Choosing Your Hosting Approach
In-Game Host (Co-op mode)
- Easiest setup - click Host from main menu
- Friends join through Steam's friend list
- Great for quick sessions or casual play
- Your PC's resources are shared between playing and hosting
- Server shuts down when you exit the game
- Ideal for 2-4 players who play at the same time
Dedicated Server
- Runs continuously, even when you're offline
- More stable for larger groups (5+ players)
- Better for heavily modded setups
- Requires more setup and configuration
- Needs sufficient hardware resources
- Recommended specs: Good single-core CPU, 4GB+ RAM
- Ideal for long-term communities across time zones
Hosting Providers
Not keen on running a server from your home network? Consider using a game server provider:
- Companies like G-Portal, Nitrado, GTXGaming offer PZ servers for a monthly fee
- They handle hardware and provide web interface for settings
- Simplified mod management with one-click installs
- Usually include DDoS protection and good uptime
- Cost is the main drawback, but saves technical hassle
Tweaking Server Settings
Project Zomboid has two types of settings: core server settings (in servertest.ini) and sandbox settings (in servertest_SandboxVars.lua).
Key Server Options (servertest.ini)
Public
If Public=true, your server will be visible in the public server list. For a private friend server, set this to false.
PvP
true/false. Decide if players can hurt each other. Many servers disable PvP to focus on co-op vs zombies.
PauseEmpty
When true, stops in-game time when no players are online. Recommended for friend servers with irregular play times.
WorkshopItems & Mods
Lists the Steam Workshop IDs and mod folder names. Used to manage which mods are loaded on the server.
AntiCheat
Settings to prevent cheating. Some legitimate mods may require disabling specific AntiCheat options (like type 12 for Brita's Weapons).
UPnP
If true, the server will attempt to automatically open ports on your router. Not always reliable. For manual setup, see our port forwarding guide.
Sandbox Settings (servertest_SandboxVars.lua)
Zombies = 3,
PopulationMultiplier = 1.0,
LootRarity = 3,
StarterKit = false,
...
}
Zombie Population
PopulationMultiplier=1.0 is default. Lower it to reduce lag or increase for more challenge. Warning: more zombies = more CPU load.
Loot Rarity
Adjust how common or rare items are. Set to abundant for casual play or rarer for hardcore scavenging.
Infection Mortality
Set Transmission = None for a more forgiving game where zombie bites don't doom players. Popular for casual co-op. For more details on infection mechanics, see our sickness survival guide.
Fire Spread
Consider setting FireSpread = false on public servers to prevent griefers from burning down towns.
Managing Mods on Your Server
Installing a New Mod
- Subscribe and Check Mod ID: Subscribe to the mod in Steam Workshop. Note the Workshop ID (number in the URL) and the Mod ID (internal name used by the mod).
-
Update Server .ini: Add the Workshop ID to the WorkshopItems line and the mod name to the Mods line:
WorkshopItems=2256623446;2256623668
Mods=Brita;BritaGunFighter - Ensure Clients Have It: When players join, they should get a prompt to download missing mods. Announcing mods beforehand helps.
- Restart the Server: Always restart after changing mods. The server will log each Workshop ID and attempt to download/update them.
Important: Build 41 saves and mods are NOT compatible with Build 42. If switching to B42, you'll need to start fresh.
Common Mod Issues & Solutions
Version Mismatch
If players get kicked with "Workshop item version different than server," restart the server to update mods. Consider the Update PLZ mod for automatic updates.
Anti-Cheat Conflicts
Some mods require disabling specific anti-cheat protections. For example, Brita's Weapons often needs AntiCheatProtection12=false.
Map Mods
Map mods need extra configuration. You must edit the Map= line in servertest.ini to include the map name, e.g., Map=Muldraugh, KY;BedfordFalls
Load Order
Mods load in the order listed in the Mods= line. If two mods modify the same thing, the last one in the list wins.
Recommended Admin/Utility Mods
Cheat Menu / Debug
Allows admins to spawn items, toggle god mode, and use other helpful tools through an in-game menu.
Update PLZ
Automatically checks for mod updates and safely restarts the server when updates are detected.
Safehouse Shield
Fixes bugs with safehouse protection, ensuring SafehouseAllowLoot=false truly prevents unauthorized looting.
Map Mods
Popular ones include Raven Creek (big city), Bedford Falls, Fort Redstone. They can attract players looking for new locations.
Keeping Your Server Running Smoothly
Hardware Considerations
- CPU: PZ server is CPU-heavy, particularly on one core. A CPU with higher clock speed will serve you better than one with many cores.
- RAM: Guideline is ~100-200 MB per player plus base overhead. If your server covers a lot of map area, memory use will be higher.
- Network: A wired connection for the server machine is strongly recommended. Hosting from home on a slow upload (<5 Mbps) might limit player count.
In Build 42, more calculations are moved to the server (to combat cheating). This means B42 servers might have higher CPU load than B41 for the same scenario.
Monitoring Performance
- Press F11 in-game (if admin) to see the performance panel
- Use /players command to list players and their ping
- Check console for error spam - often indicates mod issues
- Memory spike? Java heap might need increasing via -Xmx parameter
Backups
- Regularly back up your Zomboid/Server/<servername> folder
- Backup before adding new mods or after major patches
- Consider automating backups with scripts
- Some admins rotate backups (keep daily backups for last 7 days)
- No built-in backup in PZ - it's on you to protect your world
Periodic Maintenance
Cleanup
Enable corpse removal settings (HoursForCorpseRemoval). Admin commands like /removezombies can delete zombies in an area.
Auto-Restart
Consider setting up a mechanism to auto-restart on crash or schedule regular restarts (every 24 hours) to keep things fresh.
Mod Updates
Regularly check for mod updates, especially after game patches. The Update PLZ mod can help automate this process.
Admin Powers and Keeping Order
Admin Panel and Commands
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 that opens the panel.
Players Tab
Shows who is online, their Steam ID, ping, etc. You can teleport to them, bring them to you, heal them, or ban/kick.
Safehouses Tab
Manage claimed safehouses. You can remove abandoned safehouses or transfer ownership between players.
Items / Spawn Items
Search and spawn any item to your inventory. Useful for replacing glitched items or giving prizes for events.
Visibility and God Mode
Toggle invisibility (/invisible) and god mode (/god). Invisible makes zombies and players unable to see you.
Preventing Grief and Server Security
Safehouse Etiquette
Encourage players to claim safehouses and set rules like "Don't claim entire large buildings." Admins can unclaim if someone abuses the system.
PvP Rules
If PvP is allowed, decide on rules (random killing vs. consensual PvP). Consider enabling the safety system for new players.
Loot Respawn
Consider enabling loot respawn (HoursForLootRespawn) so new players joining later don't find empty towns.
Banning and Whitelisting
Use /ban username or the admin panel to ban troublemakers. For private servers, set Open=false and use /adduser to whitelist players.
Fun with Admin Commands
Don't forget you can use admin powers to create unique scenarios and events:
- Use /createhorde count X Y to spawn a zombie horde for an event
- Create a server-wide "air drop" by spawning supplies in a location
- Trigger helicopter event via /heli to spice up a quiet evening
- Control weather for seasonal events (snowstorm for Christmas)
- Build community areas using admin building tools
Build 42: New Challenges and Opportunities
No Upgrade In-Place – Start Fresh
You cannot simply load a Build 41 save on a Build 42 server. The differences in data are too big. Plan a server wipe or new world when moving to B42.
This is an opportunity – hype it up as a "Season 2" for your community. Players will be bummed to lose progress, but many also get excited for a fresh start with new content.
New Features to Configure
- Animal Husbandry: Players can find, pen, and breed animals. These need server resources like zombies do.
- New Professions & Crafting: B42 expands blacksmithing, pottery, etc. Consider knowledge sharing policies.
- Aiming Changes: B42 introduced major changes to firearms aiming. Players might need time to adapt.
- Lighting & Graphics: Some players with low-end PCs might blame the "server" for client-side FPS issues.
Map & Generation Changes
- Map Expansions: B42 adds new towns and locations. Expect an initial surge of exploration.
- Wilderness Generation: Beyond map edges, the server can generate endless forests. Monitor server storage if enabled.
- Loot System Overhaul: The way looted buildings are tracked changed. Test any custom loot respawn settings.
- Official Mod Support: B42 includes an official mod manager UI. This may simplify mod management.
Community Engagement with B42
New features are great opportunities for events:
- Host a server-wide "Farmers Fair" once people tame animals
- Hold a virtual "beer festival" where players share their homebrew
- Organize exploration parties to discover new map areas
- Create challenges around the new crafting systems
Wrapping Up: Keeping It Fun and Fair
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.
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).
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.
Action Steps Recap (TL;DR)
- Set Up Right: Use the in-game Host for small groups or a dedicated server for long-term communities.
- Tune Performance: Adjust zombie count and settings to match your hardware capabilities.
- Manage Mods Carefully: Always match Workshop IDs and Mod IDs in the config.
- Use Admin Tools: Familiarize yourself with admin commands and the panel.
- Secure the Server: Enable safehouse claiming and adjust settings to protect players' bases.
- Backup, Backup, Backup: Regularly save copies of your world data.
- Plan for B42: If not yet on B42, start preparing your community for the transition.
- Stay Communicative: Talk to your players and take polls on setting changes.
- Have Fun: Run events and be a bit playful as the all-seeing admin.
Further Resources
- Project Zomboid Official Wiki – Server Administration: Up-to-date info on every server setting and admin command.
- The Indie Stone Forums – Help Section: If you encounter a weird issue, search the Multiplayer section.
- Project Zomboid Discord: Official channel for server hosting where you can ask questions.
- Steam Community Guides: Search for keywords like "server" and "multiplayer".
- Community Servers: Join established servers to learn how they operate.
Happy hosting, and remember: When life gives you zombies, make zombie stew – or better yet, let your players do it and just ensure the pot stays on the fire! 🧟♂️🔥