(no biography information)
|Member for||13 years, 1 month, 28 days|
- GitHub: heinermann
Just want you to know that the hash is easily broken on older games and updating to an installation with a Digital Key is highly recommended.
I can still use my old key after registering it. Just both keys cannot be logged in at the same time.
Diablo Battle.net Beta: DIAB
I think you should if the product, pubic, and private values are associated with it. AFAIK it is for any Blizzard key
Confirmation: The Starcraft Anthology digital installer uses product value 0x17, there are no reservations.
Confirmation: The Diablo II digital installer uses product value 0x18, there are no reservations.
Retrieved the following from the game installers:
0x05: 16-digit Diablo II Beta Key
0x06: 16-digit Diablo II Retail Key
0x07: 16-digit Diablo II Retail Key
0x09: 16-digit Diablo II Stress Test Key
0x0A: 16-digit Diablo II: Lord of Destruction Retail Key
0x0C: 16-digit Diablo II: Lord of Destruction Retail Key
0x0D: 26-digit Warcraft III: Reign Of Chaos Beta key
0x0E: 26-digit Warcraft III: Reign Of Chaos Retail Key
0x0F: 26-digit Warcraft III: Reign Of Chaos Retail Key
0x11: 26-digit Warcraft III: The Frozen Throne Beta key
0x12: 26-digit Warcraft III: The Frozen Throne Retail key
0x13: 26-digit Warcraft III: The Frozen Throne Retail key (NOTE: This product seems disabled? Has something to do with Chinese region)
Any conflicts are intentional. Product IDs that havn't been seen before are reserved by the appropriate installer.
Starcraft II and the other digital keys might also have reservations, but I havn't been able to really grab it from the installer.
It might be safe to assume that DTST is a Diablo Stress Test
Enum in wc3tft beta:
There's an event 0x0B in Diablo Beta, unable to test it out or find out what it does
Parameter is more like SubType.
Values for GameType/SubType 2 Melee 3 Free For All 4 One on One 5 Capture The Flag 6 Greed -- SubType: Resources (1 = 2500; 2 = 5000; 3 = 7500; 4 = 10000) 7 Slaughter -- SubType: Minutes (1 = 15; 2 = 30; 3 = 45; 4 = 60) 8 Sudden Death 9 Ladder -- SubType: Disconnects (Specifies if a disconnect is counted as a loss or not) 10 Use Map Settings 11 Team Melee -- SubType: Number Of Teams (1 = 2; 2 = 3; 3 = 4) 12 Team Free For All -- SubType: Number Of Teams (1 = 2; 2 = 3; 3 = 4) 13 Team Capture The Flag -- SubType: Number Of Teams (1 = 2; 2 = 3; 3 = 4) 15 Top Vs. Bottom -- SubType: Teams (1-7 specifies the ratio of players belonging to both teams) 16 Iron Man Ladder 32 PGL
Those values apply to Starcraft and W2BN
Pulled these from wc3 tft beta:
Here's some random error names I found while looking at wc3 tft beta, which might contribute to creating better names:
Enum in wc3tft beta:
Couldn't find the values for these, but you can guess where they go anyway.
BNET_FRIEND_MUTUAL_FRIEND BNET_FRIEND_DND BNET_FRIEND_AFK BNET_FRIEND_ONLINE
0 BNET_FRIEND_OFFLINE 2 BNET_FRIEND_IN_CHANNEL 3 BNET_FRIEND_IN_PUBLIC_GAME 4 BNET_FRIEND_IN_PRIVATE_GAME 5 BNET_FRIEND_IN_PASSWORD_GAME
I checked and the Alpha/Pre-release has nothing Battle.net related.
I looked into the code in Starcraft where DTST is referenced. It grabs the icon from glueattle.neticons.pcx from patch_rt.mpq according to the product (this function is probably no longer used).
DRTL, DSHR, and DTST all have the Diablo icon according to that piece of code.
Getting a hold of the Diablo Battle.net Beta might give us the answers.
or 0xFF80 for All Games
Condition 3 is 0xFFFF for SEXP as well.
They are defunct and were tested through packet interception and modification.
I was testing each event for a universal text display (recv hook) in Starcraft and discovered it there.
It was there long before Diablo 3 even began so I highly doubt it. It probably was as you said (Diablo TeST)
[0x15] EID_IGNORE: (Starcraft) notifies that a user has been ignored
[0x16] EID_ACCEPT: (Starcraft) notifies that a user has been unignored
I found a product code called DTST. You can find it in Starcraft.exe(1.16.1)@0x004497A4.
From what I can tell its the same as DRTL?