Valhalla Legends Archive

Programming => Battle.net Bot Development => Topic started by: AC_Drkan on February 28, 2005, 09:22 AM

Title: Help?
Post by: AC_Drkan on February 28, 2005, 09:22 AM

[10:21:23] Failed version check!
[10:21:24] Searching for latest version code...
[10:21:24] The version code must be manually updated.

Thats on spht Bot and on flawed i get this:

[10:22:07] CDkey Error! Unknown byte: &H101


Can anone tell me what bnet did last night? or maybe i did?

Nvm, Fixed it. Please delete this message

EDIT * 2:
Just reboot the computer and mine worked fine.
Title: Re: Help?
Post by: Kp on February 28, 2005, 09:38 AM
Flawed bot is apparently living up to its name.  0x101 cannot fit in a byte.  That it would ever claim so is a flaw.
Title: Re: Help?
Post by: Mephisto on February 28, 2005, 10:32 AM
Isn't 0x01 an error code reported from 0x51?  And for that matter it's an unsigned long, not a byte as Kp mentioned.
Title: Re: Help?
Post by: UserLoser. on February 28, 2005, 02:12 PM
Quote from: SoR-Mephisto on February 28, 2005, 10:32 AM
Isn't 0x01 an error code reported from 0x51?  And for that matter it's an unsigned long, not a byte as Kp mentioned.

No. It could be, but because I highly doubt this bot was written in another language than VB (supports signed longs only) judging by what it outputs, I doubt it was an unsigned long.
Title: Re: Help?
Post by: iago on February 28, 2005, 02:36 PM
You also can't assume that an "unsigned long" is 4 bytes.  The correct term for the error code would be an "unsigned 4-byte little endian integer" :)

Title: Integer sizes
Post by: Kp on February 28, 2005, 11:18 PM
Quote from: iago on February 28, 2005, 02:36 PMYou also can't assume that an "unsigned long" is 4 bytes.  The correct term for the error code would be an "unsigned 4-byte little endian integer" :)

Commonly known in these parts as luint32_t. ;)  uint32_t is acceptable if you don't mind endianness ambiguity.