lake-dayz
English · 한국어
An MCP server that pre-flights DayZ Enforce mods — compiler-style pass/fail checks that catch boot-crashing mistakes (deprecated/commented-out classes, wrong config classes, bad modded/overrides) before you pack a PBO.
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
English · 한국어
An MCP server that pre-flights DayZ Enforce mods — compiler-style pass/fail checks that catch boot-crashing mistakes (deprecated/commented-out classes, wrong config classes, bad modded/overrides) before you pack a PBO.
An MCP server that pre-flights DayZ Enforce mods — compiler-style pass/fail checks that catch boot-crashing mistakes (deprecated/commented-out classes, wrong config classes, bad modded/overrides) before you pack a PBO.
🎮 Built while making dayzlake.online — a DayZ territory-control (점령전) server.
DayZ Enforce has no offline compile check — a broken mod only reveals its error when you launch the game.
A real incident:
modded class ActionFishing { override string GetText() { ... } }
→ on boot: Can't compile World script module! Unknown type 'ActionFishing' → the whole game UI dies.
The cause was not "ActionFishing was removed." DayZ leaves deprecated code commented out instead of deleting it — lines 1–52 of actionfishing.c are one /* ... */ block, and the live class is ActionFishingNew. A raw grep "class ActionFishing" catches the dead code inside the comment → "oh, the code exists!" → modding it = dead boot.
Lesson: "defined ≠ alive." Is it commented out? Defined but unused? You have to check the usage, not just the name.
check_modded("ActionFishing") → ㄴㄴ (no) in one line. That's why this exists.
Every tool is verdict/evidence first — the first line is the conclusion (ㅇㅇ = pass / ㄴㄴ = no).
index_local.py ─ P:\scripts + (optional) your mod source, comment-aware parse (commented_out flag) ─┐
index_config.py ─ P:\DZ\**\config.cpp → item→CfgXxx mapping ├→ data/dayz_scripts.db
DayZ-script Doxygen reference ─ members + signatures + References/Referenced-by ─┘ (pre-built into the DB)
server.py ─ serves the tools from that DB (stdio MCP)
commented_out flag — whether code is commented-out dead code, plus file:line. P:\ is the authority source, kept in sync with the game.The DB (data/dayz_scripts.db) ships with the repo, so it works right after cloning. You can query/validate without DayZ or DayZ Tools installed; you only need DayZ Tools' extracted P:\ to rebuild the DB for a new game version.
cd <repo>
python -m venv .venv
.venv\Scripts\python.exe -m pip install -r requirements.txt
claude mcp add -s user lake-dayz ^
<repo>\.venv\Scripts\python.exe ^
<repo>\server.py
docker build -t lake-dayz .
claude mcp add -s user lake-dayz -- ^
docker run -i --rm ^
-v "<repo>\data:/data:ro" ^
-v "<your-mod-source-root>:/modset:ro" ^
-v "<dir-with-enforce-script-guide.md>:/docs:ro" ^
-v "<your-addons-dir>:/addons:ro" ^
lake-dayz
check_pboinspects packed PBOs, so mount the folder your PBOs land in (/addons) too — otherwise it can only hand back the command for you to run. Running natively (option A) needs no mounts: it sees the host directly and probes DayZ Tools /P:itself.
Mounts are read-only, so rebuilding the DB on the host is picked up automatically.
Env vars: DAYZ_MCP_DB / DAYZ_MCP_MODSET / DAYZ_MCP_GUIDE.
enforce_docservesenforce-script-guide.md— put it at the repo root (orDAYZ_MCP_GUIDE) for native, or the/docsmount for Docker.
.venv\Scripts\python.exe index_local.py REM re-index P:\scripts (+ modset if DAYZ_MCP_MODSET is set)
.venv\Scripts\python.exe index_config.py REM re-index P:\DZ config
P:\ with DayZ Tools (P:\ is the authority source).index_local.py — almost always just this (the core data for modded-class verdicts).DAYZ_MCP_MODSET to your mod source root (e.g. @YourMod\source); each subfolder = one mod.Call them in workflow order. Each step stops a different kind of death.
Any code with
modded class X/class X : Y/extends Ymust passcheck_modded(X)+enforce_lint(file)before packing. Item config overrides:check_config. Whole module:check_addon.
If the verdict is ㄴㄴ (no), don't pack.
One step stays human: start the server and read profiles/script.log — that's the only place compile results show up. check_pbo hands you that request line too.
This started while building dayzlake.online, a DayZ territory-control server. I kept getting bitten by Enforce mistakes that only blow up after you launch the game — so I got fed up and built this MCP to catch them before packing. Hoping DayZ keeps growing, the Korean community included. Drop by the server sometime. 🇰🇷
server.py, indexers, etc.) — GPLv3, see LICENSE.data/dayz_scripts.db is derived from DayZ © Bohemia Interactive and remains subject to the DayZ Public License – No Derivatives (DPL-ND): https://www.bohemia.net/community/licenses/dayz-public-license-no-derivatives-dpl-ndAn MCP server that pre-flights DayZ Enforce mods — compiler-style pass/fail checks that catch boot-crashing mistakes (deprecated/commented-out classes, wrong config classes, bad modded/overrides) befo
ภาพรวม
An MCP server that pre-flights DayZ Enforce mods — compiler-style pass/fail checks that catch boot-crashing mistakes (deprecated/commented-out classes, wrong config classes, bad modded/overrides) before you pack a PBO.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Lake Dayz ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 An MCP server that pre-flights DayZ Enforce mods — compiler-style pass/fail checks that catch boot-crashing mistakes (deprecated/commented-out classes, wrong config classes, bad modded/overrides) before you pack a PBO.