SID_CLIENTID
| Protocol | BNCS |
|---|---|
| Directions | Client → Server and Server → Client |
| Used by |     
|
| Status | Historical. Only the older logon uses it, and the registration fields are no longer used. |
The client's first message in the oldest logon: registration numbers and the computer's LAN names.
Client → Server
Sent right after the protocol byte by StarCraft Shareware and StarCraft Japanese. Diablo and Warcraft II send SID_CLIENTID2 instead.
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Registration version | No longer used. May be 0. |
✅ Verified |
UINT32 |
Registration authority | No longer used. May be 0. |
✅ Verified |
UINT32 |
Account number | No longer used. May be 0. |
✅ Verified |
UINT32 |
Registration token | No longer used. May be 0. |
✅ Verified |
STRING |
LAN computer name | The Windows computer name. | ✅ Verified |
STRING |
LAN user name | The name of the Windows user who is logged in. | ✅ Verified |
Server → Client
Sent in reply to SID_CLIENTID or SID_CLIENTID2, before SID_LOGONCHALLENGE or SID_LOGONCHALLENGEEX.
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Registration version | 0. |
✅ Verified |
UINT32 |
Registration authority | 0. |
✅ Verified |
UINT32 |
Account number | 0. |
✅ Verified |
UINT32 |
Registration token | 0. |
✅ Verified |
Remarks
Early Battle.net used these fields to hand out and check registration numbers for each copy of the game. The server once replied with new numbers when the client's were invalid. Today every registration field is zero in both directions, and only the two LAN names still carry data.
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_CLIENTID (client to server): documented by the original BNETDocs contributors, and edited 4 times since.
- BNETDocs, SID_CLIENTID (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.