Hey GoD-Tony, I'd suggest adding some sort of simple cache to SMAC in order to reduce the likelihood of actions being logged and the punishment being carried out numerous times for the same instance.
I've seen things like this far too many times in my logs:
Code:
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_mode
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_mode
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:44:35: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:54:40: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:54:40: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:54:40: *** snip *** was kicked for command spamming: spec_next
L 10/22/2011 - 11:54:40: *** snip *** was kicked for command spamming: spec_next
I don't think it's very likely that the individual managed to reconnect multiple times within a second. I've also seen individuals receive multiple bans for a single convar violation on SourceBans. I'm fairly sure that the individuals are receiving multiple bans for the same instance since the timestamps on the bans are always the same. However, this appears to only occur occasionally and isn't as prevalent of a problem in comparison to the logs being constantly spammed out.
I hope you'll take my suggestion into consideration,
Thank you.