Fix mods
Find a Project Zomboid mod conflict without breaking your save
Reproduce on a new test world, confirm the necessary ZombieBuddy/Viewpoint baseline, then compare subsets of optional mods while keeping every required dependency. Narrow the failing set using the same action each time. If both subsets work alone, test their interaction instead of blaming the last mod in the list.
On this page
Define a short, repeatable failure
PZwiki’s older Build 41 troubleshooting article describes comparing mod subsets. Here we adapt that approach to Viewpoint’s dependency chain; this is a diagnostic procedure, not a tested fix for a named Build 42 conflict.
- Back up the original world and record game, loader and mod versions. Keep the experiment on a new world.
- Write one reproduction: for example, open a container, attempt one transfer and note the visible error or log time.
- Check the base game without optional mods where the action exists. Then test the required Viewpoint stack.
- If the minimal camera stack already fails, investigate installation or Java status before testing a dozen add-ons.
A missing dependency invalidates the comparison. Keep ZombieBuddy and Viewpoint whenever an enabled companion requires them. Keep other library requirements with their consumers as well.
Split optional features, not required libraries
- Confirm that your full optional set reproduces the failure on a fresh test.
- Divide the optional features into two roughly equal groups. Add each group’s required dependencies to its test list.
- Launch the first group with the working core, use a fresh test world and repeat the exact action. Record the result and enabled list.
- Repeat with the other group under the same conditions.
- If one group fails alone, divide that group again until you have a small reproducible set.
Restart between comparisons so an already loaded Java companion cannot confuse the next run’s status. Do not alter presets, bindings, graphics and mod selection together; keep the conditions that matter to the reproduction constant.
If neither half fails alone
The failure may require an interaction across the groups. Restore the known failing full set, then remove one optional feature at a time while retaining dependencies needed by the remainder. Keep each exact list and result. A passing half does not prove all its mods work with every mod in the other half.
Also check whether the original symptom depended on an old world, a particular input overlap or a server. A new-world test cannot prove an existing save is compatible, and a local test cannot certify multiplayer. For relocated keys use the control-layer comparison; for joining failures use the named file mismatch route.
Send the smallest useful report
Include the failing combination, the nearest passing comparison, required libraries, version numbers, one reproduction and the failed run’s console.txt. Say whether it is a new world or an existing save and whether the failure is local or multiplayer.
Do not label an author’s mod universally broken from one stack. Keep your original save and mod-list note intact while waiting for a targeted answer; mass unsubscribing or deleting all settings discards the comparison you just established.
Sources & version
Based on author documentation and community instructions, not our own gameplay test. Later updates may change defaults.