Lag Exploiters
Flyingcow
Join Date: 2005-02-16 Member: 41451Members
Join Date: 2005-02-16 Member: 41451Members
Im not sure how many people do this, but i have seen interp commands and scripts posted on numerous ns forums....
itsa really unfair exploit because it practically makes the exploiter invincible. A non-default interp variable will cause a player's hitboxes to lag behind their player models.
the interp command should be disabled in the next patch.
+ any other command that allows someone to lag exploit
thankyou
itsa really unfair exploit because it practically makes the exploiter invincible. A non-default interp variable will cause a player's hitboxes to lag behind their player models.
the interp command should be disabled in the next patch.
+ any other command that allows someone to lag exploit
thankyou
Comments
I thought interp only affected the client.
But he is right, that you can exploit lag.
I'm sometimes called a warper because of my shared connection,
that happens if your upload-bandwith doesn't fit anymore to your netsettings due to p2p-ing, e.g., by another user or yourself.
Edit: I dunno if special scripts/programms can manipulate your upload and cause you to lag by pressing a key, but i really can imagine that it's possible.
As for interp:
<!--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-->
Taken from <a href='http://www.usaklig.net/rates.html' target='_blank'>http://www.usaklig.net/rates.html</a>
ex_interp:
Before I begin, Webster defines interpolate as the following:
Main Entry: in·ter·po·late
3 : to estimate values of (a function) between two known values
intransitive senses : to make insertions (as of estimated values)
You cannot be perfectly synced with the server at every instant in time because you only receive a finite amount of updates per second. For example:
This graphic depicts a linear interpolation of a circle. As the number of data points (updates) increases, the interpolated figure becomes more accurate. In Counter-Strike you could consider this to be a player’s position over the span of one second. The server’s view in this case would be a perfect circle. The client has to interpolate between two “true” packets.
This is where ex_interp comes in. A small increment of time exists in between each update that is left to half-life’s prediction engine. ex_interp sets the amount of time (in seconds) to interpolate in between each successive update. In the figure above, these small time intervals correspond to the straight edges of the figure. Because interpolation is done client side, it is not perfectly consistent with the server’s view of the game. Nothing is a substitute for actual updates from the server, but interpolation generally does a good job.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
basically meaning, interp is what you see not exactly what the server is seeing.
I cant remember the actual timing, but on the assumption its miliseconds, interp 0.1 means every 0.1 milisec you update player positions, lower means the players are in a closer to true location, the animations get a bit jerky tho.
If you don't like interp, email valve, ask them exactly what it does.... they wouldn't put something into their multiplayer games that makes people invincible... come on, is this a case of being beat alot and needing something, anything to blame?!
*Edit, the post above is what i get for going and making a cup of tea while in the reply screen*
/me gets rolled-up newspaper
<a href='http://www.foom.net/fortressfiles/netcode.htm' target='_blank'>http://www.foom.net/fortressfiles/netcode.htm</a>
most of the interp scripts used a value of .4
and if interp works the way you say, then making it higher will cause lag
lol
ex_interp determines the time the client interpolates between server updates. Oh my such 'haks'.
Were all those admins who were playing TFC before NS was around misinformed too?
Even in ns, afaik, it was considered as an exploit and locked, but ns-models move faster and many complained about laggy/misplaced hitboxes.
Consequently interp was unlocked to give any connection speed and netsettings the possibility of correctly placed hitboxes.
NS is faster and therefore the advantage due to unlocked interp was much smaller than the problems caused by wrong interp-values that don't fit to the updaterate!
The only thing i don't understand, why they don't lock interp again and let the game calculate its right values by using ex_interp=1/updaterate, because everyone can change his updaterate until the hitboxes are correctly placed.
If server doesn't send as much updates as set, you have to lower your updaterate ingame and ex_interp will be changed by the game again.
lol
ex_interp determines the time the client interpolates between server updates. Oh my such 'haks'. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Of course, it is easier to complaim about hacks then to improver skill.
From reading the article, I get the opposite impression. They call it an exploit because you sacrifice quality (getting a bit jumper game) for preformance. It says that is with a lower number, you get updates from the server much faster, and therefor the data you have is more correct. Since when is having the correct information for the server a exploit?
What next, everyone must us identical connections, have the same ping, and use the same computers so that everyone is the same? And when do we start telling people that they have to dummy down their aim, because if the have better aim, the they have an unfair advantage....ohhh wait, must people call those people hackers as a way of keeping thier ego up
alias "interp" "ex_interp"
"interp 0.05"
After joining a server, I found the PG had an incredible amount of "phase" sprites coming out of it- dropping my frame-rate to less than 1. Furthermore, the shotgun would not work- it would cycle through the reload animation and sound.
After asking about on IRC, I was told it was a recent attempt by the NS team to stop interp.
Huh?
<img src='http://www.jamesshuggins.com/i/web1/hammer_and_nail.jpg' border='0' alt='user posted image' />
(i.e. altered values for ex_interp can cause players to display in proximity on your client, when on their client they are a good distance away. You bite them, then on their screen it appears as a "50 foot" bite, gg another victim of ex_interping.)
always nice to understand how the enemy works.
just a side comment.
Oh, and I could definately see people using "lag exploits" by fooling with their rates.
Were all those admins who were playing TFC before NS was around misinformed too? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Nicely answered by:
<!--QuoteBegin-BobTheJanitor+Feb 18 2005, 05:59 AM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (BobTheJanitor @ Feb 18 2005, 05:59 AM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->
A looooong time ago there were exploits involving the interp commands that would throw hitboxes out of whack. We're talking long before steam even. Nowadays you'll only get two things by messing with your interp. Either jerky player models from your point of view, or slightly better hit registration if you know how to properly tweak your netcode settings in all areas, not just interp. Other than that, there's nothing exploitable about it. The problems that made it exploitable were, as far as I know, coded out of the half-life base code years ago.
<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
It's all a matter of time, "all those admins who were playing TFC <b>before</b> NS was around".
Back then, I believe there were possible ways to exploit ex_interp. We aren't back then anymore though but people often get stuck in their ways, including league admins. Some of the community failed to pick up on the fact that Valve fixed these problems a while ago.
These days, correct use of this command simply makes the models on the client screen correlate more accurately with where the servers knows them to be, assuming that the rest of the network commands are also correctly used.
alias "interp" "ex_interp"
"interp 0.05"
After joining a server, I found the PG had an incredible amount of "phase" sprites coming out of it- dropping my frame-rate to less than 1. Furthermore, the shotgun would not work- it would cycle through the reload animation and sound.
After asking about on IRC, I was told it was a recent attempt by the NS team to stop interp.
Huh? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Way back in June when I still played this game, interp would do that to me also, but I never had problems with my shots registering either, I took lower FPS at phase gates versus laggy hitboxes
always nice to understand how the enemy works.
just a side comment. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
No. You're wrong.
Seriously do you just make this crap up?
Rolleyes
ex_interp is reversed proportional to your cl_updaterate, so with a higher updaterate you would want a lower interp to keep the information you recieve as accurate as possible.
Lowering ex_interp will reduce the amount of "fake" frames that are displayed on your screen, making the information you recieve more accurate. At the same time you're recieving and displaying less updated coordinates than you are capable of, and without ex_interp to fill the gaps other players will appear to jerk around.
The possible "exploit" involving ex_interp is that if interp is set very high, interpolarisation will make you display other players infront of their actual position, giving you an advantage when for example firing on someone running around a corner (you see him before you should see him)... this is blocked, and ex_interp is capped at max 0.1 like someone said earlier in this thread...
Of course, this is all based on my experience (not a whole lot) and conclusions drawn from reading guides and descriptions of cvars. I've probably got it all wrong.. :/
[Edit]
Something I wonder is what the variables "cl_smoothtime" and "cl_vsmoothing" actually do. Can anyone clear this up for me pretty please?
My theory is that they are somehow connected to what ex_interp does, and should be changed when you change you interp. I'm not sure how and what they actually do though, and I hate being kept in the dark.
None of these qualify as hacks, just config tweeks, and if there is a config file in NS get used to them being around/used/exploited.
There however is good news... I saved A BOATLOAD by switcing to geico!!!!11111one
That is all,
SM5
ex_interp is reversed proportional to your cl_updaterate, so with a higher updaterate you would want a lower interp to keep the information you recieve as accurate as possible.
Lowering ex_interp will reduce the amount of "fake" frames that are displayed on your screen, making the information you recieve more accurate. At the same time you're recieving and displaying less updated coordinates than you are capable of, and without ex_interp to fill the gaps other players will appear to jerk around.
The possible "exploit" involving ex_interp is that if interp is set very high, interpolarisation will make you display other players infront of their actual position, giving you an advantage when for example firing on someone running around a corner (you see him before you should see him)... this is blocked, and ex_interp is capped at max 0.1 like someone said earlier in this thread...
Of course, this is all based on my experience (not a whole lot) and conclusions drawn from reading guides and descriptions of cvars. I've probably got it all wrong.. :/
[Edit]
Something I wonder is what the variables "cl_smoothtime" and "cl_vsmoothing" actually do. Can anyone clear this up for me pretty please?
My theory is that they are somehow connected to what ex_interp does, and should be changed when you change you interp. I'm not sure how and what they actually do though, and I hate being kept in the dark. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
No, the old exploit of interp was setting it low, to .01 for example, so that their hitbox would be behind the model. I think it was a bug, you could set it low and aim slightly behind the model and still hit. Now it's fixed, and interp is a totally legit command...
Crap
<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
No, the old exploit of interp was setting it low, to .01 for example, so that their hitbox would be behind the model. I think it was a bug, you could set it low and aim slightly behind the model and still hit. Now it's fixed, and interp is a totally legit command... <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Thanks for correcting me.
One the demo, you can see him empty a shotgun in 1 shortburst, a HMG in 2 shortbursts etc. ...
As some would call for "speedhack" and so forth, he just ansewered "and be glad i only use this".
By the symptoms, you can tell that this is a netcode exploit.
Although this time, the "hack" is obvious, i suppose that more subtlle tunings are more stealthy and just look like "skill".