zomboid-review

Run a structured review gate that checks the git diff, verifies the B42.20-selected version folder and mod.info, inspects console.txt for error families, and probes domain-specific risks like loot paths and Java bridge calls. Findings are ranked by severity with required fixes.

Lua syntax checks like lua5.1 loadfile only validate syntax, not PZ globals, Kahlua userdata, Java method signatures, or event payloads. Runtime failures require verifying Java-exposed methods against decompiled sources and checking console logs for stack traces.

Yes, it verifies Workshop sources under the Steam workshop content folder before local patching, and checks that project-backed live installs are correct symlinks under the Zomboid mods directory resolving to the expected versioned mod.info.

Findings are ordered by severity: Critical or High block closeout, Medium indicates likely user-facing bugs, and Low covers polish issues. Each finding includes the file path, concrete risk, evidence from diffs or logs, and the required fix.

The review cannot prove in-game behavior outside the Project Zomboid runtime, such as live rendering, event timing, or actual gameplay flows. Remaining manual in-game validation is always stated explicitly in the final report.