Setup & servers
Set up Viewpoint QOL and Simple Mod Check for a server
List the required mods on the server, but configure ZombieBuddy and Java approvals on every player's PC. For Simple Mod Check, keep Lua checksum enabled, start with Enforce Off, let a staff member join and review the log before enforcing the baseline.
On this page
Separate the server list from the client runtime
| Where | Responsibility |
|---|---|
| Server ini | Keep the mod IDs and Workshop IDs in their respective lists; preserve other entries. |
| Every player's PC | Set up ZombieBuddy, enable the required mods and approve intended Java files. |
| Simple Mod Check server | Run its Lua part and keep DoLuaChecksum enabled; it does not need the ZombieBuddy Java runtime on the server. |
| Staff baseline | Use genuine Workshop files; staff who can kick supply the reference fingerprints. |
QOL's author calls its code client-side while still requiring the server list below. Treat those as separate responsibilities. Do not install a Windows client DLL on a rented server simply because your clients need it.
Preserve entries when adding QOL
The author gives these three entries for QOL. Add them to the existing lines, separated by semicolons, rather than creating duplicate keys or replacing all your other mods.
QOL IDs and the optional checker
Mods=ZombieBuddy;Viewpoint;ProjectViewpointQOL
WorkshopItems=3619862853;3809306528;3811256204For Simple Mod Check, add SimpleModCheck to Mods and 3812617481 to WorkshopItems, preserving the rest. These lines identify the modules discussed here; they are not a complete list for every model pack or additional mod on your server.
Each player completes the one-time ZombieBuddy setup and approves the QOL JAR when prompted. Confirm a friend's loader indicator before blaming the server list for a local loading failure.
Establish a baseline before enforcing it
- Use the checker on its author-documented Build 42.21 environment and add it to the server mod list.
- Keep
DoLuaChecksumon. On the Simple Mod Check sandbox page, set Enforce Off for the first run. - Have a staff member who can kick join with genuine Workshop files and the required Java parts loaded.
- Read the server's Logs folder and staff messages. Resolve missing, declined or mismatched files on a test connection before enabling enforcement.
- Turn Enforce on only after the expected mod set has a usable reference.
Enforce Off is a baseline-inspection step, not evidence that an unchecked client passed. Check a normal player's intended mod set as well as staff setup before inviting everyone.
Understand updates and failed checks
The checker compares SHA-256 fingerprints of loaded Java mods. After an update, the new fingerprint takes effect following a server restart and is confirmed by the first staff member or, by default, three different players reporting it. Missing loader, declined/missing/edited JARs and no report are author-listed failures. Review the exact reason in the log; do not remove checksum checks to conceal a mismatch.
What this checker cannot guarantee
The author describes a failed player's own checksummed client Lua disconnecting that player, with a 20-second failure delay. This is a consistency check for the intended client mod set; it cannot prevent someone rewriting the game client itself.
It also does not prove that every rendering mod, save or GPU is compatible. A camera crash without a fingerprint failure belongs in Viewpoint loading/rendering troubleshooting, not a forced change to the server security baseline.
Sources & version
Based on author documentation and community instructions, not our own gameplay test. Later updates may change defaults.