User Profile

D2 sends 67 of these packets in a row before sending SID_EXTRAWORK. The length of the data, excluding the BNCS header, is approximately between 100 - 200 bytes.

Diablo 2 1.14d has been observed to set the game type to 4 in C>S 0x4B SID_EXTRAWORK. The length has been observed to be as high as 2578.

Refer to my comment at https://bnetdocs.org/packet/388#comments to learn more about why this packet existed.

Blizzard sent this packet for a total of 7 days to collect email addresses from users who failed the CD key check during the connection process.

Below are some links I found referencing this situation:

• https://artho.com/warcraft/whatsold.html
• https://games.slashdot.org/story/98/04/17/23277/blizzard-violates-gamers-privacy
• http://edition.cnn.com/TECH/computing/9805/04/privacy_piracy/index.html
• https://www.gamespot.com/articles/starcraft-suit-is-history-concerns-persist/1100-2464364/
• https://www.gamespot.com/articles/starcraft-sniffing-graded-by-gamers/1100-2463569/
• https://www.gamespot.com/articles/starcraft-supports-ask-do-lawyers-suck/1100-2463650/
• https://www.gamespot.com/articles/blizzard-hit-with-privacy-suit/1100-2463619/

All links have been saved to the Wayback Machine.

If anyone finds any additional information about this, please post it here.

Recently (possibly on August 13), Blizzard removed many CheckRevision v2 files from US West, US East, and Europe servers. As of now, Asia server still retains all of the CheckRevision v2 files.

I tested the following at US West:

lockdown-IX86-{NUM}.mpq: 00 still exists, 01 - 19 are removed.

psistorm-PMAC-{NUM}.mpq: 00 still exists. 01, 02, and presumably the rest have been removed too.

psistorm-XMAC-{NUM}.mpq: 00 - 02 no longer exists, presumably the rest have been removed too.

When attempting to connect to US West, US East, or Europe with W2BN, Battle.net sends SID_STARTVERSIONING with a randomly chosen CheckRevision v2 filename despite that the chosen file may be missing. The filetime is null if the file is missing. The client hangs after receiving this packet if the filetime is null.

ix86std.dll is found in an MPQ embedded in DRTL 1.02, 1.03, and 1.04 manual patches.

I found that if D2 1.13c is served IX86ver1.mpq, it crashes with a 0xc00000005 error. Serving it ver-IX86-1.mpq, which is what Battle.net served, no longer causes it to crash. This leads me to think that Blizzard didn't just rename CheckRevision v1 files in 2006, they probably recompiled CheckRevision v1 with the same code or different code while keeping the output the same.

Max MOTD length is 512 bytes, including the null terminator.

I observed SEXP 1.16.1 sending this packet even if client has not logged in.

Icon Precedence:

1. For any user, display the first icon in icons.bni that has icon flags matching the bitwise-and of the icon flags and user flags (given by server in SID_CHATEVENT).

2. For StarCraft users displaying icons other StarCraft users' icons, the first icon in icons_STAR.bni that has an icon code matching the value in the Icon Code field in chat statstrings.
   For WarCraft 3 users displaying other WarCraft 3 users' icons, the first icon in icons-WAR3.bni that has an icon code matching the value in the Icon Code field in chat statstrings.

3. For any user displaying icons of users with different product codes, display the first icon in icons.bni that has icon flags matching the Icon Code field in chat statstrings.

4. For any user displaying icons of users with the same product code, display an internal icon. See http://classic.battle.net/info/icons.shtml and http://classic.battle.net/war3/ladder/w3xp-ladder-info-laddericons.aspx?Gateway=Lordaeron for examples.

According to PvPGN, the Tier sub-field in WarCraft 3's Icon Code field appeared in patch 1.03.

The StarCraft statstring format in this document appeared starting in patch 1.10. Previously, the latter 4 or 5 fields did not exist.

Missing information about StarCraft Beta. There also exists StarCraft Japanese Beta, don't know if it had Battle.net support.

Diablo: Hellfire appears to have basic Battle.net support.

Status 0x04 and 0x05 shows the same message that 0x03 shows.

On Diablo 2 (Open Battle.net), the client sends this packet before sending SID_LEAVEGAME.

On Diablo 2 (Closed Battle.net), this packet is never sent.

On Diablo 2 (Open Battle.net), the server responds back with SID_STARTADVEX3 and then the client sends SID_LEAVECHAT. No SID_NOTIFYJOIN packet is sent.

On Diablo 2 (Closed Battle.net), the server does not respond to this packet. The client immediately sends SID_NOTIFYJOIN followed by SID_LEAVECHAT.

When Number of ranks listed is 0, I observed four null bytes following the field.

I can confirm there's an extra null byte at the end of the packet.

ff 07 0a 00 02 00 00 00 00 00

As of 1.14d, the packet structure is significantly different.

UINT8[16]       Unknown 1 (MD5?)
UINT32          IP (Big Endian)
UINT32          Port (Big endian)
UINT8[40]       Unknown 2 (SHA-1?)
UINT8[9]        Unknown 3 (Padding?)

Diablo 2 1.14d sends 0x04 as the game type.

For Game Type, PvPGN lists PGL as 0x0E.

I'm maintaining a list of known offsets for patch 1.17.0: https://www.reddit.com/r/broodwar/wiki/1_17_0_offsets