Skip to content

Get 25% OFF your first month on every game! 🎉

In Australia? Our Australian site has the same servers, priced in Australian dollars.
In Australia? Our Australian site has the same servers, priced in Australian dollars.
In New Zealand? Our site for Australia and New Zealand has the same servers.
In New Zealand? Our site for Australia and New Zealand has the same servers.

Project ZomboidTroubleshooting

Fix Project Zomboid file mismatch error

Fix players being kicked for a file that does not match the server: restart for mod updates, match the build, repair their files, or the checksum setting.

Updated 3 min read

A player who joins your Project Zomboid server and is kicked with the message "You have been kicked because your game files do not match the server's." has hit the server's checksum check, DoLuaChecksum, which the game describes as "Kick clients whose game files don't match the server's." Build 42's settings file also has AntiCheatChecksum, which the game describes as checksum anti-cheat protection. The steps below start with the causes our panel can show you. Checked against Build 42.21, October 2026.

Check the server first

Work through these in order.

  1. Restart if a Workshop mod updated. When a mod updates on Steam, players on the new version can't join until the server restarts. A banner at the top of the panel says Workshop mods need an update, and the Mods tab shows Mods need an update. Press Restart to update, wait for Your server is online in the Console, and ask the player to try again. How to add Project Zomboid Workshop mods explains the banner and the nightly restart that avoids it.
  2. Match the game build. Open Server Settings and read the Game build card. It shows Build 42 (current) or Build 41 (legacy). A player on the other build isn't running the build the server is. They right-click Project Zomboid in Steam, open Properties, choose the Game Versions & Betas tab and pick the server's build.
  3. Check the mods loaded cleanly. The Check the mods loaded section of How to add Project Zomboid Workshop mods shows what to look for in the Console and Logs while the server starts. Disable a mod that didn't load in the Mods tab, or fix its ID, and restart, so the server's list is the one you meant.

Then fix the player's side

If the server is up to date and the build matches, the player's own files are the next suspect.

  1. Verify the game files in Steam. How to verify your game files on Steam has the steps. It makes Steam check the player's copy of the game.
  2. Unsubscribe from the Workshop items and rejoin. Open the player's Steam Workshop subscriptions for Project Zomboid and unsubscribe, then join the server again. The game downloads the server's own Workshop items when a player joins, so they get the versions the server runs.

If it only happens to some players

Compare the failing players with the ones who join fine. Ask each for the build they run (Properties > Game Versions & Betas in Steam) and which mods they have enabled. Look for what the failing players have in common.

Turn the check off only as a last resort

The check is the DoLuaChecksum line in the server's .ini file, and it is on. Setting it to false stops the server kicking clients whose game files don't match its own.

Warning

Switching it off removes a check, so try every step above first. If it is the only way to get players in, stop the server, set DoLuaChecksum=false in .cache/Server/<world>.ini with the File Manager, and start the server. Take a backup first: How to create and restore backups.

If players are being kicked with a different message, read Fix the Project Zomboid malformed packet error. If a player can't connect at all, Project Zomboid: getting started covers the address and the join steps.

Ready to launch your Project Zomboid server?

Your choice of location, NVMe disks and DDoS protection, with the version and mod loader yours to change whenever you like.

See Project Zomboid plans