Proposals / #796

Name the message id parameter of the unit change packet senders, checked against live captures

applied · by dtchitt · submitted 2026-11-02, applied 2026-11-02

Ghidra v1809 · 41c2819

Resubmit of #642 with the name the review asked for. bParam1 on the senders of 0x0C, 0x0D, 0x0E, 0x0F and 0x10 is packet byte [6]. Each client handler passes that byte as the first argument of HandleMessage, which hands it to PlayerMessage's nMessageType and ObjectMessage's eMessageType, so it is a unit message id and not a mode. Captures from a running game carry 0x13 here on monsters, which is above the highest monster mode, and 0x12 and 0x13 on the player.

Changes 5, applied together

1. Rename variable win 0x0053b430 Stack[0xc]

   namebParam1→nMessageType

2. Rename variable win 0x0053b470 Stack[0xc]

   namebParam1→nMessageType

3. Rename variable win 0x0053b4b0 Stack[0xc]

   namebParam1→nMessageType

4. Rename variable win 0x0053b570 Stack[0xc]

   namebParam1→nMessageType

5. Rename variable win 0x0053b520 Stack[0xc]

   namebParam1→nMessageType