メニュー
Pack a scaffolded mod from workspace/<ModName>/ into a .pbo at P:\Mods\@<ModName>\Addons\ via DayZ Tools AddonBuilder. Gates on /dayz-preflight, verifies the P:\<ModName>\ junction created by /dayz-new-mod, surfaces AddonBuilder output live. Default is binarized output; --clean wipes the target dir first.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit and fix DayZ .p3d model files for collision, action targeting, physics, animation, path, and structural issues. Runs py3d-based validation against known-working reference patterns. Also validates config.cpp and .rvmat files for path and property issues. Use this skill whenever: a DayZ mod object has no collision, actions don't appear, the player walks through placed objects, CCTObject raycasts miss, Geometry LOD seems ignored, a model was exported from Blender and doesn't work in-game, textures are missing, animations don't play, or the user says "review the p3d", "check the model", "audit collision", "why no actions", "flag/object has no collision", "audit the mod", "check paths", "validate the model". Also trigger when debugging any placed Inventory_Base item. This is the GO-TO skill for P3D and mod structure debugging.
Bootstrap Community-Online-Tools (COT) admin permissions on a DayZ test server in one shot. Auto-prepends @CF + @Community-Online-Tools to the mod chain, launches the server + client, waits for your character to spawn (detected when COT writes the per-player files), kills the session, grants you the `admin` role in your Players JSON, flips every ` 0` to ` 2` in your personal `Permissions/<id>.txt` file, then relaunches. Per-player grant only — `Roles/everyone.txt` is never touched. Requires /dayz-init + /dayz-add-server + /dayz-build-pbo first.
Pull the latest Agentic-Z template improvements (agents, skills, conventions, docs) from upstream into your clone, without touching your DayZ mod work in workspace/. Adds the upstream remote on first run, fetches, shows a changelog, then merges only template-managed paths. Re-runs sync-skills automatically. Refuses if your working tree is dirty unless --force is passed.
Wipe ALL template-managed artifacts across every domain so the repo is ready to push. Orchestrator — discovers and runs every domain's `<domain>-clean-workspace` skill in turn (currently just `dayz-clean-workspace`). Future domains plug in here automatically when they ship their own cleanup skill following the naming convention. Interactive confirmation by default; --yes skips it; --dry-run lists what each domain would clean.
Add missing DayZ mod scaffolding pieces (config.cpp stub, $PBOPREFIX$, workbench/dayz.gproj + DayZSetting.xml, README, .gitkeeps) into an EXISTING workspace/<ModName>/ folder. Idempotent - never overwrites files that are already present. Used by /dayz-import-mod after symlinking an external mod, but also runnable directly when you cloned a mod into workspace/ manually and want the standard skeleton filled in.
Set up a DayZ test server instance under .server/<instance>/. Copies the mission template from DayZ Server install if missing, creates per-instance serverDZ.cfg + Profiles/ (server -profiles=) and a top-level shared .server/!ClientDiagLogs/ (client -profiles=). Each instance is isolated on the server side so you can run multiple variants of the same map (chernarus, chernarus-hardcore, etc.) without cross-contamination. Refuses if the legacy workspace/_server/ layout exists (delete it manually; that layout is no longer supported). Required before /dayz-launch-test for a given instance. Use --refresh-mission to re-copy mission content after a DayZ update.
| name | dayz-build-pbo |
| description | Pack a scaffolded mod from workspace/<ModName>/ into a .pbo at P:\Mods\@<ModName>\Addons\ via DayZ Tools AddonBuilder. Gates on /dayz-preflight, verifies the P:\<ModName>\ junction created by /dayz-new-mod, surfaces AddonBuilder output live. Default is binarized output; --clean wipes the target dir first. |
Path note:
<skill-dir>in commands below is the absolute path of this skill's folder. When the agent loads this skill the harness exposes the skill's base directory; substitute it before running. Sibling skills are reached via<skill-dir>\..\dayz-X\.
Package a DayZ mod scaffold into a deployable .pbo and place it under P:\Mods\@<ModName>\Addons\ so the engine can load it. Gates on /dayz-preflight and the P:\<ModName>\ junction created by /dayz-new-mod. Reuses find_dayz_tools() from preflight per the L2 rule — no copy-paste path discovery.
Follow .claude/skills/_shared/dayz-conventions.md.
python "<skill-dir>\build.py" <ModName> [--clean]
| Argument | Required? | Notes |
|---|---|---|
<ModName> | yes | Must match an existing scaffold under workspace/<ModName>/ with the P:\<ModName>\ junction in place. |
--clean | no | Passes -clear to AddonBuilder, wiping P:\Mods\@<ModName>\Addons\ before building. Use after large refactors or when chasing a stale-asset bug. |
/dayz-preflight; halts on non-zero.workspace/<ModName>/ exists and contains config.cpp + $PBOPREFIX$.P:\<ModName>\ is a link pointing at workspace/<ModName>/ (created by /dayz-new-mod). If the link is missing or points elsewhere, halts with a clear message.AddonBuilder.exe via find_dayz_tools() (env var → registry → Steam paths). Halts if not found.P:\Mods\@<ModName>\Addons\ and P:\temp\<ModName>\ exist.AddonBuilder.exe P:\<ModName> P:\Mods\@<ModName>\Addons -prefix=<ModName> -temp=P:\temp\<ModName> [-clear]. AddonBuilder's stdout/stderr stream live so you see binarization progress and config errors as they happen.P:\Mods\@<ModName>\Addons\<ModName>.pbo exists and is newer than the build start.P:\Mods\@<ModName>\.agentic-z-scaffold (single line: the modname). dayz-clean-workspace requires this file before it will remove the deployed dir, so we never delete a deployed mod we didn't produce. Sits one level above Addons/ so --clean's -clear doesn't wipe it.P:\temp\<ModName>\ on success (kept on failure for debugging)./dayz-preflight returns non-zero.workspace/<ModName>/ is missing.workspace/<ModName>/config.cpp or $PBOPREFIX$ is missing.P:\<ModName>\ doesn't exist, isn't a link, or points somewhere other than workspace/<ModName>/. (Run /dayz-new-mod <ModName> to scaffold and create the junction.)AddonBuilder.exe isn't found (set DAYZ_TOOLS_PATH or install via Steam).Success:
DayZ preflight
[OK] P:\ is mounted
[OK] DayZ Tools found: C:\Program Files (x86)\Steam\steamapps\common\DayZ Tools
[OK] Vanilla data found: P:\dz
[OK] Workshop deploy folder exists: P:\Mods
Preflight complete.
[OK] workspace\MyMod\ found
[OK] P:\MyMod junction valid
[OK] AddonBuilder: C:\Program Files (x86)\Steam\steamapps\common\DayZ Tools\Bin\AddonBuilder\AddonBuilder.exe
[AddonBuilder] ... live output ...
[OK] Built: P:\Mods\@MyMod\Addons\MyMod.pbo (12,345 bytes)
[OK] Cleaned temp dir
Failure (any step):
[FAIL] <reason>
<hint or next step>
P:\Mods\@<ModName>\Addons\. The engine only loads from P:\Mods\ for in-development mods.P:\<ModName>\ junction here — that's /dayz-new-mod's job. If the junction is missing or wrong, fail and direct the user to scaffold first.find_dayz_tools from dayz-preflight/preflight.py.--no-binarize flag can be added later if iteration speed becomes a problem.)