Since cl_maxpackets will be boosted to max 125, it will mean in terms of 'hits latency' the ones with 125 will have a huge advantage compared to those on 30 which is now the default. It is 8 milliseconds latency of 'hits sent to the server', compared to a 33.3 milliseconds!
i.e. It's important to consider this and potentially increase the default, even if it means servers will be needing higher downloading bandwidth.
A decent solution might be to have it on 85. If FPS remains on 85 by default then that's the max cl_maxpackets can send anyway. But I wouldn't be very sorry if I saw both FPS and packets going to 125; though you don't save bandwidth.
It could be argued that high ping players can get an equal ground by having higher packets compared to low pingers but that's a pointless endeavor since low pingers can just higher theirs.
--
Thinking to remove the increase (and go back to 42) is not a solution either, since there is a huge advantage in having high maxpackets to all players: the game feels smoother, especially so called 'hits'.
--
Bandwidth savings may not be so huge anyway since client sent messages appear to be packing previous commands if they are dispatched less frequently.
This post has been edited by mitsubishi: 04 September 2010 - 09:42 AM