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

[Eric]

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?

Warcraft III uses the same CheckRevision() as all the other products requiring auth use; similar CD-Key decoding/hashing structure too, I believe.

[UserLoser.]

Warcraft III uses the same CheckRevision() as all the other products requiring auth use; similar CD-Key decoding/hashing structure too, I believe.

IIRC, Warcraft III uses two key value tables, one that's 256 bytes, and another which is 480.  I believe the 256 one is almost same, if not, exact to the current Diablo II/Warcraft II CDkey decoding.  As far as the hashing, I think it's the same.  You take the values returned (in this case, iirc a 10 byte value, and dunno the other one) and hash them the same

[MyndFyre]

Allright, so I recompiled the CheckRevision function into a Win32 DLL with the function exported, and I am successfully calling it with the DllImport("CheckRevision.dll") attribute from my C# code (I checked the packet log).  But, I think I'm passing in the wrong files.

I'm using (right now) war3.exe, storm.dll, and game.dll for CheckRevision.  Here's the exact call:

Code Select Expand


int authcheckver = 0, authcheckcsum = 0;
CheckRevision("C:\\Program Files\\Warcraft III\\war3.exe", @"C:\Program Files\Warcraft III\storm.dll", @"C:\Program Files\Warcraft III\game.dll", this.checkForm, ref authcheckver, ref authcheckcsum, this.versionCheckStatString, this.mpqFile);


(Yes, the ref keyword is effectively the same as passing a pointer).

this.versionCheckStatString is set correctly when I'm done.

this.checkForm is the string that contains the hashing formula.

I'm getting "Game version not recognized" back.

[iago]

It's possible you have them in the wrong order, since order does matter.

If you want a java version (closer to what you're doing) let me know and I'll send it to you.

[LordNevar]

Your getting "game version incorrect" is not caused by your hash calls or your cdkey calls, it's cause something most people don't know there's 2 cdkey's being swapped around while using wc3. There's the product key that use send to bnet, and the other key that bnet sends back to you in response to identify your cdkey, and game information.  As Far as I know skywing's the only one that's been able to emulate that key. If anyone can figure out any info on the other key, or if skywing would give us a hint, than wc3 hashing is indeed very prossible.

[Soul Taker]

Your getting "game version incorrect" is not caused by your hash calls or your cdkey calls, it's cause something most people don't know there's 2 cdkey's being swapped around while using wc3. There's the product key that use send to bnet, and the other key that bnet sends back to you in response to identify your cdkey, and game information.  As Far as I know skywing's the only one that's been able to emulate that key. If anyone can figure out any info on the other key, or if skywing would give us a hint, than wc3 hashing is indeed very prossible.

What?

[Eric]

Your getting "game version incorrect" is not caused by your hash calls or your cdkey calls, it's cause something most people don't know there's 2 cdkey's being swapped around while using wc3. There's the product key that use send to bnet, and the other key that bnet sends back to you in response to identify your cdkey, and game information.  As Far as I know skywing's the only one that's been able to emulate that key. If anyone can figure out any info on the other key, or if skywing would give us a hint, than wc3 hashing is indeed very prossible.

What?

I don't even think he knows what he just said.

[MyndFyre]

Your getting "game version incorrect" is not caused by your hash calls or your cdkey calls, it's cause something most people don't know there's 2 cdkey's being swapped around while using wc3. There's the product key that use send to bnet, and the other key that bnet sends back to you in response to identify your cdkey, and game information.  As Far as I know skywing's the only one that's been able to emulate that key. If anyone can figure out any info on the other key, or if skywing would give us a hint, than wc3 hashing is indeed very prossible.

What?

I don't even think he knows what he just said.

can't you guys see?  Since Skywing did it, it's "prossible."

Is that a synthesis of "probable" and "possible" ?