Original Post
Capslock control.
Hello, I thought of an interesting suggestion.
If we implemented a command that only ops, gms and so on woulb be able to use that would basically make any capslocked text turn into normal letter tourneys and betting servers would loose one rule and make them a bit more managable.
Something like /caps on/off.
If we implemented a command that only ops, gms and so on woulb be able to use that would basically make any capslocked text turn into normal letter tourneys and betting servers would loose one rule and make them a bit more managable.
Something like /caps on/off.
h
soooo
THE QUICK BROWN FOX ---> the quick brown fox or ---> The quick brown fox or ---> The Quick Brown Fox
how would we do this, some people like to capitalise their first letters, or using a capital letter when writing a name.
would every capital letter get decapitalised or every letter except the first one of the sentence etc
THE QUICK BROWN FOX ---> the quick brown fox or ---> The quick brown fox or ---> The Quick Brown Fox
how would we do this, some people like to capitalise their first letters, or using a capital letter when writing a name.
would every capital letter get decapitalised or every letter except the first one of the sentence etc
dreamy suicide act
Originally Posted by duck
I have no real grasp on coding, but what I was thinking of whas that if there were two letters after eachother that were capitalised, the second one would be decapitalised.
This will stop all the caps spammers that occur after someone wins in the bet servers.
Last edited by Lazors; Aug 23, 2015 at 09:01 AM.
Stay Fluffy My Friends | I do loans and shit
Founder of [ROT] | Destroyer of Anus
Founder of [ROT] | Destroyer of Anus
This isn't needed since OPs already have the power to enforce their rules and deal with such ordeals manually, but I like this idea, especially since it doesn't have to apply to all hosts and is an option.
But why not just have a command to control spam in general?
/spamcontrol; <no two consecutive letters can be uppercase> and it would also change the current flood kick system to something with more restricting variables (no same lines of text x times in a row within y seconds)
But why not just have a command to control spam in general?
/spamcontrol; <no two consecutive letters can be uppercase> and it would also change the current flood kick system to something with more restricting variables (no same lines of text x times in a row within y seconds)
BAD LUCK
