Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Amministratori 
client.connect 91.200.101.83:28066
The server flooding protection is supposed to weaken DDoS attacks.
Say the client is configured to send its position to the server every second.
The server might have to do a lot of work when it receives position data, so a client could modify his game to send its position a lot more regularly, to spam the server.
Flooding protection attempts to protect from this by simply ignoring packets sent too quickly.
Keep in mind that the rate at which the server receives packets from clients is nondeterministic (e.g.: your ping spikes to 1s and back to 30ms - the first packet might take a route that's way longer than that of the second packet, meaning they might arrive shortly after each other).
Assuming flooding protection is properly done (you never know ;)), a warning like this might be caused by someone trying to DDoS your server via client packet spam or by players that have ping spikes.