[Ejziponken]

Originally Posted by CowGod I ran into some csgo engine querks, so it probably won't be a thing for a while.

I rather u focus on anti aimbots

[CowGod]

Originally Posted by Ejziponken I rather u focus on anti aimbots

Yeah I really want to rework the aimbot detection, it's setup really weird to try and avoid false positives currently. I will be rewriting this in the near future.

[waylander3]

Is anticheat detects/banning players who use x2/x3 clickers on mouses?

[CowGod]

Originally Posted by waylander3 Is anticheat detects/banning players who use x2/x3 clickers on mouses?

yes they will get detected for autoshoot, it logs it doesn't currently ban.

[Nachtfrische]

Originally Posted by CowGod Generic flag, and yes if they had 1-2 consistant for like 20-30 then yes it is a hack/script and if they hit consistant 20+ on jump commands most likely using a macro.

Could you maybe create a log file for this?
So, let's say the AC says this:

[CowAC] UserX has been detected for Macro / Hyperscroll (42)!

First of all, what does the (42) mean?
Second, a log file would be good. Meaning that if someone has been detected for Macro / Bhop Script, the plugin creates a log file which basically shows the same thing that !bhopcheck showed.

Plugin detects Bhop Script -> Does sm_bhopcheck on player -> saves output in logfile

Of course, every other detection in a seperate file would be perfect as well, thank you!


Another thing, I've seen this today:

"UserY<156><STEAM_1:1:45551644><CT>" disconnected (reason "[CowAC] Turn off Bhop Assistance!")

The plugin kicked the user for bhop script, but it didn't ban him? Why is that?

[CowGod]

Originally Posted by Nachtfrische Could you maybe create a log file for this? So, let's say the AC says this: [CowAC] UserX has been detected for Macro / Hyperscroll (42)! First of all, what does the (42) mean? Second, a log file would be good. Meaning that if someone has been detected for Macro / Bhop Script, the plugin creates a log file which basically shows the same thing that !bhopcheck showed. Plugin detects Bhop Script -> Does sm_bhopcheck on player -> saves output in logfile Of course, every other detection in a seperate file would be perfect as well, thank you! Another thing, I've seen this today: "UserY<156><STEAM_1:1:45551644><CT>" disconnected (reason "[CowAC] Turn off Bhop Assistance!") The plugin kicked the user for bhop script, but it didn't ban him? Why is that?

I plan on making it log later tonight when I'm home from work, the 42 means how many jump commands were sent during the time they were in the air. Also it will kick players for b-hop assist if they get a macro detection 10 times. If they are scripting / hacking aka they are hitting a lot of 1 tick perfect to bhops then it will auto ban. Thanks for the suggestion I will do it when I get home.

[Nachtfrische]

Hey cow,

thanks for the help so far.

Together with our admins we found a huge bug which can kick people because of macro, even though they are not using one.

 [CowAC] UserZ has been detected for Macro / Hyperscroll (263)!

How to reproduce it?
"bind mwheelup +jump" to jump with scrolling. Then, go into water so that you are "swimming" on top. While your are swimming you can scroll infinitely and when you get out of water, it counts that as macro.

My guess is that when you're in the water, you're kinda "hovering" so the plugin detects that as the player being in the air and records the inputs. So when you get out of the water, it will print a warning and if you do it too often, it will kick you.

Is there a way you can fix that?

Thanks!

[CowGod]

Originally Posted by Nachtfrische Hey cow, thanks for the help so far. Together with our admins we found a huge bug which can kick people because of macro, even though they are not using one. [CowAC] UserZ has been detected for Macro / Hyperscroll (263)! How to it reproduce? "bind mwheelup +jump" to jump with scrolling. Then, go into water so that you are "swimming" on top. While your are swimming you can scroll infinitely and when you get out of water, it counts that as macro. My guess is that when you're in the water, you're kinda "hovering" so the plugin detects that as the player being in the air and records the inputs. So when you get out of the water, it will print a warning and if you do it too often, it will kick you. Is there a way you can fix that? Thanks!

Good find! Yes we can fix it, I will do it when I'm home from work.

[CowGod]

Added Logging!

[Nachtfrische]

Originally Posted by CowGod Added Logging!

Thank you very much, it looks really good!
Could you perhaps add the values from sm_bhopcheck into the logs, if a macro / script has been detected? Then we can look at the "raw" data in logs to verify that.