feat: implement command rate limiter (#1524)
This commit is contained in:
@@ -156,6 +156,27 @@ accepts-transfers = false
|
||||
# threads. Disabled by default. Requires Linux or macOS.
|
||||
enable-reuse-port = false
|
||||
|
||||
# How fast (in milliseconds) are clients allowed to send commands after the last command
|
||||
# By default this is 50ms (20 commands per second)
|
||||
command-rate-limit = 25
|
||||
|
||||
# Should we forward commands to the backend upon being rate limited?
|
||||
# This will forward the command to the server instead of processing it on the proxy.
|
||||
# Since most server implementations have a rate limit, this will prevent the player
|
||||
# from being able to send excessive commands to the server.
|
||||
forward-commands-if-rate-limited = true
|
||||
|
||||
# How many commands are allowed to be sent after the rate limit is hit before the player is kicked?
|
||||
# Setting this to 0 or lower will disable this feature.
|
||||
kick-after-rate-limited-commands = 0
|
||||
|
||||
# How fast (in milliseconds) are clients allowed to send tab completions after the last tab completion
|
||||
tab-complete-rate-limit = 10
|
||||
|
||||
# How many tab completions are allowed to be sent after the rate limit is hit before the player is kicked?
|
||||
# Setting this to 0 or lower will disable this feature.
|
||||
kick-after-rate-limited-tab-completes = 0
|
||||
|
||||
[query]
|
||||
# Whether to enable responding to GameSpy 4 query responses or not.
|
||||
enabled = false
|
||||
|
Reference in New Issue
Block a user