Agentic-Z
An AI Agent Stack for DayZ Modding, with first-class support for Claude Code, Codex, and Gemini. Install it as a plugin (or clone the repo), point it at your mod project, and your AI shows up DayZ-fluent on day one — opinionated rules, specialist agents, slash-command skills, and a local RAG over the vanilla engine source.
Quick start
Install the plugin from any Claude Code session, then run the wizard:
Two install paths (plugin or clone), full prerequisites, and troubleshooting on the Install & Setup page.
DayZ Modding workflow
/dayz-init is the front door — one slash command takes you from empty repo to mod-loaded-in-DayZ. First run is a setup wizard (env check, intent prompts, plan, execute). Every run after that drops you into a mission-control hub for the cached project: build & launch, stop diag, tail server log, open Workbench / Object Builder, switch project, etc.
The wizard wraps the lower-level skills below. Power users can still call them directly when they want surgical control.
| Command | Purpose |
|---|---|
/dayz-init | Front door. Setup wizard on first run, mission-control hub thereafter |
/dayz-preflight | Verify environment (P:\ mounted, Tools installed, vanilla data extracted) |
/dayz-workdrive | Mount P:\ without opening DayZ Tools (auto-resolves work drive from settings.ini) |
/dayz-new-mod | Scaffold workspace/<ModName>/ + create P:\<ModName>\ junction |
/dayz-import-mod | Symlink an existing mod folder into the workspace + create the junction |
/dayz-build-pbo | Pack and deploy to P:\Mods\@<ModName>\Addons\<ModName>.pbo |
/dayz-add-server | Set up a test server instance under .server/<instance>/ |
/dayz-launch-test | Start local Diag server + client with the mod loaded |
/dayz-stop-test | Kill running DayZDiag_x64.exe processes |
/dayz-cot-bootstrap | One-shot Community-Online-Tools admin setup |
/dayz-pack-texture | PNG/TGA → .paa via ImageToPAA |
/dayz-edit-types | Programmatically edit a single <type> in types.xml |
/dayz-split-types | Split monolithic types.xml into 18 categorized files |
/dayz-search-download | Pull prebuilt vector index from GitHub releases (recommended fast path) |
/dayz-search-index | Build the semantic-search index over vanilla DayZ source yourself |
/dayz-search-wiki-index | Index the Bohemia community wiki into the same DB |
/dayz-clean-workspace | Remove DayZ scaffolds and their deployed artifacts |
Specialist tools (deep work): /dayz-p3d-audit, /dayz-p3d-debin, /dayz-particles.
MCP server: dayz-rag — exposes search_dayz_source, search_dayz_wiki, get_dayz_file, list_indexed_sources to every DayZ specialist agent. Backed by the index built via /dayz-search-index + /dayz-search-wiki-index.
Full walkthrough with prerequisites, env vars, and troubleshooting: dayz-modding.
DayZ specialist agents
Specialist agents live under .claude/agents/ and cover the major DayZ surfaces:
| Agent | Focus |
|---|---|
dayz-asset-specialist | .p3d / .paa / .rvmat and Workbench asset integration |
dayz-config-specialist | config.cpp, CfgPatches, CfgVehicles, CfgWeapons, hidden selections |
dayz-map-specialist | Terrain Builder, DayZ Editor, map objects, clutter, surfaces |
dayz-mod-debugger | Log/RPT/crash analysis, BattlEye diagnosis, performance profiling |
dayz-mod-reviewer | Audit workspace/<ModName>/ for convention compliance; routes findings to the right specialist |
dayz-object-builder | .p3d LODs, named selections, geometry, damage zones |
dayz-script-specialist | Enforce Script — modded classes, RPCs, replication, gameplay logic |
dayz-server-admin | types.xml, init.c, cfggameplay.json, server performance |
dayz-ui-specialist | .layout files, widget scripting, HUD/menu, UI theme/color |
dayz-workbench-specialist | Workbench plugin development (editor-time tooling) |
Plus agent-creator for scaffolding new agent definitions to the standard template.
Where to next
- Install & Setup — plugin or clone, full prerequisites, troubleshooting
- End-to-End Workflow — what
/dayz-initorchestrates, in depth - Rules & Conventions — L2 DayZ rules every agent obeys
- Architecture — how the L1 / L2 / L3 layers fit together (for power users and contributors)
- Contributing — how to send fixes back, propose new agents, or improve existing skills