No im using simple tibia clientIt kicks you because of spamming packets, you prolly use otclient to cause that, right?
timeBetweenActions = 200
timeBetweenExActions = 1000
maxPacketsPerSecond = 25
change this in config.lua to value that u want.
Code:timeBetweenActions = 200 timeBetweenExActions = 1000
So which one is correct?maxPacketsPerSecond = 25
change
Code:maxPacketsPerSecond = 250
try both. Play with the numbers, save the default with "--". some like thisSo which one is correct?
--timeBetweenActions = 200
maxPacketsPerSecond = 250try both. Play with the numbers, save the default with "--". some like this
Code:--timeBetweenActions = 200
I wont recomment doing that, this will kill your ot with more players instantlymaxPacketsPerSecond = 250
helped
why? if maxPacketsPerSecond = 25... and u put exura in f1.... You press f1 for 5 seconds you are kickedI wont recomment doing that, this will kill your ot with more players instantly
Can you explain how and why? So what is the proper way to remove player kickI wont recomment doing that, this will kill your ot with more players instantly
So you tested with 60 players but what if there is 200-400?Try
Code:maxPacketsPerSecond = 75
Im on windows not linuxiptables packet rate limiter might be what to look for.
Target input, tcp, 7172(game server) 25 packets/second.set packet rate limit via iptables
I have a packet rate limit (max. 10 per seconds) which is set by my internet provider. This is a problem if I want to use the AceStream player, because if I exceed the limit I get disconnected. Ho...unix.stackexchange.com
It might stop their spam without entirely disconnecting them
Thanks, great respondOTs 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?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.
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.what problem for exemple i can get with !Deathlist?