← ClaudeAtlas

dayz-preflightlisted

Use when: P:\ not mounted, DayZ Tools missing, workshop folder, vanilla data unpacked, before building/packing, AddonBuilder path, DayZDiag locatable. Read-only env check. Not launch/test: dayz-test-ingame. Also: cacheP3D, unpacked -mod folder, Workbench 1.30.
willy92wins/DayZ-Modding-Knowledge-Pack · ★ 25 · AI & Automation · score 78
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# /dayz-preflight Verify the DayZ modding environment before doing any DayZ work. Halts with a clear error if `P:\` is not mounted (per `_shared/dayz-conventions.md`); warns on optional checks so the user can decide whether to proceed. **Read-only.** Preflight inspects state and reports. It never mounts drives, creates junctions, or otherwise mutates the filesystem — fixes belong to dedicated setup skills. **Non-redundancy note:** If the flow goes through dayz-test-ingame, its `dayz-test.ps1` preflight already checks AND auto-fixes these (junction creation etc.) — this skill is the read-only/warn variant. Follow `_shared/dayz-conventions.md`. ## What it checks | # | Check | Severity | |---|---|---| | 1 | `P:\` drive is mounted | **hard fail** — exit 1 | | 2 | DayZ Tools installed (AddonBuilder.exe locatable) | warn | | 3 | Vanilla DayZ data unpacked under `P:\` | warn | | 4 | `P:\Mods\` is a directory junction to `<DayZ install>\!Workshop\` (not a regular folder, not missing, not dangling) | warn — build-pbo hard-fails on the same condition | | 5 | `DayZDiag_x64.exe` locatable (required for `-filePatching` iteration; retail exes block past loading) | warn | Exit code 0 = ready (or warnings only). Non-zero = hard environment issue, named in stderr. ## How paths are resolved Paths are not blindly hard-coded. Resolution order, first hit wins: | What | Order | |---|---| | **DayZ Tools install root** | 1. `DAYZ_TOOLS_PATH` env var → 2. Windows registry (`HKLM\SOFTWARE\WO