-
Notifications
You must be signed in to change notification settings - Fork 46
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
SOCD detection #360
base: master
Are you sure you want to change the base?
SOCD detection #360
Conversation
Add, plz, statistics in output from |
fyi you don't need to close the PR over and over again, just forcepush to your branch to update it. |
Hi @b1az3, Thanks for the contribution! 1. I had a short discussion with the tournament admins, and I think we would need a bit more options for this feature. Like:
It will be up to the server admin to decide what level of SOCD detection to use. 2. We need some documentation about this feature. Nothing fancy, just a small description of the new variable, its valid values, etc.What do you think? |
build breaks qvm target, q3lcc requires variables to be declared at start of block. |
The current implementation erroneously reports joystick based movement as movement assistance. |
At this point it may be appropriate to name this something other than "SOCD detection" or "movement assistance", as it appears the specificity has been broadened quite a bit from that original aim. Wooting rappy snappy will trip the detection but is not SOCD, though it could arguably be classified as "movement assistance". Joystick movement also trips the detection but is neither SOCD nor assisted moving. Perhaps "non-traditional keyboard movement" is a more accurate description of what this algorithm detects. |
fixed
Thanks for reporting. Joystick stats should be fixed. |
Minor update of original PR.