Recommended Free Tools
To disable anti-cheat on a Project Zomboid server, stop the server, edit its generated server configuration, save the change, and restart. The correct setting depends on the game build: Build 41 uses AntiCheatProtectionTypeN flags, while Build 42 uses named anti-cheat options with enum values. Change only the check that is producing a legitimate mod false positive unless the server is private and limited to people you trust.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Project Zomboid servers with free DDoS protection and up to three free backups a day.
A setting such as AntiCheatProtectionType12=false is not the legacy disable instruction. In the Build 41 template, the comment for each key says that the protection is disabled when its value is true. Build 42 does not use that Boolean convention, so do not copy a Build 41 value into a Build 42 option.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Before you edit: identify the server build
Project Zomboid has two different anti-cheat configuration schemes in the versions covered here. Editing the wrong scheme can leave the kick in place or produce an invalid setting.
| Server version | Configuration style | What to look for | Disable approach |
|---|---|---|---|
Build 41 (including the legacy41 branch) |
Numbered legacy flags | AntiCheatProtectionTypeN, where N is a protection type number |
Set the implicated type to true, following the comment in the generated template |
| Build 42 | Named options backed by enum values | Options such as antiCheatSpeed, antiCheatNoClip, and antiCheatChecksum |
Use the value and spelling generated by the exact Build 42 version; the hosting guidance identifies 3 or 4 as values to try for mod false positives |
Use the configuration file generated by the running server version rather than a file copied from another installation. Build 42 enum meanings can change between builds, and the comments or defaults in your own generated INI are the authoritative guide for that build.
#1 Best Overall
Build 41: disable one legacy anti-cheat type
1. Shut down cleanly and make a backup
- Stop the Project Zomboid server through its normal shutdown command or your host’s stop control.
- Wait until the process has finished writing its files. Do not edit an INI while the server is still running.
- Make a copy of the server INI before changing it. Keep the backup outside the active configuration location so it cannot be mistaken for the file the server loads.
A clean stop matters because the server generates and rewrites configuration. If you edit during a running session, a later save can overwrite your change.
2. Open the generated server INI
Open the generated server configuration in the server’s Zomboid Server directory, or the equivalent file supplied by a managed host. A control panel may provide an editor for the same INI instead of exposing the directory directly. Confirm that the file belongs to the server instance and profile you are starting; editing a spare profile has no effect on the active server.
3. Find the protection named by the kick
Search the INI for the key identified in the kick or server log. The legacy pattern is:
AntiCheatProtectionTypeN=...Replace N with the type reported by the message. For example, a report for type 12 points you to AntiCheatProtectionType12. If the message names a different check but not a number, inspect the log and the surrounding template comments rather than guessing a type.
4. Set the legacy disable value
In the Build 41 template, each numbered entry is documented with a comment such as “Disables anti-cheat protection for type N.” The disabling value is true. Change only the implicated entry first:
AntiCheatProtectionType12=trueThis is why AntiCheatProtectionType12=false does not accomplish the requested disable in the legacy template: false leaves that protection enabled.
5. Save, restart, and test
- Save the INI without changing unrelated server settings.
- Start the server again.
- Have the affected player reconnect and reproduce the action that caused the false positive.
- Watch the server log for a different anti-cheat type or a repeat of the original message.
If another type is identified, stop the server again and disable that additional type using the same documented convention. Keep all other types enabled.
Build 41: when disabling every protection is appropriate
The official release note for the cited Build 41 release says that an administrator who does not run a public server—specifically, a server exclusively for family and friends without concern about griefing and cheating—can avoid false-positive frustration by disabling all anti-cheat protections in the server INI. That advice is explicitly framed around a trusted private server.
Rank #2
- Do Not Begin Unless You Intend to Finish – Jumanji The Board Game takes you & your fellow adventurers on a quest through the jungle, solving riddles & completing challenges as you fight to survive
- Jungle Adventure for 2-4 Players – Roll to determine the number of spaces to move, then race across the colorful jungle-themed board to be the first to reach the center & yell “JUMANJI” to win
- Discover Jumanji’s Secrets – What would Jumanji be without a little trickery? Slide a card into the center decoder to magically reveal the next challenge you must overcome on your way to victory
- Family Game Night: Make memories with board games for kids 4-6, board games for kids 6-8 & board games for kids 8-12. take the fun outside with camping games & outdoor games for adults and family
- Spin Master Toys & Games: Looking for kids games, yard games & card games for grown ups, kids or teens? Shop everything from family game night, travel games, puzzles for adults & family games
Do not treat the all-types approach as a general fix for public servers. Anti-cheat checks enforce server-side rules; removing them broadens what a modified client or malicious player can send or do. A private server with a small, trusted group may accept that trade-off, while a public server normally should isolate the one check causing the false positive.
Build 42: use named anti-cheat options
Options you may see
The Build 42 ServerOptions reference uses named options rather than the numbered legacy pattern. The documented names include:
Free tools Windows power users keep installed
One-click scans. No signup required.
antiCheatSpeedantiCheatNoClipantiCheatHitantiCheatPacketExceptionantiCheatPermissionantiCheatXpantiCheatSafeHouseantiCheatPlayerantiCheatChecksum
Your generated INI may display capitalization such as AntiCheatSpeed. Match the exact key spelling already present in that file; do not create a second version of the same option with different capitalization.
1. Stop and back up the Build 42 configuration
- Stop the server cleanly.
- Back up the generated Build 42 INI.
- Open the active INI in the Zomboid Server directory or the managed-host editor.
2. Match the kick to a named check
Use the kick message and server log to determine whether the problem involves speed, no-clip movement, hit validation, packet exceptions, permissions, experience, safe-house rules, player validation, or checksum validation. If the message identifies a check, edit that check first instead of changing every option.
3. Use the enum value from your generated file
Build 42 options are not Boolean switches with a universal true or false meaning. A current hosting guide for Build 42 identifies values 3 or 4 as settings to try for mod-triggered false positives. Those numbers are enum values, not a promise that one value disables every check in every Build 42 revision.
Read the inline comment or generated default next to the option in the exact version you run, then set the value there. For example, the workflow is:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
antiCheatPacketException=<value documented by your generated Build 42 INI>Replace the placeholder with the actual numeric value shown or recommended for your version. Do not paste true from a Build 41 instruction into a Build 42 enum option, and do not assume that the same number has the same effect after a game update.
4. Save and restart
- Save the edited INI.
- Start the server.
- Reconnect the affected player.
- Test the mod action while monitoring the log.
If the kick changes to another named check, adjust that check only after another clean shutdown and backup. If the setting is ignored, verify that the host panel saved the same INI loaded by the running instance and that the server is actually on Build 42 rather than the legacy41 branch.
Rank #3
- Cooperative Game: Marvel Zombies: Heroes’ Resistance is a strategy game where 1-4 players control the last surviving superheroes facing off against zombie heroes and the zombie hordes controlled by the game itself
- Over $9 Million On Kickstarter: You wanted this adult board game by Zombicide, and you got it. This game takes about 1 hour to play, for everyone ages 14 & up
- How To Play: The goal of this adult game is to complete mission objectives, defeat your enemies, & rescue endangered bystanders. Work together & push their powers to the limit so you can put an end to the zombie apocalypse
- Family Game Night: Make memories with board games for kids 4-6, board games for kids 6-8 & board games for kids 8-12. take the fun outside with camping games & outdoor games for adults and family
- Spin Master Toys & Games: Looking for kids games, yard games & card games for grown ups, kids or teen? Shop everything from family game night, travel games, puzzles for adults & family games
Choosing between one check and all checks
| Approach | Best fit | Security effect | Operational cost |
|---|---|---|---|
| Disable one implicated check | A mod causes a specific, repeatable false positive | Other anti-cheat protections remain active | Requires reading the kick or log and possibly repeating the process for a second identified check |
| Disable every protection | A private server for trusted friends and family where griefing and cheating are not a concern | Server enforcement is broadly removed | Simple once the server INI is identified, but every player and mod must be trusted |
The official rationale for disabling all protections is limited to the private-server case. On a public server, start with the narrowest change that resolves the false positive and retain the other checks.
Troubleshooting malformed-packet and mod kicks
The message says “malformed packet” or identifies a packet exception
First determine whether the message names the legacy type or the Build 42 packet-exception option. On Build 41, edit the corresponding AntiCheatProtectionTypeN key and set it to true. On Build 42, edit the named packet option using the enum value documented in that version’s generated INI; the current hosting guidance suggests trying 3 or 4 for mod false positives.
The change had no effect
- Confirm the server was stopped before editing and restarted afterward.
- Check that you edited the generated INI for the active server profile, not a backup or unused profile.
- Verify the build branch. Build 41 keys and Build 42 named options are not interchangeable.
- Check capitalization and spelling against the key already generated in the file.
- Look for a later anti-cheat message naming a different check.
- If a managed host is involved, confirm that its panel saved the file and that the panel’s start button launches the same instance you edited.
The server still kicks after the relevant check is disabled
A single mod can trigger more than one validation path. Reproduce the issue, record the next type or named check in the log, and change only that newly identified setting. Do not disable unrelated protections simply because the original change did not solve a different check.
You are running an older Build 41 release
Anti-Cheat Types 21–24 were adjusted in the cited 41.76 release to reduce false positives. Updating to a release containing those adjustments may solve the problem without disabling a protection. If you cannot update, use the narrow legacy setting documented in your generated INI.
Public-server and player-impact considerations
Anti-cheat configuration is server-side. After a restart, players may need to reconnect before the new enforcement settings apply. The available documentation does not establish a measured reconnection time, performance change, CPU saving, or network-overhead reduction from disabling checks, so do not promise any of those outcomes.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →For a public server, document any exception you make, restrict the change to the check implicated by the mod, and reassess it after the mod or game build changes. For a private server, disabling all checks can remove false-positive friction, but it also means the server is relying on the trust of its players rather than these protections.
Managed hosting versus a self-managed server
A managed Project Zomboid host may expose the same generated INI through a control panel. The underlying workflow remains the same: stop the instance, edit the relevant option, save, and start it again. Panel labels and file locations differ by provider, so use the host’s current instructions to verify which server profile and build the panel controls.
Do not assume that a panel’s “anti-cheat” switch maps to every check. If the panel offers raw INI editing, compare the generated keys with the Build 41 or Build 42 patterns above. If it offers only a high-level toggle, ask the host which underlying option it changes before using it on a public server.
Quick Recap
Final verification checklist
- The server was shut down cleanly before the file was edited.
- A backup of the active generated INI exists.
- The build was identified as Build 41/legacy41 or Build 42.
- Build 41 uses the implicated
AntiCheatProtectionTypeN=truesetting. - Build 42 uses the exact named option and enum value documented by the generated file for that revision.
- Only the check implicated by the false positive was changed unless the server is private and trusted.
- The edited file belongs to the instance that was restarted.
- The affected player reconnected and the original action was tested again.
- The server log was checked for a new or remaining anti-cheat check.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
