[Emmet_]

Quote:

Originally Posted by jakejohnsonusa Well done! +1 for the nice work!

Quote:

Originally Posted by pds2k12 Looks nice, but I didn't test it, I just looked at the code

Quote:

Originally Posted by Strawhats This can come in handy, so i won't have to script it myself

Quote:

Originally Posted by FailerZ Very useful thank you

Thanks.

Quote:

Originally Posted by [uL]Pottus I find it funny that the guy who named it "airbreaking" used the wrong variation of the word :P anyways I would like to try it but this won't work on my server without significant alteration unfortunately so I can't really give you feedback of it's effectiveness right now.

That's true, lol. "Airbreaking" doesn't make any sense, how can someone break the air? lol.

Quote:

Originally Posted by [uL]Pottus You know Richie, it really takes a lot of patience to build a AC you just can't tell what will happen until you try. I'm sure Emmet built this good but to perfect takes time and it's a absolute must to have a public server to test on. What I do when implementing any new AC features is just report to get a feel if there is false positives. It takes while to develop confidence with any AC routine so I wouldn't throw this out but try and figure out why false positives are being thrown then try again until your confidence is high enough to have it autoban which could take a week or maybe never and you have to remove the check.

Thank you for your understanding. After all, I've released an airbreak detection method last year and it had way more bugs than this one, so I had to scrap it and start from scratch. It took me about 3 more tries but I've done it. :d

This is why that in most anticheat detections, it is good to have a variable that counts the number of detections, false or not. If the variable reaches a certain amount, ban that player.

pawn Код:

new g_AB_DetectCount[MAX_PLAYERS];

public OnPlayerAirbreak(playerid)
{
    g_AB_DetectCount[playerid]++;
    if (g_AB_DetectCount[playerid] >= 3)
    {
        Ban(playerid);
    }
    return 1;
}

@Richie©: Thanks for taking your time to report the bugs, I've worked on the script a bit and all of them should be fixed now (after 1-2 hours of testing and tweaking), sorry about that XD.