Open bs321 opened 4 years ago
Aimbot has not been touched if I remember correctly
@BlackYuzia any idea about the AntiAim part?
@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
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.
Fix it yourself or wait. Don't just complain.
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.
Right, thank you for clarifying.
//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
@bs321 76561198266718297
didn't use cheats/hacks?
@BlackYuzia Are you serious? Of course not. Please go through the demo.
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?
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?
Why would you want to do that?
Why would you want to do that?
I want check 100% what angles really have in a normal player
and cheater with AA in some array of ticks.
I think my current method for detect AA have troubles.
That makes no sense, OnTickEnd already just runs every* tick with the current tick. + or - anything makes no sense.
I was break this game lol
PS: that not AA
I installed latest version on overwatch bot. It says i need to install phynton? Do i really have ti install? Drop a link please from there i can download. Thanks
Do not hijack other issues, create your own. You only need it for the NodeJS build tool for running in Steamworks
-Mode which is optional. Everything is explained in the README, read it.
@BeepIsla did you want a joke? :eyes:
So, I think AA detector
fully suck.
I can't create good method for detect AA.
But I was found what I can check angles of players per tick. I get success results for ONLY ONE cheater (who really use AA). All clear players (or cheaters without AA) get 0 or < 20 detects.
Also other guys of this demo (and of demo by @bs321) I get clear results for guys who didn't use AA.
Sry and thanks guys
Regards Mantas
On 6 Oct 2020, at 17:48, Isla notifications@github.com wrote:
Do not hijack other issues, create your own. You only need it for the NodeJS build tool for running in Steamworks-Mode which is optional. Everything is explained in the README, read it.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
But I have some troubles.
So... @BeepIsla @bs321 and any other guys can you share with me demos with Rage or HvH (where cheaters use AA)
I need more tests now.
Oh yep. A few words about AA detector.
I want totaly delete AA detector.
But add new with name AnglesCheck
or something like this.
@BeepIsla and yep. Can you disable/delete current AA detector?
1e102761e81d191a02acdff926d58d009e7ad7cd
@BlackYuzia I can try you gotta let me know if what you are trying to detect is legit AA or rage AA
@BeepIsla Can you explain to me how I can add a new Detector? I can't understand how to :eyes:
Or I should just upload new code in to AA detector
and you do all the other?
@BlackYuzia I can try you gotta let me know if what you are trying to detect is legit AA or rage AA
I upload my "new" version in to my repo and will give you link. Wait a bit.
@bs321 you can download this branch or this file and replace old file.
Try run it. But I would want get demos for test by myown :eyes:
oh, I was forgot. @bs321 also change value of AA detects to 1000+
@BeepIsla I don't know how, why and how this work but this work fine :D
All AA Cheaters what I check really have AA and get >= 10K detects
.
I think we can wait feedback from @bs321 and if all is good I would create PR with addings a new AA detect method.
Also I has been started work on legit AA detects. I don't know did that can work the same but I try and test now.
@BlackYuzia Give me some time. I will run the demo through the updated version. I am having difficulties finding demos in which there was hvh with anti aim and stuff.
The legit AA, I don’t think it will help. Because in OW demo, you’re locked with one single POV and there is no way to check for legit AA. Even if a human were to inspect it, he wouldn’t know. You need to inspect it in 3rd person to give a verdict and since OW demos don’t allow it, I don’t think it is possible.
If anybody want would get a demo with Legit AA Cheaters I have one of Demo
This both 100% use Legit AA.
The legit AA, I don’t think it will help. Because in OW demo, you’re locked with one single POV and there is no way to check for legit AA. Even if a human were to inspect it, he wouldn’t know. You need to inspect it in 3rd person to give a verdict and since OW demos don’t allow it, I don’t think it is possible.
Yep, but if >50% was use this bot on one guy ... HE WILL BE BANNED :eyes:
I am having difficulties finding demos in which there was hvh with anti aim and stuff.
You can check demo from here if you want. I tested on this demo.
But if you find a new maybe this would be better.
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.