the checksum goes out first and the tick second: setClientChecksum writes [+0x50] and setClientTick writes [+0x54], and encode writes [+0x50] before [+0x54]. we had them the other way about, which is why the log showed a tick full of noise and a checksum climbing by forty-one a message - the tick was being read as the checksum. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||