• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Spamming spell kicks from server

SixNine

Active Member
Joined
Dec 12, 2018
Messages
442
Reaction score
40
Hello,
so if you have spell on hotkeys and you hold it it kicks you from the server due too spamming but because there is exhaustion="1000" i dont think that kick is needed. How can i remove it?

TFS 1.2
 
It kicks you because of spamming packets, you prolly use otclient to cause that, right?
 
iptables packet rate limiter might be what to look for.
Target input, tcp, 7172(game server) 25 packets/second.

It might stop their spam without entirely disconnecting them
 
Try
Code:
maxPacketsPerSecond = 75
So you tested with 60 players but what if there is 200-400?

iptables packet rate limiter might be what to look for.
Target input, tcp, 7172(game server) 25 packets/second.

It might stop their spam without entirely disconnecting them
Im on windows not linux
 
OTs have been hosted for over a decade without limiting packets per second at all and the servers back then were far less optimized than what TFS is now. If you increase that limit to say 75 or 100 it isn't going to hurt anything, as long as you have some sort of reasonable limit to prevent people from spamming your server with WPE it should be just fine. Also set a simple exhaust function in front of demanding player scripts (such as !deathlist) as even with packet limits, these scripts can still cause problems if people abuse them.
 
OTs have been hosted for over a decade without limiting packets per second at all and the servers back then were far less optimized than what TFS is now. If you increase that limit to say 75 or 100 it isn't going to hurt anything, as long as you have some sort of reasonable limit to prevent people from spamming your server with WPE it should be just fine. Also set a simple exhaust function in front of demanding player scripts (such as !deathlist) as even with packet limits, these scripts can still cause problems if people abuse them.
Thanks, great respond
 
OTs have been hosted for over a decade without limiting packets per second at all and the servers back then were far less optimized than what TFS is now. If you increase that limit to say 75 or 100 it isn't going to hurt anything, as long as you have some sort of reasonable limit to prevent people from spamming your server with WPE it should be just fine. Also set a simple exhaust function in front of demanding player scripts (such as !deathlist) as even with packet limits, these scripts can still cause problems if people abuse them.
what problem for exemple i can get with !Deathlist?
 
what problem for exemple i can get with !Deathlist?
Things like !deathlist query the database and are talkactions which means normally a player can use it as often as they like. This opens up the possibility for abuse if say a player was to mass log dozens of characters and spam !deathlist 100x a second. This problem is not just limited to scripts that run database queries however, there are many things you could have in your server which are demanding enough that when spammed excessively could cause lag. I seem to recall on the original 8.0 deathzot, admin death added in snow piles that you could click to gain snowballs. Some people set up scripts to spam these piles so fast it locked up the entire server. This is an extreme example on an ancient server that was beyond unoptimized but today we see action and exaction delays standard in the config of any server, TFS or otherwise, for this very reason.
 
Back
Top