Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add +klook detection #213

Open
MaxsStee opened this issue Jan 14, 2025 · 4 comments
Open

Add +klook detection #213

MaxsStee opened this issue Jan 14, 2025 · 4 comments

Comments

@MaxsStee
Copy link
Contributor

The +klook is binded to the insert key by default, which is obviously used by nobody, and probably is not known about by even most seasoned players. The insert key is only really pressed by cheaters to open up their menus. We could use this but I'm not very too sure how to implement this. Obvious way would be to just ban anyone who uses +klook, but I'm kinda worried about the fact that there will be a "BAN ME" button right on players' keyboards, even if they aren't cheating. I'm interested to know what others think about using this.

@aussyspitz
Copy link

The +klook key could easily be bound to another key could record/notify number of times +klook is sent and give an option to set kick/ban on x number. Would be nice if it could be programmed so that every time they use +klook server sends them a different command instead like +inspect (force weapon inspection) or something else

@MaxsStee
Copy link
Contributor Author

MaxsStee commented Jan 14, 2025

You might misunderstand me, so let me be clear:

  1. The +klook dosen't make the menu show up, they just happen to be on the same button, so sending some other action like +inspect won't do anything
  2. Sure, the +klook can be unbinded altogether, but the point of StAC is to catch dumb people and scriptkiddies, not people with an actual brain to do so

Also, cheaters will press insert 2 times, because they have to close the menu, thus pressing +klook twice, so yeah it would probably be better to set the limit to at least two detections before doing anything.

@sapphonie
Copy link
Owner

Worth making a log-only detection for 👍

@MaxsStee
Copy link
Contributor Author

MaxsStee commented Jan 17, 2025

Worth making a log-only detection for 👍

Yeah, I was thinking about it too, totally worth doing it as a log-only

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants