VerByte?

[The-FooL]

What is the new VerByte for TFT/WC3?

[UserLoser.]

17

[Minux]

17

0x11 and the new hashes are here

Damn I was trying to packet log as fast as I could, but Userloser is just too damn quick on the draw . But I did figure it out before I came here to post.

Edit: I noticed BNLS isn't updated yet, and if you wish to use my hashes that I uploaded, which I got from my client folder. I guarantee they are 100% clean and I hope BNLS can be up ASAP

[Deception]

17

0x11 and the new hashes are here

Damn I was trying to packet log as fast as I could, but Userloser is just too damn quick on the draw . But I did figure it out before I came here to post.

Edit: I noticed BNLS isn't updated yet, and if you wish to use my hashes that I uploaded, which I got from my client folder. I guarantee they are 100% clean and I hope BNLS can be up ASAP

Why would you need to packet log to find the new version byte? The version byte for WarCraft III is always the same as the patch version, eg. 1.17 patch's version byte is 17 or 0x11.

[iago]

17

0x11 and the new hashes are here

Damn I was trying to packet log as fast as I could, but Userloser is just too damn quick on the draw . But I did figure it out before I came here to post.

Edit: I noticed BNLS isn't updated yet, and if you wish to use my hashes that I uploaded, which I got from my client folder. I guarantee they are 100% clean and I hope BNLS can be up ASAP

Why would you need to packet log to find the new version byte? The version byte for WarCraft III is always the same as the patch version, eg. 1.17 patch's version byte is 17 or 0x11.

So far, it is, but that doesn't mean it'll always be

[Deception]

17

0x11 and the new hashes are here

Damn I was trying to packet log as fast as I could, but Userloser is just too damn quick on the draw . But I did figure it out before I came here to post.

Edit: I noticed BNLS isn't updated yet, and if you wish to use my hashes that I uploaded, which I got from my client folder. I guarantee they are 100% clean and I hope BNLS can be up ASAP

Why would you need to packet log to find the new version byte? The version byte for WarCraft III is always the same as the patch version, eg. 1.17 patch's version byte is 17 or 0x11.

So far, it is, but that doesn't mean it'll always be

Is Blizzard just going to just pick a random number for the next version byte? I don't think so. It is logical to assume that the next version byte would be the 1 more than the previous one . The-FooL should have tried that before starting this thread.

[Zakath]

No, it is not logical. That, in fact, is a logical fallacy. If asked the question, "will the sun rise in the East tomorrow?," saying "yes" then backing it up by saying it "because it always has" is not an acceptable response.

Now, it's certainly a guess with a high probability of success, and yes, it probably would have been not-too-hard for him to have tried it first, but please...let's get our logic straight here.

[tA-Kane]

For example, if Blizzard were to make another patch in a few days, and name it 1.17b (as they have with StarCraft at least once), the version byte could be changed again.

[The-FooL]

I did try 0x11 before posting the thread.  Unfortunatly BNLS Warcraft Logins, which I rely on, were being rejected.  So I was still getting errors connecting, and wanted to know ahead of time.

Edited because my choice of words is so important.

[Spht]

I did try 0x11 before posting the thread.  Unfortunatly BNLS, which I rely on for WAR3 Hashing, was down.  So I was still getting errors connecting, and wanted to know ahead of time.

It wasn't down.  It was just rejecting Warcraft III logons.  Skywing has upgraded the patching mechanism and there's now more people with the ability to order BNLS to update itself.  So I suspect for future patches, updating BNLS hash files will happen much quicker.

[Blaze]

Skywing has upgraded the patching mechanism and there's now more people with the ability to order BNLS to update itself.

Thats good news.