Seems as if Bnet's up to it again

[Hdx]

Any bot that reports the correct mpq number to JBLS will be able to login correctly.
And I told UL to send Sky a page to make sure that BNLS works fine. (It should, there wernt any major changes)
Also all local hashing that worked with the old formula should work now.
I think hte main problem is that SB dosen't work cuz Andy is an idiot.
~-~(HDX)~-~

[Hero]

I think hte main problem is that SB dosen't work cuz Andy is an idiot.
~-~(HDX)~-~

Ouch. 

[rabbit]

I think hte main problem is that SB dosen't work cuz Andy is an idiot.
~-~(HDX)~-~

Ouch. 

Eh.  It's true.

[Sixen]

Also all local hashing that worked with the old formula should work now.

My hashing still does not work. But, then again, i'm on ShitBot. StealthBot* =]. God.. Make Andy fix it or we'll have to rape him, :X.

[Hdx]

He is fixing it, I called him last night, and after school today he will work on the bot and atleast release a new beta. And then sometime soon a new rev.
Now bring all further Sb talk to his forums, not here!
~-~(HDX)~-~

[UserLoser]

Listen up, there is no change.  The only way to fix your clients is to properly parse the MPQ digit number.  BNLS will not need to be upgraded, and that guy on StealthBot probably connected because Battle.net told him to use ver-IX86-6.mpq which was a coincedence like I had already explained.

[Mephisto]

So please explain how we properly use the new MPQ digit number when it is sent to us?

...

On RECV_AUTH_INFO I have:

Code Select Expand

pRead->ExtractData(global->_bnetData._MPQVersionFile);
// ...
global->_bnetData._MPQVersionNumber = (unsigned long)atol((const char*)&global->_bnetData._MPQVersionFile[7]);
// ...
if(global->_bnls)
global->_bnlsConnect->Send_CHOOSENLSREVISION();


(this is referring to my BNLS connection)

Maybe I just over-read the fix in this discussion? sigh...

Edit: Battle.net is still sending me the MPQ filename in the format ver-ix86-#.mpq rather than ix86ver#.mpq.  So if I set the buffer to read the digit at the [9] index it gets the correct number, but still fails the version check.  Meh...

[Spilled]

So please explain how we properly use the new MPQ digit number when it is sent to us?

...

On RECV_AUTH_INFO I have:

Code Select Expand

pRead->ExtractData(global->_bnetData._MPQVersionFile);
// ...
global->_bnetData._MPQVersionNumber = (unsigned long)atol((const char*)&global->_bnetData._MPQVersionFile[7]);
// ...
if(global->_bnls)
global->_bnlsConnect->Send_CHOOSENLSREVISION();


(this is referring to my BNLS connection)

Maybe I just over-read the fix in this discussion? sigh...

Edit: Battle.net is still sending me the MPQ filename in the format ver-ix86-#.mpq rather than ix86ver#.mpq.  So if I set the buffer to read the digit at the [9] index it gets the correct number, but still fails the version check.  Meh...

There was no change in the checkRevision... The only change was the mpqFileName... Update your bot to recognize this change and your connection should be successful. I believe the change was (IX86ver0.mpq to IX86-0.mpq or some small change of that sort)

[MyndFyre]

Listen up, there is no change.  The only way to fix your clients is to properly parse the MPQ digit number.  BNLS will not need to be upgraded, and that guy on StealthBot probably connected because Battle.net told him to use ver-IX86-6.mpq which was a coincedence like I had already explained.

Change or no, I had to update my library because they're using bigger numbers than before and I was getting overflow exceptions. 

[Mephisto]

There was no change in the checkRevision... The only change was the mpqFileName... Update your bot to recognize this change and your connection should be successful. I believe the change was (IX86ver0.mpq to IX86-0.mpq or some small change of that sort)

Code Select Expand

pRead->ExtractData(global->_bnetData._MPQVersionFile);
cout << Timestamp() << "MPQ Filename: " << global->_bnetData._MPQVersionFile << endl;
....
The MPQ file name is "ver-IX86-#.mpq" as I receive it from Battle.net, so I do ....

Code Select Expand

global->_bnetData._MPQVersionNumber = (unsigned long)atol((const char*)&global->_bnetData._MPQVersionFile[9]);
Yet, it seems to fail the version check 60% of the time and pass 40% of the time.

[Spilled]

Which library?

[vuther.de]

I'm getting the right mpq filename, but it still doesn't work.. What else needs to be done?

[MyndFyre]

Which library?

MBNCSUtil.

[Spilled]

My vb applications that use bnetauth.dll are working fine but my c++ application needs up to data bncsutil binaries. Anyone have these?

[MysT_DooM]

I'm getting the right mpq filename, but it still doesn't work.. What else needs to be done?

did you parse the number correctly
1)