Notpron Forums

Speed hack. Seen 5 today and several yesterday. Is this a bug? - maybe players getting keeper speed? A number of new players as well as clan members have had this. I guessing it's a bug. It happens quite a lot.

If it's a bug, it's causing big problems.

Two minutes after the top post , I log on and see another one.

yeah it looks like their lagged but they deffinately are moving faster then everyone else. i was running side by side with a team mate who was doing it and he was moving atleast 1 1/2 my speed

this has something to do with lag, i've seen this happen a lot in Red Orchestra, basically no one in the server can move and on the screen it says Speed Hack Detected, i've also heard about this happening in other gametypes as well like ons and assault. this started happening ever since i updated to the new patch

well this is probably a cheat to make yourself much faster. so when the game detects that you are lagging quite fast across the map, it impedes you
i had it yesterday, 500 ping or so, was uploading something, then i became really fast (lagging), and the game took me back and didnt let me move

There is a way around this.
You can disable speed hack detection by going into the ut2004.ini (guessing it's a different file in the deathball/system folder and changing:


(taken from JB bug fix list)

I seen it both ways - (1) speed hack detected player can't move. (2) player just plays with increased speed.

With the server speed detect off - you only get number 2.

I've seen this as well, and I don't think its a random thing - far to consistent for that, and people seem to travel about twice as fast

Saw it in Alien Swarm yestaday. It dosn't seem to be DBall specific, more likly a server or patch issue.

I also find it amazing how every speed hack user I've encountered only got 2k4 "yesterday".

Because they're fakenicking?

Meh..this stuff is lame >_< needs patching :<

Any news on this on Atari forums or anything?

ShockerZ wrote: There is a way around this.
You can disable speed hack detection by going into the ut2004.ini (guessing it's a different file in the deathball/system folder and changing:

Code: Select all

[Engine.LevelInfo]
MaxTimeMargin=0.0
TimeMarginSlack=0.0
MinTimeMargin=0.0

(taken from JB bug fix list)

Actually it's from the UT2004 Server Admin mailing list. I applied that at Epic's suggestion once people started seeing the false detects. There is a beta patch out now though. I may apply that to the server to see what it helps.