duckietm/Nitro_Render_V3
1
0
Fork 0
mirror of https://github.com/duckietm/Nitro_Render_V3.git synced 2026-06-19 15:06:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #105 from simoleo89/docs/claude-md-packet-registration

Browse Source 
docs(CLAUDE): outgoing-composer registration + audit both packet maps
This commit is contained in:
DuckieTM
2026-06-15 07:27:25 +02:00
committed by GitHub
parent 494beb7d13 51c8d0468e
commit b8bc7135c2
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+12
View File
@@ -294,6 +294,18 @@ furni-editor's `applyLiveFurnitureNameUpdate`.
Parser under `messages/incoming/<area>` + `messages/parser/<area>` -> wire the
barrel chain (`<area>/index.ts` -> parent `index.ts` -> package `src/index.ts`).
**Adding an outgoing composer:** id in `OutgoingHeader.ts` -> register in
`NitroMessages.ts` (`this._composers.set(OutgoingHeader.X, XComposer)`) -> Composer
under `messages/outgoing/<area>` -> wire the barrel chain. An unregistered composer
makes `getComposerId()` return -1, logs "Unknown Composer", and the packet is
silently DROPPED — the request never reaches the server.
**A feature usually needs BOTH directions registered.** `NitroMessages` holds two
maps — `_events` (incoming) and `_composers` (outgoing). When a panel is "dead",
audit BOTH, not just `_events`: the inventory Prefixes panel was broken because
`UserPrefixesEvent` (7001, incoming) AND `RequestPrefixesComposer` (7011, outgoing)
were both defined+exported but never `set()` in `NitroMessages`.
**Gotchas:**
- A branch based on `origin/Dev` may NOT contain the furni-editor slice
(`FurniDataUpdatedEvent` / `applyLiveFurnitureNameUpdate`) — verify, don't assume.