0x01 MCP_STARTUP

ProtocolMCP
DirectionsClient → Server and Server → Client
Used byD2DVD2XP

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.

TypeFieldNotesConfidence
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

TypeFieldNotesConfidence
UINT32 Result ✅ Verified

Results

ValueMeaningConfidence
0x00Accepted. The client asks for its character list next.✅ Verified
0x02, 0x0A – 0x0DRealm unavailable: the realm doesn't recognise the logon.✅ Verified
0x7ECD key banned from realm play.⚠️ Single source
0x7FThe 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

This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.

Last edited September 16, 2026 by tagban.
Edit on GitHub | Page history | Edit with Discord