Spring RTS Engine

[12:50:13 AM] <jaz182> lol
[12:50:14 AM] <jaz182> lol
[12:50:14 AM] * Channel message: <ChanServ> has muted <jaz182>



Brutal!!!

Chanserv mutes you for posting too fast. Don't do that then!

lol ^^

I like to be muted ... 1 mute per day is a minimum !!!

could've muted at the first lol, you could tell he was up to no good.

Ive learned that the hard way

So much for fixing the problem that has never really existed (lobby spam)

Lurk moar. It was absolutely hideous at times.

Licho, lobby spam was a nightly problem before chanserv got spam muting capabilities, however as a European (with American mods on after you) you would never have seen the issue before you went to sleep. There was no one on after me and deci for a long time and that's when the issues occurred.

Lobby spamming was an amusing annoyance in the late nights, but it never really did damage...

I'd really like a spring client based solution added as well. It's not really a good thing that a normal user using a normal spring lobby client can be banned by the spring server permanently for talking.

less automation more work for lordmatt!

also, betalord isnt working on the client right now iirc.

smoth wrote:It isn't that terrible to write, couldn't beta lord add a client side anti spam? It would remove all this crap that we always have to sift through on the forums... and it would definitely make the volunteer moderator's jobs easier.

+107

Ive suggested that so many times, but people says "you can still cheat when you make your own client!!!! OMGZ NOOOOOOO SUCKS"

The point was that you always need server side spam protection.

The point was not that client side spam protection is totally useless if there exists server side spam protection. They can - and should - coexist.

TradeMark wrote:

smoth wrote:It isn't that terrible to write, couldn't beta lord add a client side anti spam? It would remove all this crap that we always have to sift through on the forums... and it would definitely make the volunteer moderator's jobs easier.

+107

Ive suggested that so many times, but people says "you can still cheat when you make your own client!!!! OMGZ NOOOOOOO SUCKS"

It's irrelevant if you make your own client and cheat it, because the lobby server will still ban you if you exceed the restricted amount. The main reason why it would be nice if client prevented users from flooding is that nearly all our legitimate users use client, and many of them from time to time somehow manage to put enough data through with our default shipped client to activate the lobby server's emergency defense system and get permanently banned. In fact it's quite easy to do it on accident with copy pasting certain things and what not.

The lobby server shouldn't stop banning people for trying to overflow it, it needs to do that for security. What SHOULD be happening is our next layer up, default client, should prevent normal users from activating the low level security unintentionally.