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

SOCD detection #354

Closed
wants to merge 4 commits into from
Closed

SOCD detection #354

wants to merge 4 commits into from

Conversation

b1az3
Copy link

@b1az3 b1az3 commented Jul 31, 2024

  1. Automatic warning if the server detects SOCD (can be enabled or disabled by the admin by modifying k_allow_socd_warning)
  2. Command to check f_movement, summarizing for each player if the server detected anything. (ex: cmd check f_movement)
  3. End-of-game stats to show if SOCD was in use.

Copy link
Collaborator

@dsvensson dsvensson Jul 31, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oof... ought to be deleted instead, but separate PR, Visual Studio can import cmake projects nowadays.

.gitignore Outdated
@@ -31,3 +31,6 @@ x64/*
*.suobackup
*.VC.db
/.cache
/tools/vs/.vs/
/tools/vs/ktx/x64/
/tools/vs/x64/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe just skip these and delete tools/vs in a separate PR

@dsvensson
Copy link
Collaborator

And get rid of the useless merge commit. Just reset to origin/master and cherrypick your commit to that and force push to your branch.

@b1az3 b1az3 closed this Jul 31, 2024
@dusty-qw
Copy link
Contributor

dusty-qw commented Aug 1, 2024

My concern is that this, as it's currently implemented, is a bit opinionated and invasive and has a shaming/discouraging effect on the players.

I think instead of notifying the server that a player is doing something potentially wrong, we can report the strafing numbers in the end-game player stats in a more neutral manner. This will still allow tournament admins to make their own determinations, without you having to decide for everyone what the tolerable thresholds are.

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.

3 participants