wrote:

so with other words, custom wallhacks are nto detected?

What do you mean by 'custom wallhacks'?edit: if you mean wallhacks made by anyone out there, its possible to detect them without any software change.

wrote:

custom = non public wallhacks - ergo you don't know it exist.

When a player using that hack joins a server protected by this anticheat, even if he registered, the anticheat will get feed by their current processes running, and if there's a confirmed new hack, that one is added to the database. The player playing is kicked right away, and a message is shown on the console.

wrote:

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

No. The list of process running is verified carefully and its not automatic task. Its not only the name of processes itself, also other information on the executable file. So if that matchs a hack then its added to the db.

wrote:

does it need to know the hack or how its structured?

I dont need to know how its structured (if you mean made). All i need to know is that its running and in use, and how to know that.

what are the chances that you do not detect a cheat over the time?