wisedev/scroll.server
1
2
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

read the sector command fields the way round they are sent

Browse source 
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.
This commit is contained in:
WiseDev 2026-08-23 14:05:43 +03:00
parent 9230a212ef
commit 9f1f9a7cef
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
crates/logic/src/messages/sector_command.rs
View file

@ -4,9 +4,9 @@ use crate::commands::LogicCommand;
#[message(id = 12904, direction = "client", name = "SectorCommandMessage")] #[message(id = 12904, direction = "client", name = "SectorCommandMessage")]
#[codec(partial)] #[codec(partial)]
pub struct SectorCommandMessage { pub struct SectorCommandMessage {
#[codec(vint)]
pub client_tick: i32,
#[codec(vint)] #[codec(vint)]
pub client_checksum: i32, pub client_checksum: i32,
#[codec(vint)]
pub client_tick: i32,
pub command: Option<Box<dyn LogicCommand>>, pub command: Option<Box<dyn LogicCommand>>,
} }