Flood protection

[Dersaidin]

I've seen a lot of chat spam on servers lately.

Theres people who /m you until you overflow and get dropped from the server, and theres idiots with binds who spam shit in mm1.

I think tremulous needs a flood protection, limiting the number of say, say_team, m etc commands a client can do in a given time.

Excessive commands are ignored, or gets the person kicked.

[Juno]

that happens to me in some servers and its dam annoying


i only have " Reactor is Down! Attack!!!"


and 2 lines of that isnt really enough if theres alot of players talking aswell as playing, so i do it about 6-8 times


tbh, that isnt really annoying, goes away quickly and is effective


but on some servers its almost as if ive been muted. if i press my bind say keys more than 3 times i cant use either chat for a few minutes

[Ksempac]

Every people i saw with binds use CAPS AND FLASHY COLORS AND LOTS OF !!!!!!


So unfortunatly we cant miss a single one of theses crappy binds : most of them are sent for no real reason at all ("OMG TYRANT !") or for stating the obvious ("Aliens are attacking !!!" when there is every single human defending the base).

That's why there is absolutly no reason to send it more than ONCE : We can clearly see them, and most of the time we dont care about them, sending them twice wont change that.

[Dersaidin]

tbh, that isnt really annoying, goes away quickly and is effective

It is annoying where I play.

I've been flooded off the servers heaps.

And its not effective, just annoying.

[Juno]

you have a point ^

it depends how many times they do it

if thers 6 people doing it then yea, its annoying


where do you usually play?

[^Black]

yea, maybe someone should make a !mute admin command.

wait...

[Lava Croft]

As if your team will even react to you saying OVERMIND DOWN - ATTACK! just once.

[Quaoar]

Thing is, the messages scroll off too fast sometimes. I understand that it avoids clutter, and I am very grateful for it, but on occasion you have to finish something off before you can glance up and comprehend a message, and by that point you'd need to open the console to look at it. At least giving it another shot wouldn't be too terrible.

[rasz_pl]

but on some servers its almost as if ive been muted. if i press my bind say keys more than 3 times i cant use either chat for a few minutes

R1CH build /me thinks
DB@ mostly

[Paradox]

This is completely off topic, but i would love a /me command, same as the one in IRC:

/me ate a granger
Paradox|SST+| ate a granger

[Undeference]

From a comment in src/game/g_admin.h:

Code Select Expand

* 2 - cannot be censored or flood protected TODO
The flag is there... but the functionality is unimplemented. That doesn't seem like a top priority, but eventually the code will probably be written.

[Dersaidin]

Bump it up the TODO list since people can use it to flood you OFF THE SERVER :<

[Taiyo.uk]

Auto-kick (or mute?) when maximum number of characters per unit time is exceeded in chat, team chat and pm? Floods spew hundreds, sometimes thousands of chars into the game every second whereas even fast genuine chat only send tens per second.

If the mute or kick comes before the majority of the flood then this could avoid overflow disconnections?

[kevlarman]

Auto-kick (or mute?) when maximum number of characters per unit time is exceeded in chat, team chat and pm? Floods spew hundreds, sometimes thousands of chars into the game every second whereas even fast genuine chat only send tens per second.

If the mute or kick comes before the majority of the flood then this could avoid overflow disconnections?

you mean like this?

[Undeference]

Perhaps auto-mute, but there are (or will be -- I should really start submitting my patches) mute votes and admins who can !mute. A better implementation actually prevents flooding.

If you attempt to send more than X messages in Y seconds, flood protection will kick in for Z seconds. When flood protection kicks in and when someone tries sending a message but would be prevented, they get a nice little message saying that their last message was not sent because of flood protection.
Every time a message is sent before the flood protection period ends, the period is either reset or extended.

A count of floods could be kept so if someone keeps trying to flood, they get muted.