BNETDocs: Redux is no longer updated, this subdomain exists for archival purposes only. Visit the main site.


Generate Code: All packets

Packet Information

Message ID:0x51
Direction:Server -> Client (Received)
Used By:Starcraft Broodwar, Diablo II, Warcraft III: The Frozen Throne, Starcraft, Diablo, Warcraft III
Format:(DWORD) Result
(STRING) Additional Information
Remarks:Reports success/failure on version & CD Key check.

0x000: Passed challenge
0x100: Old game version (Additional info field supplies patch MPQ filename)
0x101: Invalid version
0x102: Game version must be downgraded
(Additional info field supplies patch MPQ filename)
0x0NN: (where NN is the version code supplied in SID_AUTH_INFO): Invalid version code (note that 0x100 is not set in this case).
0x200: Invalid CD key *
0x201: CD key in use (Additional info field supplies name of user)
0x202: Banned key
0x203: Wrong product
The last 4 codes also apply to the second CDKey, as indicated by a bitwise combination with 0x010.

If a patch file cannot be found, additional info is set to 'non-existent'. If either the executable size/date or the version code is wrong, the server will typically return a failure status.

* If you receive this status, official servers ban you for 24 hours (as of 06/15/2011). It used to be 2 weeks, but they changed recently.

While doing a little research on how autoupdates it's clients, I found that it (STAR, anyway) does not use the provisions of the SID_AUTH login system to tell clients which update file to download. Instead, it sends a SID_REPORTVERSION (from the previous logon system) containing the equivalent error code and the name of the patch file to download. This seems strange, and makes me think that the part of responsible for updating clients is isolated from the part responsible for processing logon requests. If this is the case, it makes sense that that system was never updated, since it must still support legacy clients. In addition, this would explain why most Blizzard clients retain obsolete packet processing code.
Related:[0x51] SID_AUTH_CHECK (C->S)

User Comments

For detailed questions and discussion, visit the Research Forum

Apr 28, 2010
10:13 AM

0x211 - LoD CD key is used by: string
0x101 is now being sent after a CD key has been registered on website.

Jun 30, 2010
06:04 AM

I registered my Starcraft on the website and the server doesn't send me 0x101 when I try to use my key. Do you have any proof?

Sep 10, 2010
05:49 PM

I can still use my old key after registering it. Just both keys cannot be logged in at the same time.

Sep 10, 2010
06:13 PM

Interesting; so if two separate CD keys are registered to a 2.0 account, the result is that only one CD key can be logged on at a time-- meaning the account can only be logged in one at a time?

Sep 19, 2010
02:49 AM

No, Kryo I think you misunderstood that. If I register STAR on my 2.0 account, I cannot login with my 13-digit STAR CDKey and my 26-digit STAR key at the same time. They're the same CDKey, they're just in two different formats.

This also means that any restrictions (mute, banned, jailed, etc) will be on the new Game Key.

I like to refer to the physical keys as CDKeys and the new digital keys as Game Keys.

We recommend you use Firefox to view this site. This site has been optimized for Firefox.

Get Firefox
BNLS Server Status

= Online       = Offline Server Status v1 v2




= Online       = Offline


Site scripts and design copyrights reserved to Don Cullen.
Contents copyrighted to Blizzard and their parent corporation, Vivendi.
Main credits for contents goes to Arta. View the rest of credits.
Demented Minds copyrights reserved to Don Cullen 2003-present.
Copyright infringements will be prosecuted to the fullest extent allowable by law.
Please view our legal disclaimer and terms of service.