Couldn't you just control movement server side?

to counter speed hacks, i would do something like this.

Although i work with .net, which has threading support, and would make it easier.

in some form of server loop(a seprate thread in vb.net, maby part of the server loop/another timer):
10 second delay, or even longer
send request to all clients for time

Client responce:
it includes seconds and minutes, and hours maby?
Do a check from last request to get difference, allowing for rollover, like 55 seconds, 2 min was last, and now its 25 sec, 3 min, a 30 second difference, now you take this difference, and something like

TimeDifference = (CurrentReponceDiff / DelayTime) * 100
which would be 300%
and lets say you want there to be a 150% maximum, for lag and such, anything higher and client would be banned.

lot less work with server, cause your not checking everytime they move.

Send packet from server to client
Both server and client start timer

Send packet from server to client
Both client and server stop timer
Client sends server the deltaT

compare with server's deltaT

If it's significantly different, mark the client

You could easily just do it once every minute or two. It doesn't have to be often.

I have no idea how threading would help at all, unless you are using the thread in a completely stupid manner like spawning a new thread just to send the packet after an elapsed amount of time.

threads are not bad. in vb.net, you would do something like




or if you were more oop


threads reduce the strain on a program and can speed things up alot, but you run into lots of problems accessing forms with other threads and stuff.

It's not vb .net, however the concept is the same. Shut up Matt.

Ban me. Mr. I don't give a [edit] anymore cause Willam don't give a [edit] and I can't figure out how to enforce rules because the owner of the site doesn't do it.

Don't start going off-topic.

If you've got something to say, keep it to Pms and Ims.