SOLVED: [VB6] Enter Chat Problem

[pianka]

I started coding the connection to my bot today and got up through logging in.  When I added the 0x0A and 0x0C join chat packets, I get disconnected and temporarily IP banned.  I send these two packets after Battle.net confirms that my login worked in 0x3A:

Code Select Expand


With clsOut
    .InsertString Bots(Index).Username
    .InsertString ""
    .SendPacket frmMain.sckBNET(Index), &HA
    .InsertDWORD &H2
    .InsertString Bots(Index).HomeChannel
    .SendPacket frmMain.sckBNET(Index), &HC
End With


I also get disconnected and IP banned when sending only 0x0A.  According to my packet logger, the hex dumps of these two are:

Code Select Expand


0000000000 FF 0A 0F 00 4B 6F 47 42 6F 74 34 2E 30 00 00 FF ....KoGBot4.0...
0000000010 0C 11 00 02 00 00 00 43 6C 61 6E 20 4B 6F 47 00 .......Clan KoG.


My username is "KoGBot4.0" and I'm trying to get into the channel "Clan KoG".  Can anybody help me?

[Blaze]

I've looked over everything there, and I can't seem to see anything wrong.  How about trying a non-forceful join of your clan channel (0x00 on 0x0C)?

[Joe[x86]]

He also gets banned when only sending 0x0A.

I see nothing wrong with that. Asuming you're on WC3, see this.

[pianka]

I'm on Starcraft: Broodwar, and yeah it is regardless of the join channel packet...I just have no idea how you could screw up such a small packet

[Ringo]

I'm on Starcraft: Broodwar, and yeah it is regardless of the join channel packet...I just have no idea how you could screw up such a small packet

Is battle.net requesting you check extrawork.mpq on the logon? My guess is its some prelogon offence thats causeing it.

[pianka]

Yeah that's what I'd be guessing as well, but I'm not receiving any unknown packets like that.  Are there any other reasons as to why it might do this?

[l2k-Shadow]

Those 2 packets seem correct along with the hex dumps. So the problem isn't in those two.. I suggest backtracing and seeing if you didn't mess up something on sending/handling 0x3A just in case.

[topaz]

Bans for protocol violation usually happen immediately on SID_ENTERCHAT. Check your packets.

[Joe[x86]]

I'm on Starcraft: Broodwar, and yeah it is regardless of the join channel packet...I just have no idea how you could screw up such a small packet

In that case you need to send 0x0B between 0x0A and 0x0C if you want to get a reply.

Bans for protocol violation usually happen immediately on SID_ENTERCHAT. Check your packets.

Incorrect. Bans for protocol violation happen when you conduct the violation.

[l2k-Shadow]

I'm on Starcraft: Broodwar, and yeah it is regardless of the join channel packet...I just have no idea how you could screw up such a small packet

In that case you need to send 0x0B between 0x0A and 0x0C if you want to get a reply.

Definitely not, 0x0B is a totally optional packet which may be sent whenever after sending 0x0A, and it may be sent more than once. Starcraft sends this packet whenever you click the channel button.

[Networks]

Shouldn't he wait until he receives 0x0A?

[Spilled]

Those 2 packets seem correct along with the hex dumps. So the problem isn't in those two.. I suggest backtracing and seeing if you didn't mess up something on sending/handling 0x3A just in case.

This on my opinion would be your best bet, Double check your 0x3A. Perhaps a packetlog of this?

[Ringo]

Yeah that's what I'd be guessing as well, but I'm not receiving any unknown packets like that.  Are there any other reasons as to why it might do this?

S > C 0x3A responce might be wrong?
You might have gotten account success/failed mixed up, if so, that would ipban when sending 0x0A.

[Joe[x86]]

Shouldn't he wait until he receives 0x0A?

Nope. I'm at school right now so I don't have the source code to JBBE, but I send 0x0A, immediatly followed by 0x0B, immediatly followed by 0x0C, and I have never once gotten IPBanned by doing that.

EDIT -

S > C 0x3A responce might be wrong?
You might have gotten account success/failed mixed up, if so, that would ipban when sending 0x0A.

That's entirely possible. I think success/fail have some weird values, success being 0 and failure being 1, so that could have thrown him off.

[pianka]

Yeah, you guys were right.  My parsing for 0x3A was correct, but when double hashing the password I was using the wrong client token. Whoops Thanks for your help though.