From 9f1f9a7cef9b651382e043445308dd3eeac40795 Mon Sep 17 00:00:00 2001 From: WiseDev <83840010+wisedevik@users.noreply.github.com> Date: Sun, 23 Aug 2026 14:05:43 +0300 Subject: [PATCH] read the sector command fields the way round they are sent 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. --- crates/logic/src/messages/sector_command.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/logic/src/messages/sector_command.rs b/crates/logic/src/messages/sector_command.rs index 0b518e5..dda9f1a 100644 --- a/crates/logic/src/messages/sector_command.rs +++ b/crates/logic/src/messages/sector_command.rs @@ -4,9 +4,9 @@ use crate::commands::LogicCommand; #[message(id = 12904, direction = "client", name = "SectorCommandMessage")] #[codec(partial)] pub struct SectorCommandMessage { - #[codec(vint)] - pub client_tick: i32, #[codec(vint)] pub client_checksum: i32, + #[codec(vint)] + pub client_tick: i32, pub command: Option>, }