0x3E SID_LOGONREALMEX

ProtocolBNCS
DirectionsClient → Server and Server → Client
Used byD2DVD2XP

Logs on to a Diablo II realm. The reply tells the client where the realm is and what to show it.

Client → Server

TypeFieldNotesConfidence
UINT32 Client token ✅ Verified
VOID Realm password proof (20 bytes) The official client always uses the password password, hashed like an account logon, so it proves nothing. ✅ Verified
STRING Realm name ✅ Verified

Server → Client

TypeFieldNotesConfidence
UINT32 Cookie Echoes the client token. ✅ Verified
UINT32 Status 0 on success. ✅ Verified
UINT32 × 2 Chunk 1 Opaque to the client; it passes them on to the realm. ✅ Verified
UINT8 × 4 Realm IP address Network byte order. ✅ Verified
UINT16 Realm port Big-endian, followed by two zero bytes. Not a 32-bit value. ✅ Verified
UINT16 Unused 0. ✅ Verified
UINT32 × 12 Chunk 2 Opaque to the client; it passes them on to the realm. ✅ Verified
STRING Unique name ✅ Verified

Failure

ValueMeaningConfidence
8 bytes or fewerAny reply this short is a failure: just the cookie and a status such as 0x80000001, realm unavailable.✅ Verified

Remarks

The client copies the cookie, status and both chunks into MCP_STARTUP on the realm connection, so the realm can recognise the logon. BNETDocs also records a different reply layout seen from official servers around version 1.14d. The layout above is the one a real 1.14d client accepts.

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