Nicely written, although I can correct you on one thing, I have tried and
tested this.

The "sv_maxupdaterate sv_minupdaterate sv_maxrate sv_minrate" do actually
work at capping clients to what they are set at. But the client still
displays their manually set rate, not the capped rate.  For example:

sv_maxrate 20000
sv_minrate 10000
sv_maxupdaterate 100
sv_minupdaterate 60

If a client sets:

cl_updaterate 40
rate 6000

the status will display thoes ammouts, but they will actually be on:

cl_updaterate 60
rate 10000

I tested this by setting a max and minrates on my own server to maxup 100
minup 100 maxrate 20000 minrate 20000.  I joined with 20 up and 1000 rate,
but my net graph was showing 5.7kBps down  (cl_cmdrate had to be set to 101
to get the correct download rate as lower cl_cmdrate lowers the downrate)

My explanation may be difficult to understand, but im sure youll work it out
:P

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Suck.
Sent: 21 July 2005 22:46
To: [email protected]
Subject: RE: [hlds] rate toggle


This is the best that I can explain it.  I'm sure you're aware of much of
this Alfred, but this should help inform those of you who don't know what's
going on:

The major client-side commands for different rates settings are "rate"
"cl_updaterate", and "cl_cmdrate".  The former two are difficult to exploit,
in that they affect how much info the client is receiving and processing.
cl_cmdrate, however, affects the rate that the client is sending data to the
server.  Players exploit this by turning it down to 10 or below (although
anything below 20 starts to become a problem).

Rates abusers are able to receive all the data they need to play relatively
normally, but because they're reporting their own data to the server so
infrequently, for the other players, they skip around and their actions come
in bursts.  This makes them extremely hard to hit for one, but also causes
instant deaths from nowhere as a rates exploiter appears on top of you.  A
side-effect of this is that for some reason, scoreboard ping drops extremely
low for players doing this, often around 5.

There are server-side cvars designed to set the max and min cl_updaterate,
but they don't work, as well as cvars to set max and min rate, although I'm
not sure of the efficacy of these.  There are no such cvars addressing
cl_cmdrate.


-Grant.


-----Original Message-----
From: [EMAIL PROTECTED] On Behalf Of Alfred Reynolds
Sent: Thursday, July 21, 2005 1:46 PM
Subject: RE: [hlds] rate toggle

Could I have a synopsis of the problems you are seeing please.

- Alfred




_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds



--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.9.2/54 - Release Date: 21/07/2005



_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to