Page 2 of 2

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 07 Dec 2014, 18:49
by Omnix
I think i know how to deal with spam in the matter of being annoying to victim, if there's a way, when a player starts spamming chat should warn the sender that he tries to send too many messages and it would be considered spam, then if he doesnt stop the server would cut him off the game. If only there is a way to detect if a player is repateadly trying to break the cooldown period and then kick him for that. To prevent from warning and kicking a player which just types fast this warning could appear after 50 attemts to spam for example. What do you think about that?

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 07 Dec 2014, 19:42
by Krom
Manual ignore button/switch/command sounds like a better and more universal solution. So player can ignore anyones messages if they are offensive, not only spam attack ;-)

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 07 Dec 2014, 21:01
by pawel95
Manual ignore button/switch/command sounds like a better and more universal solution. So player can ignore anyones messages if they are offensive, not only spam attack ;-)
That´s what I wanted to hear :D

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 07 Dec 2014, 22:08
by Omnix
I was just thinking about a meantime solution before bringing in the ignore button but i didnt know if that's a solution easy enought to be brought fast :P

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 08 Dec 2014, 05:36
by Krom
Easy enough solution for now is 500ms cooldown period. All other solutions are "hard" enough not to be implemented in RC5/Final without a proper testing ;)

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 08 Dec 2014, 17:40
by Ben
Plus, Lewin doesn't want to add a mute switch anyway :D

Re: Spamming private chat for a player to time out (exploit)

PostPosted: 09 Dec 2014, 05:15
by Krom
It's just a bigger risk considering upcoming release, but later on - sure, why not :)