You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
defaulttrue
MATCHMAKER_VIOLATIONS_BAN_THRESHOLD
default2
How many violations it takes before a ban (matchmaker timeout) is triggered
MATCHMAKER_VIOLATIONS_FIRST_BAN_DURATION
default600
The first ban is shorter than the rest
MATCHMAKER_VIOLATIONS_BAN_DURATION
default1800
How long each ban lasts
MATCHMAKER_VIOLATIONS_RESET_TIME
default3600
How much time needs to go by since the last violation for the violation tracking to reset
The text was updated successfully, but these errors were encountered: