client-packet-author

Stars14

Forks4

UpdatedMay 21, 2026 at 04:55

Use when authoring an outgoing client→server packet in MapleClaude.Net. Triggers on phrases like "send a packet", "client request for X", "add a C→S packet", or any reference to an InHeader entry. Locates the upstream Kinoko InHeader entry and the matching server-side handler, then generates a C# encoder in the calling Stage that writes fields in the order the server reads them.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

MujyKun

MujyKun/MapleClaude

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	client-packet-author
description	Use when authoring an outgoing client→server packet in MapleClaude.Net. Triggers on phrases like "send a packet", "client request for X", "add a C→S packet", or any reference to an InHeader entry. Locates the upstream Kinoko InHeader entry and the matching server-side handler, then generates a C# encoder in the calling Stage that writes fields in the order the server reads them.

client-packet-author

When you're writing a packet the client sends to the server, walk through these steps:

1. Identify the opcode

Look in upstream Kinoko src/main/java/kinoko/server/header/InHeader.java (repo: https://github.com/iw2d/kinoko) for the named opcode. Record the numeric value. Confirm it's in src/MapleClaude.Net/Packet/OpCodes.cs (regenerate via tools/gen-opcodes if it isn't).

2. Find the server-side reader

Search Kinoko's src/main/java/kinoko/handler/ tree for the matching @Handler(InHeader.<YourOpcode>) annotation. The method body shows the read order — that's the order you must write in.

Java read	C# write
`inPacket.decodeByte()`	`WriteByte(x)`
`inPacket.decodeShort()`	`WriteShort(x)`
`inPacket.decodeInt()`	`WriteInt(x)`
`inPacket.decodeLong()`	`WriteLong(x)`
`inPacket.decodeString()`	`WriteString(s)` (length-prefixed `short`)
`inPacket.decodeArray(n)`	`WriteBytes(buf)` (length is contextual)

3. Write the packet

Build the OutPacket in the calling Stage or in a static Packets.Build* helper (preferred when the packet is reused):

public static OutPacket BuildExample(int charId, ReadOnlySpan<byte> machineId)
{
    var p = OutPacket.Of(InOp.Example);
    p.WriteInt(charId);
    p.WriteBytes(machineId);
    p.WriteByte(0);
    return p;
}

Call session.Send(BuildExample(...)).

4. Verify before committing

Run any unit tests in MapleClaude.Net.Tests that exercise the new packet.
If feasible, smoke-test against a running Kinoko server and watch the server logs for a parse error on the new opcode.
Confirm no local paths or private project names in the file.
Propose the commit to the user; wait for approval.

Hand-off

If the C→S packet is part of a multi-step flow (e.g. login → world list → char select), launch the kinoko-protocol-mirror agent to coordinate the whole sequence.

More from this repository

same repository

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	client-packet-author
description	Use when authoring an outgoing client→server packet in MapleClaude.Net. Triggers on phrases like "send a packet", "client request for X", "add a C→S packet", or any reference to an InHeader entry. Locates the upstream Kinoko InHeader entry and the matching server-side handler, then generates a C# encoder in the calling Stage that writes fields in the order the server reads them.

client-packet-author

When you're writing a packet the client sends to the server, walk through these steps:

1. Identify the opcode

2. Find the server-side reader

Search Kinoko's src/main/java/kinoko/handler/ tree for the matching @Handler(InHeader.<YourOpcode>) annotation. The method body shows the read order — that's the order you must write in.

Java read	C# write
`inPacket.decodeByte()`	`WriteByte(x)`
`inPacket.decodeShort()`	`WriteShort(x)`
`inPacket.decodeInt()`	`WriteInt(x)`
`inPacket.decodeLong()`	`WriteLong(x)`
`inPacket.decodeString()`	`WriteString(s)` (length-prefixed `short`)
`inPacket.decodeArray(n)`	`WriteBytes(buf)` (length is contextual)

3. Write the packet

Build the OutPacket in the calling Stage or in a static Packets.Build* helper (preferred when the packet is reused):

public static OutPacket BuildExample(int charId, ReadOnlySpan<byte> machineId)
{
    var p = OutPacket.Of(InOp.Example);
    p.WriteInt(charId);
    p.WriteBytes(machineId);
    p.WriteByte(0);
    return p;
}

Call session.Send(BuildExample(...)).

4. Verify before committing

Run any unit tests in MapleClaude.Net.Tests that exercise the new packet.
If feasible, smoke-test against a running Kinoko server and watch the server logs for a parse error on the new opcode.
Confirm no local paths or private project names in the file.
Propose the commit to the user; wait for approval.

Hand-off

If the C→S packet is part of a multi-step flow (e.g. login → world list → char select), launch the kinoko-protocol-mirror agent to coordinate the whole sequence.