DayZDB

DayZDB is a solo fan project. One person parses the configs, builds the pipelines, designs the pages, and keeps the catalogue current. There is no studio, no publisher brief, and no corporate roadmap — just a long-running effort to turn DayZ’s opaque data into something you can actually read.

The goal is simple and stubborn: DayZDB should be the most complete DayZ database on the web. Not a highlight reel of popular guns. Not a tip dump. A full listing of what the game actually contains — items, systems, maps, and the links between them.

Weapons and ammunition with magazines, attachments, recoil, loudness, and ballistic curves. Clothing with insulation and protection. Food with nutrition. Medical gear, tools, craftables, vehicles, infected archetypes, animals, AI templates, territories, player spawns, loot groups, CE types, seasonal packs, diseases, forage, surfaces, weather, and gameplay globals.

Detail pages stitch those pieces together: what chambers what, where an item can spawn, which buildings stock it, which recipes consume it, and which scripts govern the systems around it. The catalogue is meant to feel exhaustive on purpose — a working database, not a brochure.

DayZDB is generated from local game files: config.cpp class trees, script constants, types.xml, spawnable types, mapgroupproto placements, territories, events, weather, and the rest of the vanilla data stack. Pages carry provenance so you can see where a number came from.

That approach is slower than copying a wiki table, and more honest. When the game updates, the extract-and-build pipeline is how the database catches up — class by class, map by map — instead of waiting on tribal knowledge to drift into accuracy.

Email the DayZDB operator at dev@dayzdb.dev, or use the Contact page.