Valhalla Legends Archive

Programming => Battle.net Bot Development => Topic started by: ChR0NiC on March 28, 2004, 04:48 PM

Title: Weird Respone to 0x51??
Post by: ChR0NiC on March 28, 2004, 04:48 PM
I received the result &H213.....for some reason..

And the string : Hydra Chat v2.0

Which is my bot.....but I am not using the key.....I am getting this error on both West, East, Europe And Asia....

And i am the only one who has this version of my bot currently....

Any suggestions as to what might be causing it??
Title: Re:Weird Respone to 0x51??
Post by: tA-Kane on March 28, 2004, 04:51 PM
Ghosted clients, perhaps (eg, you connect, disconnect, but Battle.net doesn't know you've disconnected)?

Often happens to me when my client crashes... it leaves the socket open when it does. I usually have to go into a tool and manually close the connection.
Title: Re:Weird Respone to 0x51??
Post by: ChR0NiC on March 28, 2004, 04:54 PM
But how does it make sense that it's on all 4 servers???

Edit: Plus, I don't remember &H213 being an "in use" result...maybe it's new...
Title: Re:Weird Respone to 0x51??
Post by: Spht on March 28, 2004, 05:00 PM
Quote from: ChR0NiC on March 28, 2004, 04:48 PM
I received the result &H213.....for some reason..

And the string : Hydra Chat v2.0

Which is my bot.....but I am not using the key.....I am getting this error on both West, East, Europe And Asia....

And i am the only one who has this version of my bot currently....

Any suggestions as to what might be causing it??

BNLS documentation states that 0x0213 means your second CD-key has an invalid product code.
Title: Re:Weird Respone to 0x51??
Post by: ChR0NiC on March 28, 2004, 05:07 PM
Ah yes, I noticed it's in the Protocol Spec. I'll just check there first next time. For anyone who doesn't know what im talking about...

Go Here (http://www.valhallalegends.com/yoni/stuff/BNLSProtocolSpec.asp#SID_AUTH_CHECK) Or Go Here (http://www.valhallalegends.com/yoni/BNLSProtocolSpec.txt)

Thanks SPHT :)
Title: Re:Weird Respone to 0x51??
Post by: Arta on March 29, 2004, 04:16 AM
BnetDocs also documents this result code.