- replay the shooter's combat update a second time when it launches a
projectile, matching the client's own component-pass re-entry
- carry the shooter's damage effect on every projectile and null a
shot's target/source when either leaves the board
- derive pending physical damage from the shots actually in flight
instead of an incremental total, so it can never go negative
- split the spawn ring's two angle registers so three- and five-unit
cards land where the client puts them
- attribute a combat target left at NONE to the exact site that did it,
gated to report each object once
- number and annotate every checksum field so a client-reported
mismatch resolves straight to a name
npc missions used to get a ServerErrorMessage back. now StartMission builds a
LogicGameMode snapshot off the arena tilemap and answers 21903.
towers come from assets/locations/*.csv the way initDefaultSector does it: tile
coordinates times 500, leader index decided by which half of the map the tower
sits in. the two king towers must be there, the client dereferences them without
a null check. they live in buildings.csv, not characters.csv.
LogicCharacter puts the base object fields fourth, not first. the buff component
writes a fixed array sized by the character_buffs row count even with no buffs.
training_arena parses to 2 kings, 4 princess towers, 36x64 subtiles. snapshot is
602 bytes over 6 objects. the real client has not seen it yet.
field order taken straight off LogicBattle::encode. the object manager is
columnar, not object major: 6 counters, a count, then all data refs, then all
global ids, then all objects, then four component passes. global ids must be
ascending, the client binary searches them.
LogicRandom moved out of the shop into its own module. its abs was
checked_abs().unwrap_or(0), the binary uses NEGS so i32::MIN stays i32::MIN.
one seed in four billion, but it would have desynced the card shop.
per object subclass encodes and the component payloads are still missing, so no
snapshot can be sent yet.
