Receiveing Bytes

[Yegg]

When you have a socket receiving bytes from Battle.net while on a chat client, things are received as 1001 USER Yegg 0000, etc. If I don't do any kind of parsing of the packets when I receive data from Battle.net while on a hashed connection, will I still receive something like 1001 USER Yegg 0000? Pretty much what I need to know is if both types of connects receive or can receive data in the same way.

[shadypalm88]

When you have a socket receiving bytes from Battle.net while on a chat client, things are received as 1001 USER Yegg 0000, etc. If I don't do any kind of parsing of the packets when I receive data from Battle.net while on a hashed connection, will I still receive something like 1001 USER Yegg 0000? Pretty much what I need to know is if both types of connects receive or can receive data in the same way.

* head explodes *

If you mean, "Are the events (packets) on a hashed connection in the same format as on a chat (telnet) connection?", the answer is no.  See BnetDocs for more information.

If you mean, "Do you receive data from a socket on a hashed connection using the same function calls?", or something, the answer is yes.

If you meant something else... then I'm sorry, but I didn't understand what you wrote.

[Blaze]

If you are getting plain text packets, you are sending the: Chat Protocol Byte: 0x03. Send 0x01 Game Protocol Byte instead.

[Yegg]

So it is just a matter of which packet I send to receive the different types of packets? 1001 USER Yegg 0000 would be chat and Game would be something else, correct?

[Tazo]

So it is just a matter of which packet I send to receive the different types of packets? 1001 USER Yegg 0000 would be chat and Game would be something else, correct?

Correct.