SB3: SID_AUTH_CHECK

[UserLoser]

[22:48:27] Unrecognized BNCS packet data for SID_0051 received:
0000:  00 02 00 00 53 70 68 74 42 6F 74 76 33 00         ....SphtBotv3.

Come on now why isn't this handled?

[Spht]

I'm quite certain there is code to handle that message....

[UserLoser]

I'm quite certain there is code to handle that message....

So explain why it showed that twice? ...

[Spht]

I'm not sure what you're asking?

[UserLoser]

I'm not sure what you're asking?

Why doesn't your bot handle that message with that specific message data (invalid cdkey)?  It's not hard to comprehend

[Joe[x86]]

More interestingly, why is there a 'more info' string in message 0x200?

[UserLoser]

More interestingly, why is there a 'more info' string in message 0x200?

Maybe it was because my Cd-Key info wasn't really invalid, it's just something else happened to make me get that message.  But still, I don't get why that's 'unrecognized' to the bot, it's a much known packet for a long time now..

[Spht]

More interestingly, why is there a 'more info' string in message 0x200?

Maybe it was because my Cd-Key info wasn't really invalid, it's just something else happened to make me get that message.  But still, I don't get why that's 'unrecognized' to the bot, it's a much known packet for a long time now..

I'm sure the bot handles that result code.  It's probably the extra data that triggered the error.  According to BnetDocs, that result code shouldn't have associated "additional information."

I can't verify anything at the moment because I don't have access to the source code.

You could always write a plugin to handle such messages if it bothers you that much.  I'm sure there any plenty of "much known packets" that the bot doesn't support--that's why it displays such pretty errors when they do show up, so frequently occurring unrecognized messages can be traced and supported in the future or users can write plugins to handle them.

[dxoigmn]

I'm sure the bot handles that result code.  It's probably the extra data that triggered the error.  According to BnetDocs, that result code shouldn't have associated "additional information."

Every SID_AUTH_CHECK packet contains additional information; just in some cases, it is an empty string. So there is really no reason this shouldn't be handled, nor should a sanity check stop it from being handled.

[Spht]

I'm sure the bot handles that result code.  It's probably the extra data that triggered the error.  According to BnetDocs, that result code shouldn't have associated "additional information."

Every SID_AUTH_CHECK packet contains additional information; just in some cases, it is an empty string. So there is really no reason this shouldn't be handled, nor should a sanity check stop it from being handled.

I was able to check the source code and found that there is an explicit check for empty additional info for a couple particular result codes and developer comments to keep it that way.  I do not recall the reason though, but there must've been one.

[topaz]

[20:14:33] Unrecognized BNCS packet data for SID_0051 received:
0000:  00 02 00 00 53 70 68 74 42 6F 74 76 33 00         ....SphtBotv3.

Just got this, but I was repeatedly logging on/off with different accounts.

And then... disconnected.

[20:15:55] Error 10053 connecting to Battle.net server!