Increase default cl_maxpackets to 125

[Calinou]

This decreases latency if FPS is greater than or equal to 60 (since the previous default for cl_maxpackets was 60), and allows for more consistent input handling. com_maxfps already defaults to 125, so it's a 1:1 match if your PC can render 125 FPS.

Increasing snaps further does not change anything on servers running sv_fps 20 or sv_fps 40, but it ensures you automatically benefit from increased position update rates on servers running higher sv_fps. This in turn allows you to see players' positions more accurately compared to their real position on the server.
Edit: This PR no longer changes the default of snaps, see https://github.com/ec-/Quake3e/pull/299#issuecomment-2422973974.

I've been using this configuration for years now and it works just fine, even on an average ADSL connection (before I had fiber).

[ensiform]

Does the default engine/other server engines besides quake3e cap to sv_fps for snaps?

[Calinou]

Does the default engine/other server engines besides quake3e cap to sv_fps for snaps?

Yes, I've tested this in ioquake3 (even old versions from ~2011) and various derivative games like Jedi Outcast.

[ec-]

I agree with cl_maxpackets but disagree with snaps: there is no benefits increasing it over 40 (same for sv_fps), it wont improve your average ping but increase incoming traffic (-demofiles) a lot, you shouldn't follow such servers' behavior

[Calinou]

I agree with cl_maxpackets but disagree with snaps: there is no benefits increasing it over 40 (same for sv_fps), it wont improve your average ping but increase incoming traffic (-demofiles) a lot, you shouldn't follow such servers' behavior

I've modified the PR to only change cl_maxpackets.