I think what he was getting at is that its fine for the STATS output, he just didn't want other GSPs to somehow figure out what ticrate he was using to reach that response. I don't care about them seeing the ticrate, I only care that they cannot alter it. The same thing ought to be done with fps_max in SRCDS.
AnAkIn . wrote: > Anyway they can still use the stats command to see how much FPS the server > has. > > 2009/6/21 Marcel <[email protected]> > > >> Thomas Kalman wrote: >> >>> Simple; for nondisclosure. Many GSP's are duplicating the value of the >>> >> cvar >> >>> sys_ticrate from other GSP's. I think it should be a corporate secret >>> >> what >> >>> settings each company uses. >>> >> Maybe it works with "-sys_ticrate 1000 +sys_ticrate 2000". It should fix >> sys_ticrate to 1000 and show sys_ticrate 2000. >> But come on...this is so ridiculous! >> >> sys_ticrate is and was never a secret - tweak your kernel and it'll be >> fine. everything else is useless. >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.339 / Virus Database: 270.12.82/2190 - Release Date: 06/20/09 > 17:54:00 > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
