[bruxo00]

Quote:

Originally Posted by NaS There should be a way to know which processes/files are looked for (for the player) before actually joining. For example, when the scheme is downloaded and illegal files/processes are found already, there should be a warning to the user before reporting it to the server. That gives them a chance to remove it before getting banned for a harmless vorbisFileHooked.dll or similar. You could make this exclusive to file modifications as those are more likely to happen accidently, as some people use ENB or FPS fixes or an installation with SP mods, vehicle models, etc. If they ignore that warning and proceed to join the server anyway, it's their fault for ignoring it. Also, process names are useless.

Quote:

Originally Posted by NaS There should be a way to know which processes/files are looked for (for the player) before actually joining.

Do you mean show to the player a list of files/directories/processes that will be scanned?

Quote:

Originally Posted by NaS For example, when the scheme is downloaded and illegal files/processes are found already, there should be a warning to the user before reporting it to the server. That gives them a chance to remove it before getting banned for a harmless vorbisFileHooked.dll or similar. You could make this exclusive to file modifications as those are more likely to happen accidently, as some people use ENB or FPS fixes or an installation with SP mods, vehicle models, etc. If they ignore that warning and proceed to join the server anyway, it's their fault for ignoring it.

That's exactly what it does. It connects to the server, scans the files and shows a message in case a file is forbidden/modified. If they connect to the server, it will simply say that the anticheat is not connected.

I don't know which files are "bad" or not, I'm not really in the world of SAMP cheating. The server owner is responsible for that. I'm sure that there are mods and other stuff that don't hurt the gameplay.

Quote:

Originally Posted by NaS Also, process names are useless.

Well, it's better than nothing. You say this because it's easy to change a process name, right? The only think I can think of to prevent this is calculate the checksum of every running process and try to find a forbidden one, the only problem is the load I would be putting on the system.