Valhalla Legends Forums Archive | Battle.net Bot Development | BNLS Help?

AuthorMessageTime
FuzZ
Yeah, I'm back and newbified. (none of you probably remember me anyway, but I prefer it that way)

Sending 0x1A to BNLS..
[code]
0000:  35 00 1A 03 00 00 00 00 00 00 00 00 00 00 00 6C  5............l
0010:  6F 63 6B 64 6F 77 6E 2D 49 58 38 36 2D 31 35 2E  ockdown-IX86-15.
0020:  6D 70 71 00 4A ED A2 68 A8 7D 9B F6 63 9C 8A 1B  mpq.Jí¢h¨}›öcœŠ
0030:  1A C2 77 2D 00                                    Âw-............

0000:  0B 00 1A 00 00 00 00 00 00 00 00                  ..............
[/code]
Something incorrect with this? I fail version check everytime.

Or is there another explanation why I'm failing version check? Perhaps bad parsing in 0x50?


November 5, 2007, 12:20 AM
l2k-Shadow
look at bnetdocs:

(DWORD) Product ID.*
(DWORD) Flags.**
(DWORD) Cookie.
(ULONGLONG) Timestamp for version check archive.
(STRING) Version check archive filename.
(STRING) Checksum formula.

you are leaving out a part of the message.
November 5, 2007, 12:36 AM
FuzZ
Well, I realize that the timestamp is missing, what confuses me is that this works

[code]
0000:  35 00 1A 03 00 00 00 00 00 00 00 00 00 00 00 6C  5............l
0010:  6F 63 6B 64 6F 77 6E 2D 49 58 38 36 2D 31 32 2E  ockdown-IX86-12.
0020:  6D 70 71 00 D5 27 C2 4E 5A EB E7 77 B6 58 48 F3  mpq.Õ'ÂNZëçw¶XHó
0030:  9C 28 7B AF 00                                    œ({¯............
[/code]

but mine does not.. To me, after looking over this several times I don't notice anything that's different, except perhaps the checksum itself and the # of the lockdown file.
November 5, 2007, 1:00 AM
DDA-TriCk-E
What BNLS/JBLS server are you using? Try hdx.jbls.org I never have any problems with that one. I believe bnls.valhallalegends.com is not updated for WarCraft III, because it still returns 0x14 as the version byte, so maybe lockdown is broken as well?
November 5, 2007, 1:10 AM
FuzZ
I am using HDX's JBLS server. I'm still trying to figure out what exactly is causing this.. I'm about to give up for the night though.. It's perplexing to say the least.
November 5, 2007, 1:13 AM
FuzZ
I'm not sure why the other was working, but I have it fixed, I was just too lazy to add the file time into it, but now that I have, it's corrected. Thank you both for your insight.
November 5, 2007, 1:16 AM
DDA-TriCk-E
Perhaps show us your code?

Edit: didn't see you resolved it :o
November 5, 2007, 2:10 AM
HdxBmx27
Nither of those logs should work...
[code]
35 00 1A 5.
03 00 00 00 ....
00 00 00 00 ....
00 00 00 00 ....
6C 6F 63 6B 64 6F 77 6E 2D lockdown
49 58 38 36 2D 31 35 2E 6D 70 71 00 -IX86-15.mpq.
4A ED A2 68 A8 7D 9B F6 63 9C 8A 1B 1A C2 77 2D 00 Jí¢h¨}›öcœŠÂw-............[/code]
Like Shadow said, you're missing the timestamps. I should kick you in the face for filling up my logs with 'Unknown Checkrevision Archive: -IX86-15.mpq TimeStamp: 0x2d6e776f646b636f6c'
Try sending the correct packet format.
~Hdx
November 5, 2007, 8:57 PM
FuzZ
Yeah, that's why I was confused about why one would work, and the other one wouldn't.. Because according to the BNLS Protocol, neither should work, but one of them did.

Regardless, I stopped being lazy and added the Timestamp, and it resolved the issue.. Thank you, again, for your input :)
November 6, 2007, 4:20 PM

Search