wrote:

wrote:

wrote:

or with other words, any new process can cause you being kicked by it? Oo

The list of process running is verified carefully and its not automatic task.

seems so, so it does not detect automatically, just send info to developer and after some work flag as a cheat or not.

Yes, thats right. There could be an automatic way of doing so, but that implies more probabilites of error (and that could be worse). Other anticheats that take screenshots, their developers do verify those screenshots thats still a manual task.Anyway there's a list of cheats that are not detected by at least the noghost mod, but by this anticheat.Once the cheat is added to the db, that one cheat will be available for detection to every user.

or with other words, its a client hack that implements an anticheat based checking ram accesses of other processes if it involves q3, compares them to a signature database and allows unique id's for the users. (if I understood everything right, I am on lan since 4 days now after a whole week of lan at home, totally feel wasted)

Depending on the database of the anticheat this system can be either super efficient or worse then punkbuster.

Will probably give it a go at home, but im sceptical about this hacking an anticheat into q3, ofc you don't have to give out the sourcecode of it, but since you can just hook 1 hack into q3.exe this should kill every other hack instantly, same as a custom q3 exe disallows normal quake3 clients.

wrote:

3rd is not, though. This program doesn't modify the quake3.exe.

thats not what I meant, I mean, since its a hook for q3 you can only hook once, ergo cheats can't use their cheat if they hook the anticheat into q3.

You can have same effect way simpler if you modify q3 to disallow different clients, causing somebody to write a hook for your new q3. (which should be quite easy since you always have to give sourcecode to id besides using a hook like you did).

So after all, sceptical, will try it tomorrow at home.

maybe the banlist is too long?

wrote:

wrote:

3rd is not, though. This program doesn't modify the quake3.exe.

thats not what I meant, I mean, since its a hook for q3 you can only hook once, ergo cheats can't use their cheat if they hook the anticheat into q3.

You can have same effect way simpler if you modify q3 to disallow different clients, causing somebody to write a hook for your new q3. (which should be quite easy since you always have to give sourcecode to id besides using a hook like you did).

So after all, sceptical, will try it tomorrow at home.

This program is not a hook, its not altering the behaviour of the quake3.exe. I hope i understood your point. I was looking at the other posts here, and i'm not sure if i mentioned the banning that comes with this anticheat. Since there's a uniqueId for every client, you can ban and somehow not let them come back. There's a way to actually evade this ban but it requires something that not everyone will do often, so that makes this 'technique' quite effective.