idb-bind

النجوم١٤

التفرعات٤

آخر تحديث٢٥ مايو ٢٠٢٦ في ٠٦:٥٦

Use when you need the v95 IDA database (the ida-pro/idalib MCP) to decompile/look up an original-client function but it may be unavailable — busy/locked by another IDA GUI or idalib session, or the MCP server is disconnected. Binds the database, or waits in the background until it frees and then continues. Owns the canonical procedure for binding the locked .i64 (free check, background wait, copy-to-temp fallback, alignment verification). Never prints or commits the local .i64 path.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

MujyKun

MujyKun/MapleClaude

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name

idb-bind

description

idb-bind

The authoritative v95 client reverse-engineering source is the live IDA Pro database exposed through the ida-pro/idalib MCP server. It has demangled names (CUIStat::Draw), StringPool resolution, struct offsets, and on-demand decompilation — strictly higher fidelity than the static text dumps that [disasm-lookup] reads.

Two distinct things can stop you from using it. Diagnose which one before acting:

MCP server disconnected — the mcp__plugin_ida-pro_idalib__* tools are not present at all (a ToolSearch for them returns no match). This is a Claude Code MCP connection, not a file lock. You cannot fix it from a tool — ask the user to (re)start the ida-pro/idalib MCP server, then retry. The watcher below does not help here.
Database busy / locked — the tools exist but idalib_open fails with "Failed to open database" because the IDA GUI or another idalib session holds an exclusive lock on the .i64. This is what the watcher and copy-to-temp trick are for.

The path (never commit it)

The .i64 path lives in the gitignored CLAUDE.local.md as IDA_IDB. Read it from there at runtime and pass it as an argument. Never hard-code it in a committed file, and never print it into a PR/commit/issue. Translated values (coordinates, offsets, formulas) may land in committed C#; the path and filenames may not.

Procedure

Confirm the MCP is connected. ToolSearch for select:mcp__plugin_ida-pro_idalib__idalib_open,mcp__plugin_ida-pro_idalib__decompile. If nothing matches → failure mode 1: tell the user to restart the idalib MCP server and stop here.
Check the lock. Run the watcher (path from CLAUDE.local.md):
```
& ".claude/skills/idb-bind/idb-watch.ps1" -Path "<IDA_IDB>" -Mode Check
```
IDB_STATUS=FREE (exit 0) → go to step 4. IDB_STATUS=LOCKED (exit 2) → step 3.
Wait in the background until it frees, then get re-invoked. Launch the watcher in Wait mode as a background Bash job (run_in_background: true); the harness re-invokes you when it exits, so keep working on other tasks meanwhile — do not poll:
```
& ".claude/skills/idb-bind/idb-watch.ps1" -Path "<IDA_IDB>" -Mode Wait -IntervalSeconds 20
```
It exits 0 (IDB_STATUS=FREE) the moment the other session releases the file. (-TimeoutSeconds N to bound the wait; 0 = forever.)
Bind. Prefer opening the real database when it is free:
```
idalib_open(input_path="<IDA_IDB>", session_id="v95", run_auto_analysis=false)
```
If it must run while the GUI still holds a shared (read-only) lock, fall back to the copy-to-temp trick — copy the .i64 to $env:TEMP\v95_<purpose>.i64 and open the copy (the legacy .idb will not load in idalib 9.x; always use .i64).
Verify alignment before trusting any address. decompile 0x602140 must show result->left = 66 * (nIdx % 5) + 23 (CUIChannelSelect::GetRect). If it does not, the addresses are stale — re-derive symbols by name via lookup_funcs / list_funcs rather than by hard-coded address.
When done, leave the session open for follow-ups, or idalib_close if you started it solely for a one-off lookup and the user may want the GUI back.

Privacy

Same rules as [disasm-lookup]: never paste the .i64 path, filenames, or any private project name into committed files, PR bodies, commits, or issues. Run git diff before committing and abort if any path fragment appears.

Known follow-ups that need this skill

Stat detail window (StatDetailInfo.cs): the live IDB dropped mid-port, so the detail rows are best-effort. Revisit CUIStatDetail::Draw (≈0x8625f0) for the exact DrawText (x,y) per row and CUIStatDetail::GetCriticalProp (≈0x861bf0) for the crit formula. See [[stat-window-cuistat]].

المزيد من هذا المستودع

نفس المستودع

authentic-ui-rebuild

MujyKun/MapleClaude

Use when the user wants a placeholder/custom UI overlay replaced with the authentic v95 client version sourced from the WZ assets + IDA database — phrases like "not the custom overlay", "not the placeholder", "we have a custom overlay right now, but it's not authentic", "authentic v95", "authentic [stat/inventory/equip/chat/skill/quest/family/system menu/NPC dialog/channel select/character profile/key config/buddy/party/guild/alliance/blacklist] window", "rebuild [UI] 1:1 from the IDB", "look up CUI[X] and rebuild it 1:1", "fix [UI screen] to match the IDB", "look into the proper IDB implementation", "use the natural UI and proper icons", "should reuse the [UIWindow*.img/...]", "look into the IDB for the proper [UI]". Walks the WZ subtree identification → `CUI*` class decompile via `ida-lookup` → coordinate extraction → C# rebuild loop. For full-screen rebuilds it escalates to the `v95-ui-rebuilder` agent; for origin extraction to the `ui-origin-finder` agent. Triggers ONLY for UI that exists in the original

2026-05-2614

autonomous-phase

MujyKun/MapleClaude

Use when the user explicitly hands off the phase queue and wants Claude to pick the next item from `docs/roadmap.md` and run it to completion, then loop — phrases like "continue with the next phase", "do the next phase", "do the next phase from the readme", "continue with the phases", "continue with the phases to be implemented from the readme", "auto-implement the rest of the phases", "on auto mode dont ask me about anything", "im going to bed", "keep going on the roadmap", "keep going", "auto-run the roadmap". Reads `docs/roadmap.md` for the next un-shipped phase, plans, implements (delegating to `authentic-ui-rebuild`, `ingame-feature`, `wz-audio-bind`, `wz-subsystem-research`, packet skills as needed), tests, and ships via `ship-pr` — which still asks for per-commit approval per CLAUDE.md (no blanket auto-commit). Loops to the next phase until interrupted, roadmap exhausted, or three consecutive failures. Triggers NOT for a single mid-flight task (just keep working) and NOT for short replies like "continu

2026-05-2614

ida-lookup

MujyKun/MapleClaude

Use when the user wants a single v95 client class, function, struct, or constant looked up — phrases like "look into the IDB", "look into the IDB for X", "reference the IDB", "look up CXxx", "look in the idb", "check the IDB for", "investigate it with the idb", "look into how the v95 client does X", "look into the proper IDB implementation", "find the function that does Y", "decompile CUI[X]", "the IDB for the proper [Y]", or anywhere the user implies "go ask the IDA database what the real client does here". Drives the live `ida-pro/idalib` MCP via `idb-bind`, runs the standard lookup_funcs → decompile → xrefs recipe, and surfaces a paraphrased answer with translated constants / coordinates / formulas — never the .i64 path, never raw decompiled C++ blocks pasted into committed files. Triggers ONLY for single-symbol queries; NOT for full WZ subsystem sweeps (use `wz-subsystem-research`) and NOT for full UI screen rebuilds (use `authentic-ui-rebuild`, which itself calls into this skill).

2026-05-2614

ingame-feature

MujyKun/MapleClaude

Use when the user wants a player or world feature implemented end-to-end (packets + animation + WZ assets + state) — phrases like "implement [combat / death / drop / pickup / NPC click / emotion / facial expression / damage / attack / knockback / tombstone / revive / collision / aggro / mob movement / loot / level up]", "research how a player dies", "ensure when the player's HP reaches 0 he dies", "we need to be able to hit mobs", "mobs should X when Y", "player should X when Y", "when [event] happens, [response]", "mob death animation", "drop to the ground", "pick it up should fly into the character", "play the mob's sounds when hit", "introduce facial expressions", "we want emotions when F1-F7 is pressed", or similar full-feature requests that cut across the packet layer + the IDB animation logic + the WZ assets + the runtime state. Coordinates calls into `client-packet-author`, `server-packet-mirror`, `ida-lookup`, `wz-audio-bind`, and `wz-subsystem-research`. Triggers NOT for UI windows alone (`authentic-

2026-05-2614

layering

MujyKun/MapleClaude

Use when the user reports — or wants to enforce — that an NPC, mob, character, or drop is rendering on the wrong z-layer relative to a map's tiles/objs/trees — phrases like "layering", "z-index", "z-order", "z order", "render order", "the player goes behind/in front of [the tree/the object/the platform]", "draw order is wrong", "entity is in the wrong layer", "obj covers the player", "tree is behind the mob", "foothold layer", "make NPCs/mobs/characters layer-aware", "honor the v95 layer model", "draw on the correct layer", "behind the [obj/wall/decoration]". Owns the 8-layer + per-layer-z draw model documented in `docs/map-wz.md`, the foothold→entity-layer mapping, and the canonical per-layer entity draw order used by `GameStage.DrawEntitiesAtLayer`. Triggers NOT for parallax-back sort order (that's the `back/front` flag inside `FieldScene.DrawBacks`) and NOT for shader depth-buffer questions (we are 2D — no real depth buffer).

2026-05-2614

layout-tune

MujyKun/MapleClaude

Use when the user wants to nudge an already-rendered UI element by a small amount — phrases like "move it [N]px [direction]", "move it 3px down", "lower it like 3px", "move it 2 pixels to the right, 4 down", "icon too high", "icon too low", "the [element] is wrong [direction]", "needs to be a bit higher", "needs to be a bit lower", "nudge [element]", "position is wrong", "the position is off", "needs to be [N]px [direction]". Redirects the user to the live debug overlay (`watch.ps1` + `MAPLECLAUDE_DEBUG=1`) for tuning without rebuild, and only when overlay tuning isn't possible, makes the smallest constant-edit in the right Stage/UI file. Triggers ONLY for nudging an existing element; NOT for adding new UI (use `authentic-ui-rebuild`) and NOT for reading WZ origins from scratch (use `ida-lookup` or the `ui-origin-finder` agent).

2026-05-2614

name

idb-bind

description

idb-bind

Two distinct things can stop you from using it. Diagnose which one before acting:

MCP server disconnected — the mcp__plugin_ida-pro_idalib__* tools are not present at all (a ToolSearch for them returns no match). This is a Claude Code MCP connection, not a file lock. You cannot fix it from a tool — ask the user to (re)start the ida-pro/idalib MCP server, then retry. The watcher below does not help here.
Database busy / locked — the tools exist but idalib_open fails with "Failed to open database" because the IDA GUI or another idalib session holds an exclusive lock on the .i64. This is what the watcher and copy-to-temp trick are for.

The path (never commit it)

Procedure

Confirm the MCP is connected. ToolSearch for select:mcp__plugin_ida-pro_idalib__idalib_open,mcp__plugin_ida-pro_idalib__decompile. If nothing matches → failure mode 1: tell the user to restart the idalib MCP server and stop here.
Check the lock. Run the watcher (path from CLAUDE.local.md):
```
& ".claude/skills/idb-bind/idb-watch.ps1" -Path "<IDA_IDB>" -Mode Check
```
IDB_STATUS=FREE (exit 0) → go to step 4. IDB_STATUS=LOCKED (exit 2) → step 3.
Wait in the background until it frees, then get re-invoked. Launch the watcher in Wait mode as a background Bash job (run_in_background: true); the harness re-invokes you when it exits, so keep working on other tasks meanwhile — do not poll:
```
& ".claude/skills/idb-bind/idb-watch.ps1" -Path "<IDA_IDB>" -Mode Wait -IntervalSeconds 20
```
It exits 0 (IDB_STATUS=FREE) the moment the other session releases the file. (-TimeoutSeconds N to bound the wait; 0 = forever.)
Bind. Prefer opening the real database when it is free:
```
idalib_open(input_path="<IDA_IDB>", session_id="v95", run_auto_analysis=false)
```
If it must run while the GUI still holds a shared (read-only) lock, fall back to the copy-to-temp trick — copy the .i64 to $env:TEMP\v95_<purpose>.i64 and open the copy (the legacy .idb will not load in idalib 9.x; always use .i64).
Verify alignment before trusting any address. decompile 0x602140 must show result->left = 66 * (nIdx % 5) + 23 (CUIChannelSelect::GetRect). If it does not, the addresses are stale — re-derive symbols by name via lookup_funcs / list_funcs rather than by hard-coded address.
When done, leave the session open for follow-ups, or idalib_close if you started it solely for a one-off lookup and the user may want the GUI back.

Privacy

Known follow-ups that need this skill

Stat detail window (StatDetailInfo.cs): the live IDB dropped mid-port, so the detail rows are best-effort. Revisit CUIStatDetail::Draw (≈0x8625f0) for the exact DrawText (x,y) per row and CUIStatDetail::GetCriticalProp (≈0x861bf0) for the crit formula. See [[stat-window-cuistat]].