5 Practical Tips for Project Zomboid Server Administrators

For Project Zomboid Build 42.19 server options.

Good administration starts with clear rules and settings you can repeat after a restart. The five sections below cover option names, where they live, what they change, and the tradeoffs players will feel.

If you use Host > Manage Settings, the game edits both groups through its interface. Manual file editing is most useful for dedicated servers; keep the exact capitalization of every key.

1. Use UPnP for automatic internet port forwarding—not for LAN-only play

UPnP=true asks a UPnP-enabled internet gateway to create port-forwarding rules automatically. This is not a LAN-only feature: devices on the same local network normally do not need router port forwarding to reach each other.

Build 42.19 defaults UPnP to true. If automatic setup fails, the server falls back to its default ports. Confirm DefaultPort and UDPPort in the INI file instead of restarting without reading the log.

2. Turn your PVP policy into exact settings

“PVP enabled” is not a complete rule. Decide whether combat is disabled, always active, or controlled by the safety system, then publish that policy before players create characters.

PVP=false

PVP=true
SafetySystem=true
ShowSafety=true
SafetyToggleTimer=2
SafetyCooldownTimer=3
PVPLogToolChat=true
PVPLogToolFile=true

With PVP=true and SafetySystem=false, players may damage one another at any time. With the safety system on, damage is possible when at least one participant is in PVP mode—do not advertise it as mutual-consent combat. Defaults in Build 42.19 are PVP on, safety on, toggle timer 2, cooldown 3, and both PVP logging options on. Test the timing before launch and explain it in the welcome message.

You do not need to disable PVP globally to protect a spawn point or trading hub. An authorized administrator can create a Non-PVP Zone from the Admin Panel and define the protected area on the map.

3. Configure loot respawn as a complete rule

“Resource refresh time” is too vague. These sandbox settings control container loot and work together:

The Build 42.19 Apocalypse preset uses HoursForLootRespawn=0, SeenHoursPreventLootRespawn=0, MaxItemsForLootRespawn=5, and ConstructionPreventsLootRespawn=true. For a persistent public server, choose a nonzero respawn interval only after deciding how much scarcity, trading, migration, and support for new players you want.

4. Enable recoverable backups and regular saves

Autosaving and backups solve different problems. SaveWorldEveryMinutes saves loaded map areas after the specified real-world interval; rotating ZIP backups give you older recovery points after corruption, a bad mod update, or an administrative mistake.

BackupsCount=5
BackupsOnStart=true
BackupsOnVersionChange=true
BackupsPeriod=60
SaveWorldEveryMinutes=10

• BackupsCount=5 keeps five rotating files for each backup type (default is 5).
• BackupsOnStart=true creates a startup backup (enabled by default).
• BackupsOnVersionChange=true backs up when the detected game version changes (enabled by default).
• BackupsPeriod is measured in real-world minutes. Default is 0 (periodic backups off); the example uses 60 minutes.
• SaveWorldEveryMinutes is also measured in real-world minutes. Default is 0; the example saves every 10 minutes.

5. Define safehouse, raid, and protected-zone rules together

Safehouses affect access, fire, looting, respawn, inactivity cleanup, and loot refresh. Configure them as one policy rather than changing individual checkboxes after disputes begin.

PlayerSafehouse=true
AdminSafehouse=false
SafehouseAllowTrepass=false
SafehouseAllowFire=false
SafehouseAllowLoot=false
SafehouseAllowRespawn=true
SafehouseDaySurvivedToClaim=1
SafeHouseRemovalTime=144
SafehousePreventsLootRespawn=true

This example allows players and admins to claim protected cooperative bases after surviving one in-game day. Non-members cannot enter or loot them, fire cannot damage them, members may respawn there, and an inactive member is removed after 144 real-world hours. It also prevents loot respawn inside the claimed building.

A raid server may deliberately enable trespass, fire, or looting, but those choices should be announced before play. Use Non-PVP zones for spawn and public trading areas, and record administrator-created events or compensation so players can distinguish a published event from hidden intervention.

Administrator launch checklist

1. Back up the complete server user-data folder.
2. Write down whether each change belongs in <server>.ini or <server>_SandboxVars.lua.
3. Change one category at a time and restart the server.
4. Confirm the loaded values and any UPnP or port result in the startup log.
5. Publish PVP, loot respawn, safehouse, reset, mod, and admin-intervention rules where players can read them.
6. Test with a non-admin account before opening the server publicly.

For related tasks, see the guides to grant administrator access, add server mods, review server settings, and troubleshoot connection problems.