Jumpbug: optional velocity-timed assist

The unduck window is only 2 units, while a 625-ups fall moves ~9.3 units per
66.7 Hz movement command, so pure jumpbug is ~20% reliable at that speed.

- Add Jumpbug -> Assist timing (default off). When the natural next command
  would skip [36,38], pin the post-command ducked distance to 37 by writing
  the vertical velocity for that command. Pure jumpbug remains available with
  the option off.
- Resolve the client local m_vecAbsVelocity (0x11C) via the client datamap
  and the server m_vecAbsVelocity (0x228) via the server datamap.
- Write both the authoritative server velocity (what SetupMove reads through
  GetAbsVelocity) and the local prediction fields, so the next CreateMove sees
  the assisted origin on both sides.
- Do not write the server m_vecVelocity directly: the datamap scan finds two
  same-named entries (0x1C and 0x29C); SetAbsVelocity syncs it after movement.

0 files changed, 0 insertions, 0 deletions