Project Zomboid Dedicated Servers for Build 42

A listen-server from the in-game Host menu is enough for two friends on a LAN. A dedicated server is what you want when the world should keep simulating after everyone logs off, when you rent a box, or when 42.20.3’s 254-player handling actually matters. Project Zomboid Early Access still expects you to match the exact build string, back up the Zomboid folder, and treat Workshop mods as a shared contract. This guide covers the Steam dedicated-server tool, the first-run config files, the servertest.ini keys that decide whether anyone can join, ports, and the August 2026 hotfix habits that stop “Loading Map” tickets. It is not a replacement for Servers and Co-op social rules or Multiplayer Mods load order-read those before you open ports to strangers.

Dedicated versus in-game host

In-game host: convenient, dies when the host client closes or crashes, shares the host PC’s FPS hit. Fine for a weekend with three people.

Dedicated: separate process (or separate machine). The world keeps time, weather, and zombie migration while you sleep. You edit INI files instead of a single GUI pass. You must update the server files when Steam updates the Build 42 default branch-42.20.3 as of 17 August 2026.

Local split-screen does not exist. Dedicated still means online co-op on PC. Agree Sandbox settings before the first character rolls; the server owns those values globally.

Build 42.20 dedicated server tutorial: first boot and servertest.ini

Install paths: Steam app versus SteamCMD

On a desktop you already use for Zomboid, install Project Zomboid Dedicated Server from your Steam library tools list, then run StartServer64.bat from the install folder. The first launch generates default configs and may take several minutes while it unpacks the doubled Build 42.20 map.

On a headless box, use SteamCMD to install the dedicated-server app into a folder you control, then run the same start script. Always stop the server with a clean exit (answer Y if Windows asks to terminate the batch job) before you copy or edit files. Never patch a running world.

After the first successful boot, shut down and go to your user folder:

C:\Users\<you>\Zomboid\Server\

Copy servertest.ini to servertest-backup.ini before you touch anything. The video mid-page walks that first boot visually; the rest of this page is the checklist hosts skip.

servertest.ini keys that actually matter

Open servertest.ini in a text editor and set at least:

• Public=true if you want the server listed. Leave false for bind-on-LAN-only tests.
• PublicName and PublicDescription - the browser label. Put the build string in the description (42.20.3 stable) so players do not join a leftover 42.19 box.
• Password - the join password, not the RCON line. Blank join passwords on a public listing attract grief. RCON password is a separate field; leave it unset unless you actually use RCON.
• Open=true - if this stays false, the listing can exist while nobody can connect. Confirm it after every copy-paste of an old INI.
• MaxPlayers - 42.20.3 improved handling up to 254, and administrators can join when the server is full. That is a capacity ceiling, not a performance promise. A doubled Knox County plus animals plus basements still wants RAM and a daily restart more than a 200-player vanity cap.

Save the file, start the server again, then confirm the main-menu build string on a client. If Steam is still on a beta branch, you will fight invisible version mismatches. Default / None is current stable 42.20.x. Finish 42.19 worlds on the 42.19 beta; they do not load in 42.20. legacy41 is only for Build 41.

Ports, forwarding, and join flow

Default UDP ports are still the Zomboid set: 16261 (server), 16262 (Steam), plus 8766 depending on your Steam networking path. Forward those on the host router if players are not on LAN. Renting a host panel usually exposes IP plus a port field-paste the IP without a trailing :port in the IP box and put the port in the port box, the way most 42.20 video walkthroughs show.

Clients: Multiplayer → Add server → name, IP, port, password → create the admin account on first connect if you are the operator. 42.20.3 fixed clients hanging forever on Loading Map; if someone still hangs, they are often on a stale client, a broken Workshop list, or an out-of-memory box-ask for logs, not for you to “open more ports.”

Memory, restarts, and 42.20.3 hygiene

The August hotfixes chased memory leaks, chunk-unload lag, lighting errors, and grey boxes while travelling. Dedicated hosts should still:

1. Schedule at least one restart per day in a low-pop window.
2. If a new save out-of-memory-crashes, file a report with logs and a debug profiler video as The Indie Stone requested-do not keep raising -Xmx blindly on a dying Java process.
3. Keep the % → %% mod-text rule from 42.20.2. A dedicated box with old Workshop tooltips can still spam errors.

Pin the workshop ID list in Discord. After every Steam update, update server files first, then ask players to verify their game cache. See Returning Players if someone is still on an unstable branch by accident.

Mods on a dedicated box

WorkshopItems (numeric IDs) and Mods (mod IDs) both have to match. The in-game mod manager on clients does not magically sync a dedicated INI. Follow Multiplayer Mods. Never host a Build 41 world folder on a Build 42 server-42.20.1 already blocked some of those foot-guns; do not test the rest.

Backups and wipe votes

Copy the entire Zomboid user folder (saves, Server INIs, logs) before map-touching patches. 42.20.0 doubled the map; 42.20.x hotfixes should not wipe 42.20 saves, but mods and disk faults still do. Schedule wipe votes in the group instead of surprising people mid-week. Admin join-when-full is for operators who need in, not for skipping the player cap on a machine that already swaps.

Related reading

1. Servers and Co-op - etiquette, PVP, public listings
2. Sandbox settings - lock rules before day one
3. Multiplayer Mods - Workshop hygiene
4. Build 42 Overview - branch cheat sheet
5. System Requirements - if the box is also a playable PC

A dedicated server is a second copy of Knox County with a longer uptime. Treat the INI like a generator: label it, back it up, and do not run it on empty after a patch night.