|Transport Layer:||Transmission Control Protocol (TCP)|
|Application Layer:||Battle.net v1 TCP Messages (SID)|
|Direction:||Server to Client|
|Used By:||Starcraft Original, Starcraft Broodwar|
Starcraft Shareware, Starcraft Japanese
Diablo Retail, Diablo Shareware
Diablo II, Diablo II Lord of Destruction
Warcraft II BNE
(does not include protocol header)
Client should set the internal Battle.net server list from the contents of this message.
This packet is supported by all Battle.snp games and Diablo II and its expansion.
Note that this packet is defunct. The clients (including Warcraft III) all ask Battle.net for the FILETIME structure of the gateway list file and then compares that structure to its own cached copy. If the FILETIMEs do not match, then it goes to BNFTP and downloads a new one and stores it to the Windows Registry (or on file, if using Mac) while also caching the new FILETIME for later. They do not ever under any circumstance store the actual file data, and therefore as long as the cache is not changed and Battle.net always reports the same FILETIME, you can modify your gateway list without it knowing it changed.
no one has commented yet.