BNLS_VERSIONCHECKEX2

[Ersan]

Code Select Expand

.InsertULONG MpqFileTime
A filetime struct has two 4-byte halves, totalling 7 bytes an a null terminator.

As for why your parsing's off:

Code Select Expand

If .GetBYTE = &H1 Then
The BOOL response is 4 bytes long (GetDWORD), not one.  I have no idea why Skywing did that.

[Skywing]

A FILETIME is not a delimited item.  It is two raw four-byte halves (or a single unaligned eight-byte field); there is no null terminator.

Aside from fields with an explicit (dynamic) length or null delimited fields, all fields in the body of BNLS messages tend to be at least four bytes in length.

[Chriso]

Whenever I send 0x51 using Version, Checksum and ExeInfo from 0x1A I get disconnected and IPbanned on the server

[l2k-Shadow]

paste your fixed 0x1A parse + 0x51 send?

[Kp]

Therefore, we can conclude that you're doing it wrong.  If you want more help, we need more information.  Perhaps you should post the actual bytes sent?  You can censor the cdkey data, but without seeing the outbound message we cannot even be sure you're sending the data in the right order.

[Ersan]

A FILETIME is not a delimited item.  It is two raw four-byte halves (or a single unaligned eight-byte field); there is no null terminator.

Sorry, I have no idea where I read that it was nullterm, it's 8 bytes regardless.

[MysT_DooM]

these posts in this topic should help you out also
http://forum.valhallalegends.com/index.php?topic=15960.210

[Chriso]

Thanks I'll try everything you guys said, I still don't know why it's disconnecting me, everything looks correct compared to BnetDocs but I'll get back to you if I fix it...

[Ringo]

Oh maybe it's the ULONGLONG? I just assumed that was FILETIME? does it have a different format/size? how many bytes should it be in length?

Code Select Expand


0x1A

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




Heres what I'm getting from BNLS compared to hashing

Code Select Expand


D2DV

Using Hashes
version: 16780032
checksum: 522892090
exeinfo: Game.exe 07/19/06 11:54:27 2125824

Using BNLS
version: 0
checksum: -1895759861
exeinfo: í~Game.exe 08/17/05 01:11:43 2125824


Apart from (what looks like) not skipping the BNLS packet header, I dont think BNLS_VERSIONCHECKEX2 supports d2/w3 clients as of yet?

[Skywing]

It should support those clients.

[Ersan]

Apart from (what looks like) not skipping the BNLS packet header, I dont think BNLS_VERSIONCHECKEX2 supports d2/w3 clients as of yet?

I already mentioned that he was treating the boolean success as one byte instead of four.  And yes it does.

[Ringo]

It should support those clients.

Oh my bad, I thought D2/W2 clients couldnt use it yet

I already mentioned that he was treating the boolean success as one byte instead of four.

Ok, but dont expect an award or anything..

And yes it does.

Thanks.

[Chriso]

Apart from (what looks like) not skipping the BNLS packet header, I dont think BNLS_VERSIONCHECKEX2 supports d2/w3 clients as of yet?

I already mentioned that he was treating the boolean success as one byte instead of four.  And yes it does.

Yeah I have  been treating it as four bytes since you pointed that out, still doesnt work.

[Hdx]

Post a packet log + Your changed handle code.
~-~(HDX)~-~

[Chriso]

The error had to do with BNLS_CDKEY_EX it wasn't returning the cdkey data correctly.