bab24f2295
the server was simulating correctly all along - the log shows a goblin covering 120 units a tick and a knight 60, exactly their Speed columns, in a straight line with no jitter. the teleporting was the correction rate: one snapshot a second, while the client runs its own prediction in between and diverges from ours. a unit gets more than a tile out of step before our state arrives and drags it back. the snapshot now goes every four ticks and the gateway ticks every fifty milliseconds rather than two hundred, so a correction moves a unit a fifth as far. this makes the symptom smaller, not absent. it goes away when the two simulations agree, which is what the checksum comparison is for and what collisions and projectiles are still missing for. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||