| Remarks: | Sends information about the Client to Battle.net.
*These fields can be set to zero without breaking logon.
Protocol ID:- Battle.net's current Protocol ID is 0.
Platform ID:- A DWORD specifying the client's platform (IX86, PMAC, XMAC, etc).
Product ID:- A DWORD specifying the client's game.
Version:- The client's version byte.
Product Language:- This field is under investigation. It can safely be set to 0.
MPQ Locale ID:- This field is part of Blizzards multi-lingual MPQ system. Is used to specify which version of an MPQ should be used when the MPQ is available in multiple languages.
Local IP:- This is the local network IP of the client, in network byte order.
Timezone bias:- The difference, in minutes, between UTC and local time. The client calculates this value by subtracting the Local Time from the System Time, having converted both to Filetime structures, and then converting the resultant offset to minutes by diving it by 600,000,000. If you wish to understand the mechanism involved, read Microsoft's documentation on File times.
Language ID, Country Abbreviation, and Country:- These values can be retrieved by querying the system's locale information.
Language ID can be retrieved using the GetUserDefaultLangID API.
Country Abbreviation & Country can be retrieved using the GetLocaleInfo API to request the LOCALE_SABBREVCTRYNAME and LOCALE_SENGCOUNTRY, respectively. |
= Online 
= Offline
, 
, 
, 
, 
, 
BNETDocs News
User Comments
For detailed questions and discussion, visit the Battle.net Research Forum
Dec 01, 2007
02:04 AM
Local IP address in network byte order can be determined using the inet_addr API (http://msdn2.microsoft.com/en-us/library/ms738563.aspx)
Region can be determined by joining LOCALE_SISO639LANGNAME and LOCALE_SISO3166CTRYNAME together after they have been determined by the GetLocaleInfo API e.g.:
Region = GetLocaleInfo(LOCALE_SISO639LANGNAME) & GetLocaleInfo(LOCALE_SISO3166CTRYNAME)
Jul 08, 2009
06:39 AM
The product ID can use W2BN / WarCraft II BNE. I saw MirageBot by Chriso using it when I network-logged it, and it works just fine as of June 8th, 2009. All I am saying is, W2BN does not have to use the older version (CLIENTID packets), and that it can use this newer version (SID_AUTH_INFO, SID_AUTH_CHECK, SID_LOGONRESPONSE2, SID_ENTERCHAT).
In an interesting topic, I wonder (have not tested) if it is possible to supply CHAT to the product ID, instead of an actual binary client like STAR or WAR3. If you could do this, then the ol' Chat-icon that was seen back before 2005 may still be able to be seen around the Battle.net.