DEVLOG | May 21, 2026

Cleaner Remote Movement Updates

Separated remote movement from slower combat state so the client can spend more of each update on what is changing right now.

Changes

• Coalesced acknowledgement-only update ticks so the live session lane spends less bandwidth on messages with no visible aircraft movement.
• Separated fast aircraft movement from durable world state so position updates can reach clients without carrying older context that does not affect the current view.
• Split durable combat events away from movement updates so hits, crashes, and scoring records no longer have to ride in the same packet as aircraft motion.
• Stopped combat events from carrying broad world snapshots, keeping those messages focused on the result players care about while reducing stale data around them.
• Interleaved preserved updates with aircraft movement so important carried-forward state can still arrive without blocking fresher position changes.
• Added a compact movement update shape so remote aircraft state can be sent more cheaply, leaving more room for frequent position refreshes during a round.