菜单
Programmatically add, update, or remove an entry in DayZ's types.xml. Upserts a `<type name="...">` block with the given attrs (nominal, min, lifetime, restock, cost, category, usage, value, tag). Auto-backs up the file before modifying. Idempotent — re-running with the same args is a no-op or a clean update.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | dayz-edit-types |
| description | Programmatically add, update, or remove an entry in DayZ's types.xml. Upserts a `<type name="...">` block with the given attrs (nominal, min, lifetime, restock, cost, category, usage, value, tag). Auto-backs up the file before modifying. Idempotent — re-running with the same args is a no-op or a clean update. |
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\.
Edit a DayZ Central Economy types.xml file programmatically — add a new spawn entry, update an existing one, or remove one. Backs up the file to types.xml.bak before any change.
Follow .claude/skills/_shared/dayz-conventions.md.
python "<skill-dir>\types_edit.py" <types.xml> <ClassName> [options]
python "<skill-dir>\types_edit.py" <types.xml> <ClassName> --remove
| Argument | Notes |
|---|---|
<types.xml> | Path to the types.xml file. Typically .server/<instance>/mission/db/types.xml. |
<ClassName> | The name attribute of the <type> block to upsert / remove. |
--remove | Remove the entry instead of upserting. Other field flags ignored. |
--nominal N | Target spawn count. Default for new entries: 1. |
--min N | Minimum spawn count. Default for new entries: 0. |
--lifetime S | Despawn timeout in seconds. Default for new entries: 3888000 (45 days). |
--restock S | Restock interval in seconds. Default for new entries: 0. |
--cost N | Spawn cost / weight. Default for new entries: 100. |
--category CAT | Sets <category name="CAT"/>. Single value (replaces any existing). |
--usage TAG | Add a <usage name="TAG"/>. Repeatable. Replaces all existing usages on the entry. |
--value TAG | Add a <value name="TAG"/>. Repeatable. Replaces all existing values on the entry. |
--tag TAG | Add a <tag name="TAG"/>. Repeatable. Replaces all existing tags on the entry. |
<types.xml>. Locate the <type name="<ClassName>"> block (or note its absence).<flags ... /> element.--remove): delete the block entirely. No-op if it didn't exist.<types.xml>.bak (overwriting any prior backup).<types.xml>./dayz-preflight returns non-zero.<types.xml> doesn't exist.<types.xml> isn't valid XML.Add new entry:
[OK] Added <type name="MyMod_Vest"> with 1/0 lifetime 3888000 cost 100
[OK] Backup: workspace\_server\missions\dayzOffline.chernarusplus\db\types.xml.bak
[OK] Wrote workspace\_server\missions\dayzOffline.chernarusplus\db\types.xml
Update existing:
[OK] Updated <type name="MyMod_Vest">: nominal 1 -> 5, lifetime 3888000 -> 7776000
[OK] Backup written
[OK] types.xml updated
Remove:
[OK] Removed <type name="MyMod_Vest">
[OK] types.xml updated
<flags> granular attributes (count_in_cargo, etc.) — there's no flag for that yet because most modders never edit them once defaults are set. Add flags as separate options later if real demand emerges.xml.etree.ElementTree; preserve the user's structure as much as possible..bak is cheap insurance; the user might paste in args wrong.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.