菜单
Configure Object Builder (DayZ Tools' .p3d model editor) on a fresh machine. Imports the default registry settings shipped with DayZ Tools so Object Builder opens with sane window layouts and defaults instead of an empty config. One-time per machine; idempotent. Run before /dayz-launch-objectbuilder on a clean install.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | dayz-setup-objectbuilder |
| description | Configure Object Builder (DayZ Tools' .p3d model editor) on a fresh machine. Imports the default registry settings shipped with DayZ Tools so Object Builder opens with sane window layouts and defaults instead of an empty config. One-time per machine; idempotent. Run before /dayz-launch-objectbuilder on a clean install. |
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\.
One-time configuration of Object Builder. Bohemia ships a .reg file with sensible defaults (window layouts, panel positions, render flags) but doesn't auto-import it — without this step, Object Builder runs from a blank HKCU\Software\Bohemia Interactive\DayZ Tools\Object Builder tree and looks broken on first open.
Follow .claude/skills/_shared/dayz-conventions.md.
/dayz-preflight.find_dayz_tools() resolver.Bin\ObjectBuilder\ObjectBuilder.exeBin\ObjectBuilder\ObjectBuilder_defaultSettings.regHKCU\Software\Bohemia Interactive\DayZ Tools\Object Builder\CConfig for an existing config.reg import on the default .reg file.First time (or after a fresh DayZ Tools reinstall):
python "<skill-dir>\setup.py"
Force re-import (resets Object Builder to factory defaults — wipes any custom panel layout you've saved):
python "<skill-dir>\setup.py" --force
DayZ Object Builder setup
[OK] DayZ Tools: C:\Program Files (x86)\Steam\steamapps\common\DayZ Tools
[OK] ObjectBuilder.exe: ...\Bin\ObjectBuilder\ObjectBuilder.exe
[OK] Default settings file: ObjectBuilder_defaultSettings.reg
[OK] Buldozer.exe: ...\Bin\Buldozer\Buldozer.exe (used for 3D preview)
[INFO] Registry empty — importing defaults.
[INFO] Running: reg import ...\ObjectBuilder_defaultSettings.reg
[OK] Registry imported successfully.
[OK] Object Builder is configured. Launch with: /dayz-launch-objectbuilder
On an already-configured machine, output stops at [OK] Registry already configured and exits 0.
Object Builder is an old MFC-based Windows tool — its config lives entirely under HKEY_CURRENT_USER\Software\Bohemia Interactive\DayZ Tools\Object Builder. The shipped .reg file writes window/panel/toolbar defaults into that tree. It's HKCU-only, so:
--force re-import or by deleting the registry tree./dayz-preflight clean — the skill enforces it..reg writes to HKCU, not HKLM..reg file in DayZ Tools install — Steam will overwrite it on update. If you want custom defaults, save a layout from inside Object Builder; it persists in the same registry tree but in MainFrame-* subkeys you don't need to touch directly.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.