MCP_CHARLIST2
| Protocol | MCP |
|---|---|
| Directions | Client → Server and Server → Client |
| Used by |
Lists the account's characters for the character-select screen, with when each one expires.
Client → Server
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Characters to list | The official client asks for 8. | ✅ Verified |
Server → Client
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT16 |
Characters requested | ✅ Verified | |
UINT32 |
Characters on the account | ✅ Verified | |
UINT16 |
Characters returned | ✅ Verified | |
| For each character returned | |||
UINT32 |
Expires | Seconds since January 1, 1970. 0xFFFFFFFF never expires. |
✅ Verified |
STRING |
Name | ✅ Verified | |
STRING |
Portrait | The character's statstring, without the product code and name that chat statstrings start with. | ✅ Verified |
Remarks
A classic Diablo II client can't play Lord of Destruction characters, so a realm should leave them out of the list for that client. Lord of Destruction sees both kinds.
When the player returns to character select from chat, the client asks again on the realm connection it already has open.
Appears in
Sources and credits
- Command Center: bnetccd realm server: tested with a real Diablo II: Lord of Destruction 1.14d client
- BNETDocs, MCP_CHARLIST2 (client to server): documented by the original BNETDocs contributors.
- BNETDocs, MCP_CHARLIST2 (server to client): documented by LordVader, and edited 2 times since.
This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.