SID_CLIENTID2
| Protocol | BNCS |
|---|---|
| Directions | Client → Server |
| Used by |   
|
| Status | Historical. Only the older logon uses it. |
A newer form of SID_CLIENTID, sent first by Diablo and Warcraft II.
Client → Server
Right after the protocol byte, followed immediately by SID_LOCALEINFO and SID_STARTVERSIONING.
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Server version | Sets the order of the next two fields: 1 puts registration version first, 0 puts registration authority first. |
✅ Verified |
UINT32 |
Registration version or authority | Depends on the server version. No longer used. | ✅ Verified |
UINT32 |
Registration authority or version | Depends on the server version. No longer used. | ✅ Verified |
UINT32 |
Account number | No longer used. | ✅ Verified |
UINT32 |
Registration token | No longer used. | ✅ Verified |
STRING |
LAN computer name | ✅ Verified | |
STRING |
LAN user name | ✅ Verified |
Remarks
The server answers with SID_CLIENTID, then SID_LOGONCHALLENGEEX, then SID_PING.
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_CLIENTID2 (client to server): documented by Leaky, and edited 3 times since.
This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.