stajs / procon-1 Goto Github PK

From dyn via https://forum.myrcon.com/showthread.php?8625-Team-Kill-Tracker:

Ban after X punishes in Y rounds or X punishes in current round. We often see people just grief over and over again. Being able to have the default in game kick for TeamKills at 7 but then kick for 3 or 4 punishes would enable people to get more teamkills if the rounds are longer and would only (hopefully) be punished for when they grief a bunch of people. Additionally, we have seen people get kicked for the default TK limit and then come back and TK some more until they are finally banned for BAN PLAYER AFTER # OF KICKS. These are the players we need to be able to identify and quickly ban out... even if it's only a 1 hour ban just so they can either cool off or find a new server. On the other end of it, if we have a limit of 5 TKs for kick that means gamers can TK 15 people until they are perm banned. Then on maps where TKs are bound to happen (Metro) getting the 3 kicks for TK is actually not that hard especially if the server is online for several days and, I think, it remembers that the gamer has been kicked previously.... so now we have a perm banned, probably non-malicious, player who has to appeal their ban.
Maybe kick after X punishes and then if the killer quickly (defined in time or rounds?) reconnects and gets Y more punishes issue a temp ban? Then clear this restriction / punishment and let them start over with a zero score after Z time.

Just trying to identify the problem users quickly and ensure they are removed. Also trying to ensure that if someone is banned it's just for a short (1-2 hours) duration so that we don't have to deal with the appeal. Usually these problem players are not regulars on the server anyway; they connect for an hour or two, rage and then get disconnected. It just is a bummer to apply kick after 5 TK to everyone because we have to worry about the griefers.

It will be easiest to support this via a plugin setting so I'll go for that first.

A further future step will be persisting the list somewhere (I need to find out how the sandbox plays with saving files to disk) so that you don't lose the list on restarting the server or updating the plugin. Also it probably makes sense to protect players on the reserved list.

A whitelist setting was implemented for #3, but this loses the list on a server restart. Would be better to persist it somehow.