Valhalla Legends Archive

I need to know the packet for news for the type of connection of 0x1E. If anyone can tell me it, i will be most appreicated.

I believe it's 0x46, but I could be wrong.

Quote from: Inner on May 12, 2004, 09:47 PM
I need to know the packet for news for the type of connection of 0x1E. If anyone can tell me it, i will be most appreicated.

What kind of connection type is 0x1e?  I've only ever heard of connections of 0x01, 0x02, and 0x03.

Quote from: Myndfyre on May 12, 2004, 11:40 PM

Quote from: Inner on May 12, 2004, 09:47 PM
I need to know the packet for news for the type of connection of 0x1E. If anyone can tell me it, i will be most appreicated.

What kind of connection type is 0x1e?  I've only ever heard of connections of 0x01, 0x02, and 0x03.

The older style authentication , used Hash.dll and CheckRevision.dll . where as the newer style use's BnetAuth.dll

Quote from: effect on May 13, 2004, 12:45 AM

Quote from: Myndfyre on May 12, 2004, 11:40 PM

Quote from: Inner on May 12, 2004, 09:47 PM
I need to know the packet for news for the type of connection of 0x1E. If anyone can tell me it, i will be most appreicated.

What kind of connection type is 0x1e?  I've only ever heard of connections of 0x01, 0x02, and 0x03.

The older style authentication , used Hash.dll and CheckRevision.dll . where as the newer style use's BnetAuth.dll

... both connection styles have the same hashing and checkrevision functions.

0x1E is the older form of connecting to Battle.net and I don't believe has any really descriptive name seperating it from 0x50 other than the "old logins".

Uh , im getting at the fact 1 style uses 2 DLL's and the other is encaptulated in 1?

Evidently everyone who responded missed the sarcasm in the question.  Connection type 0x1e is still connection type 0x01 -- binary.  It's just another login method.  

Quote from: effect on May 13, 2004, 01:16 AM
Uh , im getting at the fact 1 style uses 2 DLL's and the other is encaptulated in 1?

The number of libraries you use has nothing to do with the form in which you connect to bnet.

Quote from: Myndfyre on May 13, 2004, 03:33 AM
Evidently everyone who responded missed the sarcasm in the question.  Connection type 0x1e is still connection type 0x01 -- binary.  It's just another login method.  

I got it, but the point I was trying to make is that you shouldn't jump all over him when he was just trying to include which login style he was using.

The functions in bnetauth.dll are identical to those in hash.dll and checkrevision.dll...

And none of that affects how you logon. My bot uses no DLLs, and yet I have no trouble performing those functions. I must be a genius or something!

Quote from: Zakath on May 13, 2004, 10:25 AM
The functions in bnetauth.dll are identical to those in hash.dll and checkrevision.dll...

And none of that affects how you logon. My bot uses no DLLs, and yet I have no trouble performing those functions. I must be a genius or something!

I'm leaning towards something.

Wow...

Quote from: BinaryzL on May 13, 2004, 03:16 PM
Wow...

Best contribution to a thread ever!

Quote from: Zakath on May 13, 2004, 10:25 AM
I must be a genius or something!

Quote"Zakath, your a ****ing genius" - Jigsaw of Valhalla Legends on 1/7/02 at 7:22:23 PM EST

Well...

Back on topic?

If you check SoupBot source you'll find 0x46 C->S and C->S. (Since BnetDocs, AFAIK, is down and doesn't have a reference for this packet)
I've had some trouble while using it when using MCP (Realms) to connect.

I believe you have to call for it on login, or else WC3 and TFT will be the only clients to display it without asking for it. Atleast that's what I had to do. Not sure if anyone else has that problem, but it works fine for me, I request it for all clients but WC3 and TFT, if I do it calls it twice.