STransferServer (0x03)
Previous: SLoginCheck | Server action index | Next: SUserPosition
STransferServer is server-to-client action 0x03 in the 4.21 protocol.
Direction: server to client
Encrypted: No. See Sequence and XOR Transformation.
Payload offsets begin with the first byte after the action. The frame marker, frame length, action, sequence, and trailing zero are excluded.
Payload format
| Offset | Width | Field | Established meaning |
|---|---|---|---|
0x00 | payload_length | unknown_00 | Payload bytes whose field boundaries are not yet mapped. |
Handler functions
| Function address | Current IDA name | Role |
|---|---|---|
Darkages.exe:0x0045F780 | ui_main_menu_handle_server_packet | Accepts the action in the main-menu packet handler. |
Darkages.exe:0x00468A90 | ui_map_dispatch_server_packet | Accepts and dispatches the action in MapPane. |
Handler notes
Darkages.exe:0x0045F780 ui_main_menu_handle_server_packet and Darkages.exe:0x00468A90 ui_map_dispatch_server_packet. The MapPane branch calls transfer-server processing and can send kClientTransferServer. XOR bypass.
Schema status
The 4.21 client accepts this action in the listed functions. Payload field division remains a placeholder until its readers and client-side effects are traced end to end.