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 config option for disabling matchmaker violations #1051

Open
Askaholic opened this issue Feb 22, 2025 · 0 comments · May be fixed by #1052
Open

Add config option for disabling matchmaker violations #1051

Askaholic opened this issue Feb 22, 2025 · 0 comments · May be fixed by #1052

Comments

@Askaholic
Copy link
Collaborator

Askaholic commented Feb 22, 2025

The DDoS attacks can cause people who otherwise generally don't have connection issues to register matchmaker violations. We should add some config options to enable/disable violations entirely, and while we're at it we could add a config option to set the threshold for how many violations are needed to start triggering a matchmaker timeout, and how long it takes for violations to expire.

Proposed config options:

  • MATCHMAKER_VIOLATIONS_ENABLED default true
  • MATCHMAKER_VIOLATIONS_BAN_THRESHOLD default 2
    How many violations it takes before a ban (matchmaker timeout) is triggered
  • MATCHMAKER_VIOLATIONS_FIRST_BAN_DURATION default 600
    The first ban is shorter than the rest
  • MATCHMAKER_VIOLATIONS_BAN_DURATION default 1800
    How long each ban lasts
  • MATCHMAKER_VIOLATIONS_RESET_TIME default 3600
    How much time needs to go by since the last violation for the violation tracking to reset
@Askaholic Askaholic linked a pull request Feb 23, 2025 that will close this issue
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 a pull request may close this issue.

1 participant