READ THE ENTIRE POST BEFORE REPLYING!!!
1. Instead of saying "You are not allowed to say this!", say "You are not allowed to say x because y!".
Just to make life easier.
2. URL's with "cubecraft.net" as their domain name should not be blocked.
If someone needs help on a CubeCraft topic in-game, you can easily link them to a location on the website (which usually covers everything).
3. Slashes "x/y/z" should not be blocked.
I know it's part of the link filter, but these slashes really don't need to be blocked for obvious reasons. Just block the line if it has a non-CubeCraft domain name in it.
4. Blocked words separated by spaces should not be blocked.
This can create some weird interactions, like "put a chest over here".
5. Unblock unicode characters.
It really doesn't help. If it blocks people from spamming unicode, it's not going to help because they'll just spam keyboard characters instead. If it blocks people from swearing, again it will not help. People will always find ways to bypass the filter, and the only way to prevent that is to downright mute everyone, so unless you're going to do that, don't even try. Just block the original word, and that's it. If people are going to swear in other languages, don't worry. Either hire staff that speak those languages (maybe post a "hey, we are looking for <language> speaking staff! Apply here <link>" on Twitter?), or use Google Translate. As a last resort, make it so that reports have to include a screenshot of Google Translate in their reports involving foreign languages.
How that would look like:
A huge percentage of Internet users don't speak English, so you're chasing away a huge playerbase, which coming to think of it, is bad for the CubeCraft economy.
6. Unblock words that don't need to be blocked.
These words include: OptiFine, Mojang, FNAF, Freddy, creeper, cape, and others
Sure, maybe those words can be used inappropriately (all words can), but it doesn't matter. Those words are perfectly legitimate and G-rated, and just because a small handful of people are misusing them doesn't mean you should block them! If someone is using these words, I can guarantee that it's most likely they're using it in an appropriate way. Oh yeah, some people are unable to put their own usernames in chat, despite their usernames not being inappropriate in any way.
The way it currently is, it almost gives staff an impression that they're lazy because they don't want to deal with an extra small handful of reports in case these restraints (see above) weren't there. So, they'd rather essentially apply large punishments to the innocent and rule-abiding majority.
Are you afraid that my suggestion will cause more rulebreakers? Fear not! We have reports for a reason! We have staff for a reason! We have staff application for a reason! Don't make these features become obsolete :(! It's not like CubeCraft would be suddenly flooded with rulebreaking if my suggestion gets added.
Please do not use the excuse "it'll result in more rulebreakers" to downvote this suggestion, unless you think it will cause a lot of extra rule breakers (and I mean a lot, as in the amount of hackers we have now)- and you must be able to explain why you think it'll result in the tons of extra rulebreakers.
Also, please give a valid reason before downvoting a suggestion, or your vote won't count.
1. Instead of saying "You are not allowed to say this!", say "You are not allowed to say x because y!".
Just to make life easier.
2. URL's with "cubecraft.net" as their domain name should not be blocked.
If someone needs help on a CubeCraft topic in-game, you can easily link them to a location on the website (which usually covers everything).
What are the rules?
Where do I report people?
Can I please have a Tower Defense guide?
3. Slashes "x/y/z" should not be blocked.
I know it's part of the link filter, but these slashes really don't need to be blocked for obvious reasons. Just block the line if it has a non-CubeCraft domain name in it.
4. Blocked words separated by spaces should not be blocked.
This can create some weird interactions, like "put a chest over here".
5. Unblock unicode characters.
It really doesn't help. If it blocks people from spamming unicode, it's not going to help because they'll just spam keyboard characters instead. If it blocks people from swearing, again it will not help. People will always find ways to bypass the filter, and the only way to prevent that is to downright mute everyone, so unless you're going to do that, don't even try. Just block the original word, and that's it. If people are going to swear in other languages, don't worry. Either hire staff that speak those languages (maybe post a "hey, we are looking for <language> speaking staff! Apply here <link>" on Twitter?), or use Google Translate. As a last resort, make it so that reports have to include a screenshot of Google Translate in their reports involving foreign languages.
How that would look like:
Name: RuleBreaker
Offense: disrespect
Evidence: <insert evidence of someone being impolite in Chinese>
Translation:
Offense: disrespect
Evidence: <insert evidence of someone being impolite in Chinese>
Translation:
6. Unblock words that don't need to be blocked.
These words include: OptiFine, Mojang, FNAF, Freddy, creeper, cape, and others
Sure, maybe those words can be used inappropriately (all words can), but it doesn't matter. Those words are perfectly legitimate and G-rated, and just because a small handful of people are misusing them doesn't mean you should block them! If someone is using these words, I can guarantee that it's most likely they're using it in an appropriate way. Oh yeah, some people are unable to put their own usernames in chat, despite their usernames not being inappropriate in any way.
What's your name?
My name is Freddy.
You are not allowed to say this!
How do I beat 20-20-20-20 in fnaf?
You are not allowed to say this!
Can OptiFine be used with Forge?
You are not allowed to say this!
My alt account got stolen! What do I do?
Have you contacted Mojang?
You are not allowed to say this!
The way it currently is, it almost gives staff an impression that they're lazy because they don't want to deal with an extra small handful of reports in case these restraints (see above) weren't there. So, they'd rather essentially apply large punishments to the innocent and rule-abiding majority.
Are you afraid that my suggestion will cause more rulebreakers? Fear not! We have reports for a reason! We have staff for a reason! We have staff application for a reason! Don't make these features become obsolete :(! It's not like CubeCraft would be suddenly flooded with rulebreaking if my suggestion gets added.
Please do not use the excuse "it'll result in more rulebreakers" to downvote this suggestion, unless you think it will cause a lot of extra rule breakers (and I mean a lot, as in the amount of hackers we have now)- and you must be able to explain why you think it'll result in the tons of extra rulebreakers.
Also, please give a valid reason before downvoting a suggestion, or your vote won't count.
Last edited: