Spread control: override the server FireBullets seed for the local player

The installed 2024 server ignores the client usercmd random_seed and uses its
own shot seed. Force the server's CBaseEntity::FireBullets RandomSeed call for
the local player only:

- hook the server.so RandomSeed GOT slot (R_386_JUMP_SLOT at 0xce1348);
- read the FireBullets `this` from the caller frame and compare it with the
  local server player base;
- replace the seed with the precomputed best single/shotgun window and step it
  per pellet; NPC shots and everything else pass through.
- client prediction still uses the same chosen usercmd seed, so both sides
  agree on the spread pattern.

0 files changed, 0 insertions, 0 deletions