DZDocs

A golden standard of reference material

DayZ modding knowledge is scattered across Discord messages, half-finished repos, YouTube videos, and private mentorships — and a lot of it is simply gatekept. This site exists to gather it into one place that outlives Discord scroll: a curated, cross-linked reference for the esoteric, hard-to-find side of modding the game.

It is not a Q&A queue and not an auto-generated API dump. It’s a deliberately built knowledge base — closer to good project docs than a wiki — covering the subsystems, pipelines, and gotchas people actually run into.

---

Find your discipline

Getting Started What this is, a modding overview, Workbench setup, and how to contribute.

Scripting EnScript basics and gotchas, common engine subsystems, native functions, and game structure.

Asset Work The modeling pipeline: P3D setup, proxies, selections, memory points, RVMATs, textures, and configs.

Tooling & Setup Packing, file patching, publishing, and a sane project workflow.

Contributing How to write docs, the style guide, and the pull-request process.

---

Built by the community

Correctness is the only bar

What matters is whether a page is right and actually gets you unstuck — not who, or what, wrote it. Modders come here for help, not provenance.

AI-drafted, community-verified

The first pass of this site was written with AI, and AI-assisted contributions are just as welcome. The community’s job is to check it, correct it, and deepen it — that’s where the trust comes from.

If you can write Markdown, you can contribute

The source is open. Fix a typo, flesh out a thin page, or write a whole guide — every page has an Edit link, and changes land through pull requests.

Build a staircase, don't pull the ladder up

A reaction to a cold, gatekeeping culture. The docs — and the way we collaborate on them — are meant to model the opposite.