BeepIsla
wrong anti aim and aimbot detection
Like the title suggests, anti aim detection and aimbot detection is extremely wrong. Getting false positives when someone is ducking in game using ctrl key or using +duck in console in warmup. Just noticed that I am getting false positives with aimbot as well after the last update.
@BeepIsla
About aimbot part - we just change death event to hurt.
hurt event has been call more times.
Maybe because that we can get more detects from clear players.
About AA part. @bs321 can you share demo with me?
Also. Give a screenshot with current results (detects and verdict)
About warmup false-positive. If that true I can return check of warmup for AS detect.
Right I forgot about the death event to hurt event change, the hurt event simply triggers a lot more often, the normal aimbot detection already had 1-5 or so detections but it wasn't enough to convict, the hurt event will have a lot more of those since it triggers more often. Might need to adjust the default config.
@BeepIsla oh yep. When I test aimbot detector on legit cheaters they get smaller aimbot detects like clear players. Lol.
If you ask why - they use triggerbot a lot of time.
//False Positive for Anti Aim
@BlackYuzia @BeepIsla http://www.mediafire.com/file/6v50cq43pvz70t0/3.dem/file
https://imgur.com/a/olCm5jE
run the demo through the bot with steam id 76561198266718297
have a look at the game as well then through the csgo client
Please fix the aimbot detection as well. It's extremely poor right now. False positives everywhere.
It's pointless for me to fix it. Your bot is falsely convicting clean players out there.
Overwatch cases are viewed by many people before the suspect is banned. A couple of false verdicts are likely not going to have any impact.
Sorry if I am being impatient but there's a possibility of someone getting convicted because same demo went to multiple people using OW bot, right?
Of course its possible, but false bans are always possible with Overwatch. Its Valve's job to make sure there are no false bans and to ban people automating Overwatch or just making the bot not work.
//False Positive for Anti Aim
Okey, I has been remove check AA if warmup period is enable. So, I get only 32 (65 - 33) false-positive results.
But I think this didn't full successfully fix. Kinda TYPO fix or something like this.
@bs321 so, if you duck AA detector was think what you are use AA?
@BlackYuzia I see. It's not only for warmup. Anytime you duck in game, it's detected as AA.
If you see the demo, you will see that person was ducking on box on Mirage looking at A main, so that palace guy cannot see him. That's being detected as AA on the bot. @BlackYuzia
Play a game and like sit somewhere holding ctrl (duck) and then run the game through the bot. @BlackYuzia
Yep, AA detector is suck big black dick.
I try fix that. Also I try create new method for detect AA. I check what really detect my AA and sometimes he find some EPIC shit. :eyes:
@BlackYuzia Yes. Thank you brother. Too many false positives. Aimbot too, not sure what's wrong since last update but something's isn't right there as well. You know how when someone is using AA their legs switch/flick, right? Hope that can help.
or something like someone is looking somewhere else, but shoots at target?
Already. That checks aimbot detector (actualy - check prev and current angles but ... something like this. yep)
But that sometimes can have false-positive.
@BeepIsla ~~tickEnd(tick)~~ OnTickEnd(tick) was return current tick or tick+1?
I can't find some ticks.
After everything within a tick has been parsed, it will fire with the current tick.
Some ticks just don't trigger this for whatever reason... Possibly because demos are 32 tick and matches are 64 tick?
For example:
I can't find ticks 45076, 45114, 45284
But I can find 44973, 45285, 45283
Some ticks just don't trigger this for whatever reason... Possibly because demos are 32 tick and matches are 64 tick?
yep, demo 32 tick
@BeepIsla so, I need add one tick (value + 1) or del one tick (val - 1) to get?