If you can get a hold of one of the older changelogs 2.0-3.0 thier is mention of cl_rate being locked at 9999. Having no luck with the search feature on the forum tends to work now and again at best.
CheeseLork on the ClorfJoin Date: 2003-12-15Member: 24396Members, Constellation
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->Having a low rate of 5000 will not make you harder to hit, or harder to play against. Not even a rate of 1 will make you hard to hit.
Rate affects are client side only, so it's at your advantage to keep them high. Lowering your rate will make the game unbearably laggy, since rate is how fast you take information from the server.
Setting your rate too high for your connection (i.e. 2501 is a good setting for 56K) will just make the game lag for you since your client will try to download too much information at once.
cl_rate is a command which controls how fast you send info to the server; so naturally if you lower it then it will make you appear laggy to others since the server will not know exactly where your real position is. However, you will still see things normal if you keep your rate high. That is why cl_rate is locked to 9999. cl_rate is your upload, rate is download.
Hope that clears any questions up.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
ok...but that would mean its impossible to rate hax in ns. Is that right? If so i ll have to retalk with the guys who called us rate hackers...they told us that it was neraly impossible to shoot us because we had set our rates to 5000...and that they wont play against cheaters...but if it is impossible to do it...what sense would that make?
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->ok...but that would mean its impossible to rate hax in ns. Is that right? If so i ll have to retalk with the guys who called us rate hackers...they told us that it was neraly impossible to shoot us because we had set our rates to 5000...and that they wont play against cheaters...but if it is impossible to do it...what sense would that make? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> I'm not sure. Cl_cmdrate is unlocked, and it controlls the number of updates you send to the server. If it's set absurdly low, then it might be a problem for other players. However, your "reflexes" over the net will also be dulled so much (you'll tell your client to fire or move, which then has to wait for the next packet to send out to the server) that it may be more of a handicap than an advantage.
However, setting your rate variable to 5000 should in no way be exploitive. Setting cl_rate, however, may be exploitive, depending on if it's been locked or not. I'm not sure, but judging by what people have said about it, it may not "dull your reflexes" as much as cl_cmdrate would by being set low.
i have a cable modem. is that too low? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> cl_updaterate and cl_cmdrate are not exploitive commands.
Having a bad cl_cmdrate increases choke. Dunno about you, but a high choke is worse than a high ping, by far and large. It will keep any of your shots and bites from registering.
Having a bad cl_updaterate will increase latency. Lag sucks. Keep good update rates.
Lowering either of these commands could potentally make you a tougher target to hit... but it will not be nearly as big as a disadvantage as not being able to kill anyone else.
Therefore it follows cl_updaterate and cl_cmdrate are non-exploitive. You can set them to whatever you want.
Anyone who claims you are rate hacking doesn't know what he is talking about. You can just ignore them, because they are ignorant.
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> the ns dev team say they will do a lot of things
put cl_rate 1000 ingame and ask someone what your model looks like<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
If you change your cl_rate in game, and check your cl_rate again by typing in "cl_rate" it will say your cl_rate is 9999.
So is the console bugged as well? Honestly I don't believe you, it's more likely that you guys were trying too hard to spot something wrong than the console be bugged too.
<!--QuoteBegin-NGE+Apr 9 2005, 07:48 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (NGE @ Apr 9 2005, 07:48 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> If you change your cl_rate in game, and check your cl_rate again by typing in "cl_rate" it will say your cl_rate is 9999. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> Mine doesn't D: it stays at whatever I set it to, and it keeps it like that when I change server =/
<!--QuoteBegin-NGE+Apr 9 2005, 01:48 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (NGE @ Apr 9 2005, 01:48 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> So is the console bugged as well? Honestly I don't believe you, it's more likely that you guys were trying too hard to spot something wrong than the console be bugged too. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> it isn't hard to spot what's wrong with cl_rate 1000
Comments
If you can get a hold of one of the older changelogs 2.0-3.0 thier is mention of cl_rate being locked at 9999. Having no luck with the search feature on the forum tends to work now and again at best.
put cl_rate 1000 ingame and ask someone what your model looks like
Rate affects are client side only, so it's at your advantage to keep them high. Lowering your rate will make the game unbearably laggy, since rate is how fast you take information from the server.
Setting your rate too high for your connection (i.e. 2501 is a good setting for 56K) will just make the game lag for you since your client will try to download too much information at once.
cl_rate is a command which controls how fast you send info to the server; so naturally if you lower it then it will make you appear laggy to others since the server will not know exactly where your real position is. However, you will still see things normal if you keep your rate high. That is why cl_rate is locked to 9999. cl_rate is your upload, rate is download.
Hope that clears any questions up.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
ok...but that would mean its impossible to rate hax in ns. Is that right? If so i ll have to retalk with the guys who called us rate hackers...they told us that it was neraly impossible to shoot us because we had set our rates to 5000...and that they wont play against cheaters...but if it is impossible to do it...what sense would that make?
I'm not sure. Cl_cmdrate is unlocked, and it controlls the number of updates you send to the server. If it's set absurdly low, then it might be a problem for other players. However, your "reflexes" over the net will also be dulled so much (you'll tell your client to fire or move, which then has to wait for the next packet to send out to the server) that it may be more of a handicap than an advantage.
However, setting your rate variable to 5000 should in no way be exploitive. Setting cl_rate, however, may be exploitive, depending on if it's been locked or not. I'm not sure, but judging by what people have said about it, it may not "dull your reflexes" as much as cl_cmdrate would by being set low.
in my config its at 55
i have a cable modem. is that too low?
in my config its at 55
i have a cable modem. is that too low? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
cl_updaterate and cl_cmdrate are not exploitive commands.
Having a bad cl_cmdrate increases choke. Dunno about you, but a high choke is worse than a high ping, by far and large. It will keep any of your shots and bites from registering.
Having a bad cl_updaterate will increase latency. Lag sucks. Keep good update rates.
Lowering either of these commands could potentally make you a tougher target to hit... but it will not be nearly as big as a disadvantage as not being able to kill anyone else.
Therefore it follows cl_updaterate and cl_cmdrate are non-exploitive. You can set them to whatever you want.
Anyone who claims you are rate hacking doesn't know what he is talking about. You can just ignore them, because they are ignorant.
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> the ns dev team say they will do a lot of things
put cl_rate 1000 ingame and ask someone what your model looks like<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
If you change your cl_rate in game, and check your cl_rate again by typing in "cl_rate" it will say your cl_rate is 9999.
So is the console bugged as well? Honestly I don't believe you, it's more likely that you guys were trying too hard to spot something wrong than the console be bugged too.
Mine doesn't D: it stays at whatever I set it to, and it keeps it like that when I change server =/
it isn't hard to spot what's wrong with cl_rate 1000