Greetings,
TS3 PROTOCOL PAPER
==================
# 0. Naming Conventions
- `(Client -> Server)` denotes packets from client to server.
- `(Client <- Server)` denotes packets from server to client.
- All datatypes are sent in network order (Big Endian) unless otherwise
specified.
- Datatypes are declared with a prefixing `u` or `i` for unsigned and signed
and a number for the bitlength.
For example `u8` would be the C equivalent of `uint8` or `unsigned char`
- Arrays are represented by the underlying datatype in square brackets,
additionally if the length is known it is added in the brackets, separated by
a semicolon. Eg: `[u8]`, `[i32; 16]`
- Array ranges (parts of an array) are specified in square brackets with the
included lower bound, two points (`..`) and the excluded upper bound. Eg: `[0..10]`
# 1. Low-Level Packets
## 1.1 Packet structure
show original
In section 2.4, a note says that if the server sent 127 which is 07F instead of 0x03, the client should reset the connection and start from packet 0 again, I have tried everything, but the client isn’t restarting the connection, just sending packet 2 over and over until the client return a failed message.
Is this feature deleted?
Hope anyone can helps.
Best Regards
Hmm, it seems so simple. The solution is to send 0x00 after 0x7F. An admin can close the thread
