Yes we use ma_rates to check. Yes we have the vars set in server.cfg. Yes we run zBlock Max 2.0.2, will be updating to zBlock Max 2.0.3 in the morning Most our players are sub 50 ping. zBlock only has those vars to notify players of server side changes to those vars.
All I can say it that it has been observed by our admins and myself many times, hence why we warn kick and ban on refusal. Once brought up to an acceptable level that amazingly hard to hit player can then be hit. Our Source server box is running two srcds servers and a once a day updated [5 am] psychostats set up, one server is just a locked down test bed for a yet to be announced server plugin. The other a very popular 24 player Friendly Fire CS:S server plugins: Mani's non MM:S with much of it off PTBx zBlock Specs: 66 tickrate on dual 2.8ghz xeons, 3 gigs ram, running FC-3 out of a top level data center -------------------------------- I've yet to see a player go below our minrate/minupdaterate. You're sure it's set in the server.cfg? How are you checking their rates? ma_rates w/ Mani works like a charm. The largest complaint we have is players with a large difference between cl_updaterate and cl_cmdrate. I've tried it myself...sure doesn't seem like much of an advantage. zBlock Max v.2.something and sv_mins seem to do the (pub) trick). _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
