Valhalla Legends Archive

Hey this is for I3inary below, but anyone else that likes this code can use it. (Insert this code RIGHT BELOW InsertDword Checksum in packet 0x51.)


If Product = "RHSS" Or Product = "LTRD" Or Product = "RHSD" Then
InsertDWORD &H0
InsertDWORD &H0
InsertNTString exeinfo
InsertNTString "Freeware"
SendPacket &H51
Exit Sub
End If


This sends the 0x51 packet with 0 cdkeys (ignoring all the cdkey info alltogether) Hope you find it useful.

If that works, does this mean 0x50 works for those products too? [havn't tested this yet]

Edit: Wow, 0x50 does work for DRTL - 0x51 works too!

Is there a way to get JSTR to work with 0x51?  I get disconnected, but no IPban, i've also tried sending the CDKey in plain text also, and that didn't work either, yet no ipban.

mamazing! +1

Thanks for comments. Yes it does use 0x50 like a normal binary connection. You could use the old login procedure, but (stupidly) bnet enabled the newer login connection for older clients.

SC Japan: I have tried logging in with SC Japan many many times, but am unable to get it to work. If anybody knows anything about connecting with it please post

[edit] After some research i found out that SC Japan requires the old login procedure since they disowned the game. SC Japan obviously still works (saw someone just the other day with a SC Japan icon), but I dont know any bots that support it. With Bnet Docs down, I cant find the older login procedure code anywhere. If anybody really wants to connect with SC Japan ill try to packet log it later.

The real non-cdkey clients presently do not use the 0x50 login; it is an oversight by the battle.net programmers that allows this method to work.  If they correct that oversight, your client will quite likely be banned upon its next connect.

Quote from: Kp on September 03, 2003, 04:45 PM
The real non-cdkey clients presently do not use the 0x50 login; it is an oversight by the battle.net programmers that allows this method to work.  If they correct that oversight, your client will quite likely be banned upon its next connect.

Yah but since when are they smart enough to do that. (*Cough Cough SC Japan Cough*)

You are correct; since SC Japan.
There was a short period where "Japan bots" were the latest craze and Blizzard disabled that, first by disabling non-plain CD-keys from SC Japan clients, then by restricting them to public channels.

Yup Japan Bots were crazy until blizzard disabled them (in about a month). Though they were too stupid to ban all the cdkeys that did login with SC Japan. Probably Text Colors will be disabled next.

Well if anybody did want to know how to login with SC Japan:

Version byte: 0xA9

                   With PacketBuf
                       .InsertDWORD 0
                       .InsertNTString varCdkey 'Plaintext
                       .InsertNTString "Freeware"
                       .SendPacket sckBnet, &H30
                   End With

There you go its the '0x51' for SC Japan.
[Edit] I dont really know much about 0x30 login, but I think if you did want to login as spawn make the dword 1.

Quote from: Freeware on September 03, 2003, 04:44 PM
Thanks for comments. Yes it does use 0x50 like a normal binary connection. You could use the old login procedure, but (stupidly) bnet enabled the newer login connection for older clients.

SC Japan: I have tried logging in with SC Japan many many times, but am unable to get it to work. If anybody knows anything about connecting with it please post

[edit] After some research i found out that SC Japan requires the old login procedure since they disowned the game. SC Japan obviously still works (saw someone just the other day with a SC Japan icon), but I dont know any bots that support it. With Bnet Docs down, I cant find the older login procedure code anywhere. If anybody really wants to connect with SC Japan ill try to packet log it later.

If you actually have Starcraft Japan, mind packet logging creating a game [0x1a/0x1c?], starting a game [0x3c?], and leaving a game, also a ladder game along with 0x2c

Quote from: Freeware on September 03, 2003, 05:11 PM
Yup Japan Bots were crazy until blizzard disabled them (in about a month). Though they were too stupid to ban all the cdkeys that did login with SC Japan. Probably Text Colors will be disabled next.

Why would they ban the CD-keys of users that log on with the Japanese version of Starcraft? There are still people who play the game...

Quote from: UserLoser on September 03, 2003, 05:17 PM
If you actually have Starcraft Japan, mind packet logging creating a game [0x1a/0x1c?], starting a game [0x3c?], and leaving a game, also a ladder game along with 0x2c :P

I will upload that information later after i get JSTR login to work.

Holy Jesus!   Someone did their homework.....might be a little delayed in the color department but nice work everywhere else.

Quote from: CrAz3D on September 03, 2003, 05:52 PM
Holy Jesus!   Someone did their homework.....might be a little delayed in the color department but nice work everywhere else.

Yup didnt take too long, - im almost done with JSTR login if anybody cares.

That's right, don't mention Camel for suggesting sending zero cd keys.

Quote from: Camel on August 29, 2003, 12:58 AM

Quote from: 13inary on August 28, 2003, 04:07 PM
Well Starcraft Shareware Accepts my 0x50 login but of course it rejects my 0x51 since there is no cdkey for starcraft shareware. For starcraft shareware's it seems like i can just send my 0x50, then the 68XIRHSS with the Exe information and continue from there. I just need to know if im doing it right.

Also it seems that i still use Bnetauth.dll to make a password hash, but it doesnt seem to need a 0x51 challenge hashes. Anyway I just want to know if i can send 0x50, send 68XIRHSS with the Exe information, send my login, join chat and thats it.

Every time i log the data everything sent is the same, but i need to know what

Code Select Expand

D‡Û before the exe information is, that seems to be the only changing variable.

Did you try sending 0x51 with zero cd keys? I'm not sure if it will work, but from the way you phrased that, it seems like you're sending a single junk cd key.

BTW, that DWORD is probably the checksum.

Well camel I used my own code i already had, and did not know you posted that. *thanks camel anyway*