fps_max is limited at 30 and has been since the same update that brought us sv_pure
] fps_max 15 sv_cheats is 0 and fps_max is being limited to a minimum of 30 (or set to 0). Sean Rowswell wrote:
I think most if all server admins know that sv_mincmdrate can be bypassed simply by the client setting fps_max lower than the required cmdrate value. So I suggest the following commands: sv_minfpsrate - self explanatory (default: 0) sv_maxfpsrate - self explanatory (default: 0) sv_minclientfps - if the clients fps drops below this value they are kicked (default: 10) sv_maxclientping - if they clients ping goes above this value they are kicked (default: 300) Also to prevent rate and fps exploiting (if you don't know how this is done Alfred feel free to email me and I will send you the details; I would rather not post it) I would suggest you make another flag (like FCVAR_CLIENT_CANT_BIND - forgive me if this is wrong) that would make the following cvars unbind'able (and also don't work as binds even if set before with sv_cheats 1) while sv_cheats is set to 0: rate cl_cmdrate cl_updaterate cl_interpolate cl_interp_ratio fps_max cl_smooth (Make sure that the flag takes into account if a user tries to use bindtoggle or bind incrementvar) Also could you make the clients tickrate (how many ticks they are currently sending to the server) a network variable like ping so it can be retrieved when creating a playerlist keygroup. Thankyou - criticism and comments welcome.
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
