0x54 SID_AUTH_ACCOUNTLOGONPROOF

ProtocolBNCS
DirectionsClient → Server and Server → Client
Used byWAR3W3XP

Finishes a Warcraft III logon: each side proves it knows the password without sending it.

Client → Server

TypeFieldNotesConfidence
UINT8 × 20 Client proof (M1) See NLS. ✅ Verified

Server → Client

TypeFieldNotesConfidence
UINT32 Status ✅ Verified
UINT8 × 20 Server proof (M2) ✅ Verified
STRING Error message Only with status 0x0F. Never send it otherwise; see below. ✅ Verified

Status

ValueMeaningConfidence
0x00Logged on.✅ Verified
0x02Wrong password.✅ Verified
0x06Account closed.⚠️ Single source
0x0ELogged on, but the account should have an email address. The client then sends SID_SETEMAIL.✅ Verified
0x0FCustom error. The message follows the proof and is shown to the player.⚠️ Single source

Remarks

A successful reply must be exactly 24 bytes: the status and the 20-byte proof, with nothing after them. BNETDocs lists a message string at the end, but a real Warcraft III client disconnects ("connection to Battle.net has been lost") if even one empty-string byte follows a success. Only the custom-error status 0x0F carries a string.

Wrong (client disconnects):  00 00 00 00  <M2, 20 bytes>  00
Right:                       00 00 00 00  <M2, 20 bytes>

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