Direct answer

Build the server in layers: documented SteamCMD install, known launch directory, vanilla startup, one matching client, backed-up settings, then mods. After every update, verify the startup version instead of assuming a panel changed the running install.

Do this first

  1. Document fixed install and data directories.
  2. Install or update through SteamCMD.
  3. Start vanilla and record the version from logs.
  4. Join with one client on the same build.
  5. Back up working configuration before Workshop items.

A reproducible server is easier to repair

Record install path, data path, launch command, version, ports, settings, and mod identifiers. A control panel is convenient, but underlying paths and logs decide what ran.

Update without guessing

Stop the instance, back up world and configuration, update the correct install, restart, and read the startup version. Resolve client differences before changing save or Workshop list.

Add mods after vanilla works

A vanilla checkpoint gives a known-good path. Add one compatible item and dependencies, verify a client can join, then expand in batches and preserve the working list.

FAQ

Quick answers

What is the key update check?

The version printed by the running server after restart, compared with the connecting client.

Should I add every mod before first launch?

No. Establish a working vanilla connection first.

Evidence log

Sources checked

Official sources establish universal facts; forum and specialist sources are used for symptoms, vocabulary, and cross-checking.

Platform docsSteamCMD Documentation

Platform documentation for installing and updating dedicated server applications through SteamCMD.

OfficialProject Zomboid Build 42.20 Released

Official Stable status, legacy41 instructions, and the explicit Build 41/42.19 save boundaries.

Official forumBuild 42.13 Multiplayer Released

Official forum background on Build 42 multiplayer, mod compatibility, and conservative server testing.