0x3D SID_CREATEACCOUNT2

ProtocolBNCS
DirectionsClient → Server and Server → Client
Used bySTARSEXPD2DVD2XP

Creates an account using an X-SHA-1 password hash.

Client → Server

When the player creates a new account, usually after SID_LOGONRESPONSE2 reports that the account doesn't exist.

TypeFieldNotesConfidence
VOID Password hash (20 bytes) X-SHA-1 of the password converted to lowercase, hashed once. Verified
STRING Account name Names longer than 15 characters are cut short. Verified

Server → Client

TypeFieldNotesConfidence
UINT32 Status See the table below. Verified
STRING Suggested name May be empty. ⚠️ Single source

Status

ValueMeaningConfidence
0x00Account created. Verified
0x02Name contains characters that aren't allowed.⚠️ Single source
0x03Name contains a banned word.⚠️ Single source
0x04An account with that name already exists. Verified
0x06Name doesn't have enough letters or numbers.⚠️ Single source
0x07Name has punctuation characters next to each other.⚠️ Single source
0x08Name has too much punctuation.⚠️ Single source

Remarks

Lowercasing is the client's job. The server only ever sees the hash, never the password, so it can't fix a client that forgets to lowercase first. An account created that way can only be logged on to by clients that make the same mistake. Blizzard's own clients always lowercase.

Warcraft III doesn't use this message. It creates accounts with SID_AUTH_ACCOUNTCREATE.

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 John Leighow.
Edit on GitHub | Page history