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

Ricochet yt movement stuff PR #175

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

Ricochet yt movement stuff PR #175

wants to merge 5 commits into from

Conversation

sapphonie
Copy link
Owner

No description provided.

RicochetYT and others added 4 commits September 26, 2023 01:15
A lot of these will go unused, I never did feel like removing the ones that are unused. Feel free to!
@sapphonie sapphonie mentioned this pull request Oct 24, 2023
@sapphonie sapphonie changed the title Ricochet yt Ricochet yt movement stuff PR Oct 24, 2023
@RicochetYT
Copy link

I will note that there are more checks from both Oryx and Bash2 that could be implemented into this anticheat assuming that you could fix all of the false positives that occur with them and also adapt the checks to work in Team Fortress 2. I started work on this at some point, but I'm unsure if I still have that laying around.

@sapphonie
Copy link
Owner Author

I will note that there are more checks from both Oryx and Bash2 that could be implemented into this anticheat assuming that you could fix all of the false positives that occur with them and also adapt the checks to work in Team Fortress 2. I started work on this at some point, but I'm unsure if I still have that laying around.

My concern is with how ugly playerUsingController is, tbqh - it doesn't seem very robust at all, and i don't want people getting false positive'd

@RicochetYT
Copy link

I will note that there are more checks from both Oryx and Bash2 that could be implemented into this anticheat assuming that you could fix all of the false positives that occur with them and also adapt the checks to work in Team Fortress 2. I started work on this at some point, but I'm unsure if I still have that laying around.

My concern is with how ugly playerUsingController is, tbqh - it doesn't seem very robust at all, and i don't want people getting false positive'd

It was robust enough that I used it on a relatively active TF2 server that had controller users (at least 2, it's very rare) and had no issues with false positives, I even did testing myself and the only way you'd cause false positives is if you were to intentionally try to (join without a controller plugged in, plug a controller in and enable it, unplug the controller and stop using it, and plug it back in and start using it again), or be very unlucky. There's probably a better way, but I'm unsure of what it could be. playerUsingController could lead to easy bypasses (in the one check it's used within) because it's easy to just force the cvars on the client, but once again, the only other solution I can imagine is checking a player's viewangles for controller-like movement. That's beyond my understanding and experience though, you'd have to check for consistent acceleration when the viewangles are being changed, and I'm not even sure how well that would work.

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

Successfully merging this pull request may close these issues.

2 participants