Server can increase this with sv_fps. I read somewhere that this will crash the server, but it worked fine on my LAN server. It may not with larger server though, idk. Would be pretty pointless anyway, since it would nearly double the server’s bandwidth consumption without making a significant difference.
Antoher thing I noticed when testing that, was that changing snaps had no effect, neither on etpro nor nq. With sv_fps 40 and snaps 10, the lagometer still showed that I recieved 40 packets per second. In fact, it doesn’t seem to work in 2.60b at all, but it does in 2.55… 
[QUOTE=C;227973]
We also limit com_maxfps to 125 max. This to prevent people with fast computers to draw many-many frames, and flood the server with packets.
Yeah, i know… it’s evil.[/QUOTE]
Unless I’ve misunderstood you, the number of packets sent to the server is already limited by cl_maxpackets, which again is limited to 100 in the engine. So clients can’t send more than 100 packets anyway.
And one more thing, setting com_maxfps to 0 means maximum (About 980), so if you want to properly enforce that 125 cap, force it IN 1 - 125. Otherwise clients could set it to 0 and still flood you. 
