Where are you going? I would like to have a longer conversation with you.

Well, all I really need are server operators willing to host it. After going over the release I've just done, there are WAY too many bugs in the way I've coded it. Linker was nice enough to point out some signficant flaws, and another way to detect HM2.

The version above will expire midnight today. I'm going to build a more monolithic system for this cheat detection to minimize any disabling things. I'll have some time starting Thursday to make 1.1b.

There I hope to rewrite the server auth portion to be signficantly more active. I think communication between client and server should be about 9 times faster then it is now(once every 20 seconds, versus 3 minutes). A better authentication cypher system, somewhere around 30 steps instead of 3, with a much larger root code base(currently the root code is pretty static). I'll see about adding Linker's HM2 detection method(it might be a tad high in respects to server processing power).

Personally, I'd wait until I finish 1.1b before loading it onto any non-testing servers.

Im interested in this as well. I will keep watching this to see how things are coming along. Im not a big fan of DT or its creator, so this is a great idea. Keep up the good work.

Yup Screw rodent .

A few questions about it. What will the restrictions be? Will weapon, base and terrain skins be allowed? Im kinda curious on what all its going to block out.

Well, see, I'm doing this entirely in T2 script. I can't really do verification testing on any of the skins, and I really don't care too much about skin changing.

I have to come up with ways to detect hacks in script. HM2 isn't too difficult. I have some ideas on stopping script based locators. Unless I figure out some way of verifying textures, things like ClearWater and clan weapon skinpacks will still be useable. Model change packs like Purple which require CRC spoofing, I'll look into.

I'm looking at stopping the major advantage giving hacks first, after that I'll look into some of the more obscure stuff. It will finally come down to if it is possible to add detection in script. I don't have much time to work on this, and thus progress is slow, I still have some bugs with the HM2 detection to resolve.

I've done quite a bit of research into T2 based hacks. The really major ones are HM2(autoaim, IFFs, nofog), locators(IFFs), f_ck missile(lets you fire off massive amounts of missiles per second), Purple(replaces models with very bright purple ones). In the middle are texture hacks like clearwater(makes water fully transparent). On the non-important end are things like Boot's autopoints(requires they be in your team's sensor range), auto-missile(worthless IMO), auto-flare(just as worthless as auto-missile).

I also develop and analyze hacks I have scripted myself. I mainly develop them to see what is possible, and the best way to stop them.

So, im gathering you just want to block out HM2 and interpolate and not some of the things that DT blocked out that people were unhappy with. Im willing to run this on my server to test it out with my team. Any chance of getting a more recent copy since the last one expired March 21st?

you can use getcrc() to find the crc of a file, or some command along those lines.

and when do i get a chance to test and destroy this new version?

Well, I'm working on it. It might be a few more weeks though, I'm somewhat busy with school and having a social life. I might work on it during lecture or downtime in classes(on my notebook), but I can't do any testing(T2 requires 12 MB VRAM, my notebook has 8 MB).

Im still watching this topic hoping for an update.

I'll tell you know that you can stop checking until after May 10th. I have AP tests coming up in Calculus, Physics, and American History and they will be done on May 10th. After that I might have a chance to work on it.

muhaha i take US history AP in sophmore year!!! MUHAHAHAAHHAHAAH yea... most other high schools is junior year... too bad i'm failing that class... but anyways... looking forward for the new version so i can get to defeat the system.

Yeah, I know you will. I'm thinking I'll probably restructure the whole system yet again in 1.2 making the client portion act like a dumb terminal without any idea how to stop cheats by itself and is told by the server what to do through a signed command system. That will be hard to manipulate, and even harder to see what is going on(provided I use some nice strong cyphers). Additionally, it won't ever need updating assuming I make the encryption system complex enough.

HECK YEAH!!!!!!!!!!!!!!! I cant wait!!

Have you considered having a shared ban list with a ban method based off the GUID?