RaidBench / Project Zomboid / Decision guide

Project Zomboid mod conflict isolation checklist

Find a broken Project Zomboid mod combination with a repeatable clean test instead of repeatedly damaging the main save.

Run the checklistOpen Project Zomboid hub
Reviewed 2026-09-03Patch-sensitiveNo paid answer offeredEditorial standards

How do I identify which mod is breaking the game or save?

Direct answer

Reproduce the problem in a disposable profile, confirm the unmodded baseline, and restore mods in small groups. Keep the load order and game build fixed during each comparison so a successful launch actually tells you something.

Decision signalWhat to verifyNext move
Problem exists unmoddedTest a clean profile on the same buildInvestigate the base game or local files first
Problem disappears cleanEnable half the suspect setContinue narrowing the failing group
Load order mattersRepeat with the same mods in controlled orderRecord the smallest failing combination

Decision checklist

  • Back up the affected save before changing the mod list
  • Record the game build and complete enabled-mod order
  • Confirm a clean disposable profile can reproduce or clear the issue
  • Restore mods in bounded groups rather than one random order
  • Keep logs and the smallest failing combination

Stop and recheck when

  • Stop using the main save when a test changes map or item data
  • Do not declare a fix until the same setup survives a restart

Common mistakes

  • Testing directly on the only valuable save
  • Changing build, mods, and load order together
  • Assuming one successful launch proves long-session stability

Sources and evidence boundary

Decision frameworks for the current stable Project Zomboid branch. Back up saves and recheck build-specific behavior before changing an established world.

Reviewed 2026-09-03. Publisher-controlled sources may support factual claims. The community thread supports topic selection only. Unsupported mechanics, exact values, and outcomes must not be inferred.