War3 v1.15 beta patch - new stuff! (updated)

[UserLoser.]

0x35 (C->S) - Profile request
----------------
(DWORD) Cookie
(STRING) Username

0x35 (S->C)
----------------
(DWORD) Cookie
(STRING/BYTE) Unknown - Always seen 0
(STRING) profile\description value
(STRING) profile\location value
(DWORD) Clan name



0x82 (C->S) - Clan user information
----------------
(DWORD) Cookie
(DWORD) Clan tag of user
(STRING) Username

0x82 (S->C)
----------------
(DWORD) Cookie
(STRING/BYTE) Unknown - Always seen 0
(STRING) Clan name
(BYTE) Rank in clan
(FILETIME) Date joined

[evileye]

Very thx!
btw, is there a 0x80 packet?
I've seen description of 0x70 to 0x79 and 0x81, 0x82 packet, but 0x80 lacked

[Stealth]

Can these be requested by Warcraft III clients on the standard (non-beta) servers?

[Soul Taker]

Can these be requested by Warcraft III clients on the standard (non-beta) servers?

Try it...?

[FuzZ]

Can these be requested by Warcraft III clients on the standard (non-beta) servers?

Try it...?

Why should he take the risk of getting IP Banned when someone may have already tested it? ;p

BTW, grats on your 500 posts Soul Taker

[Stealth]

Can these be requested by Warcraft III clients on the standard (non-beta) servers?

Try it...?

Bah. No, they can't.

[Spht]

0x35 (S->C)
----------------
(DWORD) Cookie
(STRING/BYTE) Unknown - Always seen 0
(STRING) profile\description value
(STRING) profile\location value
(DWORD) Clan name

That's the clan's tag, not name.

0x82 (S->C)
----------------
(DWORD) Cookie
(STRING/BYTE) Unknown - Always seen 0
(STRING) Clan name
(BYTE) Rank in clan
(FILETIME) Date joined

That "unknown" is a success byte. If non-zero, the message will be 5 bytes.

[nYko]

It would be cool if BNLS supported the 1.15 beta patch, so I could try those packets out.

[Spht]

It would be cool if BNLS supported the 1.15 beta patch, so I could try those packets out.

Not really, then we wouldn't be able to use Warcraft III on non-Westfall. But it might be nice if someone were to set up a temporarly BNLS server somewhere which uses Warcraft III 1.15 files.

[MyndFyre]

It would be cool if BNLS supported the 1.15 beta patch, so I could try those packets out.

Not really, then we wouldn't be able to use Warcraft III on non-Westfall. But it might be nice if someone were to set up a temporarly BNLS server somewhere which uses Warcraft III 1.15 files.

However, wouldn't it be okay to set up an additional two product IDs -- Warcraft III 1.15 = 9, Warcraft III The Frozen Throne 1.15 = 10?  Depends on how BNLS works I suppose

[conjecture]
Since I'm getting "unrecognized" version from 0x51 (because I've updated my version byte and the exe version string), I believe that there are two things left for me to update: the second DWORD of 0x51, Exe Version, which I've gotten by packetlogging, and then the EXE hash, the third DWORD of 0x51.

The conjecture is this: is the EXE hash a standard double-hash -- with the server and client tokens -- of the EXE version string?
[/conjecture]

If so, it should be fairly simple, by packetlogging, to get BNLS to do the work (using BNLS_HASHDATA).  You might need to play around with your stuff a little bit though.

[iago]

It would be cool if BNLS supported the 1.15 beta patch, so I could try those packets out.

Not really, then we wouldn't be able to use Warcraft III on non-Westfall. But it might be nice if someone were to set up a temporarly BNLS server somewhere which uses Warcraft III 1.15 files.

However, wouldn't it be okay to set up an additional two product IDs -- Warcraft III 1.15 = 9, Warcraft III The Frozen Throne 1.15 = 10?  Depends on how BNLS works I suppose

[conjecture]
Since I'm getting "unrecognized" version from 0x51 (because I've updated my version byte and the exe version string), I believe that there are two things left for me to update: the second DWORD of 0x51, Exe Version, which I've gotten by packetlogging, and then the EXE hash, the third DWORD of 0x51.

The conjecture is this: is the EXE hash a standard double-hash -- with the server and client tokens -- of the EXE version string?
[/conjecture]

If so, it should be fairly simple, by packetlogging, to get BNLS to do the work (using BNLS_HASHDATA).  You might need to play around with your stuff a little bit though.

If I correctly understand what you're saying, then no.   It's not a hash of the EXE version string, it's a hash of the actual data files.

[Spht]

However, wouldn't it be okay to set up an additional two product IDs -- Warcraft III 1.15 = 9, Warcraft III The Frozen Throne 1.15 = 10?  Depends on how BNLS works I suppose

That'd probably be too much work considering the beta is only lasting a couple weeks.

If someone *really* wants to get on the server, they can download the CheckRevision DLL on the bot development web site and run a local CheckRevision on the game (assuming you own Warcraft III 1.15), and use BNLS for everything else. This is probably the fastest solution now.

[MyndFyre]

However, wouldn't it be okay to set up an additional two product IDs -- Warcraft III 1.15 = 9, Warcraft III The Frozen Throne 1.15 = 10?  Depends on how BNLS works I suppose

That'd probably be too much work considering the beta is only lasting a couple weeks.

If someone *really* wants to get on the server, they can download the CheckRevision DLL on the bot development web site and run a local CheckRevision on the game (assuming you own Warcraft III 1.15), and use BNLS for everything else. This is probably the fastest solution now.

Having looked through BotDev on your suggestion, where is the CheckRevision DLL?  I can't seem to find it....

[Tuberload]

However, wouldn't it be okay to set up an additional two product IDs -- Warcraft III 1.15 = 9, Warcraft III The Frozen Throne 1.15 = 10?  Depends on how BNLS works I suppose

That'd probably be too much work considering the beta is only lasting a couple weeks.

If someone *really* wants to get on the server, they can download the CheckRevision DLL on the bot development web site and run a local CheckRevision on the game (assuming you own Warcraft III 1.15), and use BNLS for everything else. This is probably the fastest solution now.

Having looked through BotDev on your suggestion, where is the CheckRevision DLL?  I can't seem to find it....

http://botdev.valhallalegends.com/files/checkrevision.zip

[tA-Kane]

If someone *really* wants to get on the server, they can download the CheckRevision DLL on the bot development web site and run a local CheckRevision on the game (assuming you own Warcraft III 1.15)

Am I missing something? I was under the impression that the implementation of CheckRevision() in that DLL does not work for WarCraft 3 or TFT?