SID_CREATEACCOUNT
| Protocol | BNCS |
|---|---|
| Directions | Client → Server and Server → Client |
| Used by |     
|
Creates an account in the older logon. Same request as SID_CREATEACCOUNT2, but the reply is only success or failure.
Client → Server
| Type | Field | Notes | Confidence |
|---|---|---|---|
VOID |
Password hash (20 bytes) | X-SHA-1 of the lowercase password, hashed once. | ✅ Verified |
STRING |
Account name | Names longer than 15 characters are cut short. | ✅ Verified |
Server → Client
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Result | ✅ Verified |
Results
| Value | Meaning | Confidence |
|---|---|---|
0x00 | Unresolved. BNETDocs and the Atlas server say this means the account wasn't created. But an account created through Invigoration got 0x00 back with no problem. See the remarks. | 🛑 Unknown |
0x01 | Account created. | ✅ Verified |
Remarks
The result is reversed compared to SID_CREATEACCOUNT2. Here 0x01 means created. In SID_CREATEACCOUNT2, 0x00 does.
What 0x00 means is unresolved. BNETDocs and the Atlas server both describe 0x00 as failure. In practice, a 0x00 reply hasn't caused problems: accounts created through Invigoration, a bot that also works on official Battle.net, got 0x00 back and logged on normally.
Invigoration, like many bots, doesn't read the value. It treats any reply as "account created", disconnects and logs on. So the safest reading today:
- Clients should treat either value as "account created", then confirm by logging on.
- Servers should send
0x01for success, which every source agrees on.
A client that wants a reason for the failure can use SID_CREATEACCOUNT2, which any product may send.
Appears in
Sources and credits
- BNETDocs Atlas server (MIT): message handler used to cross-check the layout
- BNETDocs, Battle.net Chat Server Protocol Overview: written by Kyro, and edited 11 times since.
- BNETDocs, SID_CREATEACCOUNT (client to server): documented by the original BNETDocs contributors.
- BNETDocs, SID_CREATEACCOUNT (server to client): documented by the original BNETDocs contributors, 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.