← ClaudeAtlas

dayz-mcp-verifylisted

Auto-test a DayZ mod in-game through dayz-mcp without keyboard or OCR: spawn a classname, orbit/capture, raycast collision, inspect placement/attachments/telemetry and emit PNG+JSON evidence. Compose with dayz-test-ingame; dayz_test_run/dayz_test_stop own the managed lifecycle, then this skill drives the bridge. Use for "auto-probar el mod", "verificar in-game con MCP", visual smoke/re-test, "comprobar que el .p3d carga/se ve/colisiona", automated spawn+capture+raycast, or the vehicle acceptance ladder (spawn→render→get-in→drive→wheel direction). Covers static objects, items/weapons, buildings without doors and vehicle placement/drivability. Player UI, door interaction, inventory use and firing remain manual. Also: ScriptConsoleTabRegistry, IsHeadless roboclient, UA_AM_INIT action inject.
willy92wins/DayZ-Modding-Knowledge-Pack · ★ 25 · AI & Automation · score 78
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# DayZ MCP verify — auto-test in-game vía tools MCP ## GATE 0 — ask WHO is driving, before touching anything (added 2026-08-07) (until 1.29: managed `dayz_test_run` / `dayz_test_stop` and Mode=all capture still hold.) (since 1.30: Diag Script Console tabs register via `ScriptConsoleTabRegistry`; `IsHeadless()` names roboclients; SP `PerformActionStart` no-ops while pending. Details: [dayz-1-30-mcp-verify.md](references/dayz-1-30-mcp-verify.md).) **Before the first `dayz-mcp` tool in a verification run, ask the user whether they are driving or the MCP is.** Neither is assumed. A single question per run, not per capture. Why it is a gate and not a preference: **with the user present, their manual cycle is faster and yields better results** — spawns with VPP in seconds and evaluates the whole scene at a glance, while MCP loop needs to position camera, capture, and chain tools. MCP wins when the user is NOT there: early morning, unattended run, or while attending another front. Furthermore, changing mode is not free midway (clean manual test requires relaunching without `@DayZ_MCP`), so the decision is made at the start of the cycle or paid twice. | Situation | Who drives | |---|---| | User present and available | **Them** (VPP + direct judgment) — MCP only if they ask | | User absent / unattended run | **MCP**, and report is left for them with evidence | | Doubt | **Ask.** Never assume | What does NOT change: MCP remains mandatory for what a human cannot measure by eye (tel