DayZ Hub · Mods
DHUB Diagnosticsv1.1.0
Server-side
Patches a known vanilla crash/dupe exploit in inventory manipulation, and logs the difference between a fluke and an active exploit attempt.
Free for DayZ Hub customers
Included for DayZ Hub customers — a server on Premium 3, or Premium 1 / Premium 2 billed annually.
Log in with Discord
See plans
Features
- Fixes a real vanilla crash (and dupe exploit vector) in HandleRemoteItemManipulation — combine, split, and move
- Silent during normal play — only writes to disk when something actually goes wrong
- Flood detection flags when guard trips look like an active exploit attempt, not a one-off
- Tracks trips per player by Steam64, so you can tell "something is wrong" from "watch this one player"
- Log file is self-trimming, so it never grows forever on a long-running server
Good to know
Why it's useful
Vanilla DayZ can crash when a client sends a broken inventory-manipulation request — splitting, combining, or moving a stacked item with a missing item reference. It's a documented crash/dupe vector, not a rare edge case, and it can be triggered deliberately. This mod rebuilds that one vanilla method with a safety check at the exact crash point, so a bad request gets rejected instead of taking your server down — everything else about vanilla behavior stays exactly the same.
Setup
Server-side only — your players don't need it. Add it to your server's addons as a server-side mod (most hosts call this "Server-Side Mods" — or use -serverMod=, not -mod=), and load it LAST, after any other mod that also touches inventory/item manipulation (loot/economy mods, other anti-dupe tools). Nothing for players to download. Config and log auto-create on first boot under <profile>\Dayzhub_diagnostics\.
📣 Update Log
v1.1.02026-08-22
- Re-verified line-by-line against the current game build — the handler still matches vanilla exactly, so there's no behavior change for players
- Guard trips now also print a short line to the server log (RPT), not just the diagnostics file — throttled to milestones/warnings so it can never spam, even under a flood. Toggle with EchoGuardTripsToServerLog
- New: Lightweight performance mode — skips per-call bookkeeping for near-zero overhead on a busy server, at the cost of recent-calls context in a crash dump. Off by default
- Still never reads or modifies types.xml, globals.xml or any other vanilla file, and never deletes or alters items — it only adds the crash guard and writes diagnostics
- Existing v1.0 Config.json values are kept on upgrade — the two new options use their defaults until you add them by hand or regenerate the file
- If another mod also overrides HandleRemoteItemManipulation, load DHUB_Diagnostics LAST so its guard wins