dayz-mod-devlisted
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# DayZ mod development: the entry point
This skill is the way into the Pack for mod work. It does not repeat the domain skills: it says which one
to read, carries the rules every mod task needs, and runs the loop that turns code into a mod that loads.
Use it **alongside** the domain skill, and alongside `dayz-mod-workflow` (how to implement and debug) once
code is being written.
Target: **DayZ 1.30 or later** (written against 1.30.164289). Builds before 1.30 are not covered; do not write
`#ifdef` branches for them unless the user asks for a mod that must still load on an older server. On a newer build,
re-check a fact against that build's sources before relying on it (next sections).
## The loop
1. **Scope.** A non-trivial feature first gets `dayz-feature-spec` (success criteria, forward contract).
2. **Write.** Read the domain skill (router below) and `dayz-mod-workflow`; look up every API before using it
(next section).
3. **Build.** `dayz-pbo-build`: validate, pack, sign.
4. **Boot it.** A PBO that builds is not a tested mod. Boot it on a local server, compare the script module counts
with a vanilla boot, read `script_*.log`. `dayz-test-ingame`.
5. **Verify in game** when the change is visible or player-driven: `dayz-test-ingame`, `dayz-mcp-verify`.
6. **Publish** only when the user says so: `dayz-pbo-build` (`references/workshop-publish.md` on Windows,
`references/dayzmake-linux.md` on Linux).
## Rules for every task
- **Look it up before you use it.** Ever