MCP_STARTUP
| Protocol | MCP |
|---|---|
| Directions | Client → Server and Server → Client |
| Used by |
The first message on the realm connection. Hands the realm the logon data Battle.net issued, so it knows who the client is.
Client → Server
Right after the 0x01 protocol byte on the realm connection.
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Cookie | Copied from the SID_LOGONREALMEX reply. |
✅ Verified |
UINT32 |
Status | Copied from the SID_LOGONREALMEX reply. |
✅ Verified |
UINT32 × 2 |
Chunk 1 | Copied from the SID_LOGONREALMEX reply. |
✅ Verified |
UINT32 × 12 |
Chunk 2 | Copied from the SID_LOGONREALMEX reply. |
✅ Verified |
STRING |
Unique name | The account's name on Battle.net. | ✅ Verified |
Server → Client
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Result | ✅ Verified |
Results
| Value | Meaning | Confidence |
|---|---|---|
0x00 | Accepted. The client asks for its character list next. | ✅ Verified |
0x02, 0x0A – 0x0D | Realm unavailable: the realm doesn't recognise the logon. | ✅ Verified |
0x7E | CD key banned from realm play. | ⚠️ Single source |
0x7F | The address is temporarily banned from the realm. | ⚠️ Single source |
Remarks
The client doesn't interpret the sixteen 32-bit values. It copies them exactly as SID_LOGONREALMEX delivered them, so a realm that shares a process with the Battle.net server can use them to carry any handle it likes.
Appears in
Sources and credits
- Command Center: bnetccd realm server: tested with a real Diablo II: Lord of Destruction 1.14d client
- BNETDocs, MCP_STARTUP (client to server): documented by RealityRipple, and edited 1 times since.
- BNETDocs, MCP_STARTUP (server to client): documented by LordVader, and edited 1 times since.
This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.