[Feature] Togglable CheatCheck

[LNFFire]

Add a cvar to enable and disable the cheatcheck part of the plugin.

[7mochi]

In the meantime I have compiled the plugin based on the 1.2.1-stable tag with the requested changes. The reason why I don't push the changes to the main repo is because I was working on 2.0-stable and I'll implement the same in that version.
Could you test if it works for you?
LLHL + CheatCheck Changes | Works with amxx version 1.9.0.5294 or higher | Source code if you want to compile it yourself

Also, the 2.0-stable version has been finished for quite a while but I haven't released it yet because it has some performance issues for the players (a very small portion) and I haven't figured out why.
If you like, you could try the 2.0 version. New features
LLHL 2.0 Dev builds generated by Github actions

[LNFFire]

Oh great, ill test them both.
Thanks a lot!

[7mochi]

Np, let me know if it worked!
I'll leave the issue open until I implement it in 2.0

[LNFFire]

Nope it didnt. But a friend of mine did it somehow.
He even made it for the 2.0. So atm my server is running with the 2.0, will report to you if I see any bugs / performance issues.
Cheers!

[7mochi]

Glad to hear that! Thank you
Edit: I would appreciate it if you or your friend could do a PR if everything worked fine

[andreiseverin]

@7mochi Hi,

I went through the code and for the OpenGF32 detector there's an issue. I have tested it using the actual cheat. The problem is that every command as wh aimbot etc are caught by the cheat buffer and the client_command part won't see them as registered commands even if they are written by the player in the console.
I solved this by forcing players the following commands and check if the buffer sees them as actual client commands. If not, the player is cheating (the cheat buffer catch those commands)

Cheers!
teylo

    client_cmd(id,"aimbot false;");
    client_cmd(id,"aimbot off");
    client_cmd(id,"aim off");
    client_cmd(id,"wh false");
    client_cmd(id,"wh off");

[7mochi]

@LNFFire a bit late but this will be implemented in 3.0 which will be released soon when #50 is merged