The old rule display (a forum announcement) was inefficient, users had no way to tell if rules were updated and we had no way to see if users read the rules.
When you first join the forum (or when you first see the new system) you'll be shown a welcome message explaining that you need to view the rules, like so:
After viewing the rules via that link the message will disappear. Then whenever the rules are updated the message will come back including a summary of the new rules:
If you have any problems or feedback let me know in this topic.
You can access the rules at any time via rules.mcf.li and you can find the sourcecode (and raw rules) on github.com/minecraftforum. We'll be adding a link to the rules for users to find at all time at some point in the future, still working out where it will fit best.
Hopefully this new rules system is much better for users
Profanity is still not allowed (as in, please do not, but we won't warn you if you do) and we no longer will we warn for it. Any attempt to circumvent the filter will result in a 2 point warning.
I'll post a topic with all the words soon; adding them at the moment.
Side note: if you edit a post containing profanity it'll mess up, you'll need to delete the profanity tag and re-type the word in.
Wait, so we're just strongly advised not to curse?
No, we can't cuss period because we'd have to bypass the censor to do so which is against his cliche rules. so, basically, the filter option does nothing and is probably meant to quell the overwhelmingly negative response to his rules.
Quote from Rules »
No hoaxes - this includes sightings of Herobrine.
"As of today me and twenty other dudes decided that Herobrine is not family friendly. You'll get an option to turn Herobrine sightings on and off."
No, we can't cuss period because we'd have to bypass the censor to do so which is against his cliche rules. so, basically, the filter option does nothing and is probably meant to quell the overwhelmingly negative response to his rules.
Evading with the filter is probably going to be doing something like putting spaces between the words (like t h i s.)
Cussing is blocked for people without the censor. Even though I turned my censor to "show profanity" and it won't work.
unfortunately there's no proper way for me to do this, so yeah, it has problems like that it would be nice if people were just happy not swearing, but nope! So yeah, we suffer from the scunthorpe problem.
So yeah, we suffer from the s[profanity="[profanity="[profanity="cunt"]"]"]horpe problem.
Interesting that we can write "s[profanity="[profanity="[profanity="cunt"]"]"]horpe"
ed: this is not looking too good either =/
...so I guess bypassing the filters is what we need to do to write shitsu and scunthorpe...Incidentally, I turned off the filter but I'm still not seeing the tagged words.
Profanity is still not allowed (as in, please do not, but we won't warn you if you do) and we no longer will we warn for it. Any attempt to circumvent the filter will result in a 2 point warning.
I'll post a topic with all the words soon; adding them at the moment.
Side note: if you edit a post containing profanity it'll mess up, you'll need to delete the profanity tag and re-type the word in.
Crisis averted.
Now the RP section can go back to our sex racism swear and general unpleasant things that add depth to bad guys.
Rollback Post to RevisionRollBack
It has been since time immemorial that man has looked to the stars in wonder, so I ask you, how can going to them be anything but an extension of a will older than any of us? It is our very nature to discover, and to lust for knowledge, you accept this but doubt the nobility of working to the stars?
Eh, this filter seems pretty poorly written... double-filtering already tagged stuff and not recognizing empty bbtags kind of indicates it should be filtering later on in the process of converting bbcode to html, if that's possible with IPB. Maybe there's something better out there (or someone could whip something up in JavaScript, even)?
Eh, this filter seems pretty poorly written... double-filtering already tagged stuff and not recognizing empty bbtags kind of indicates it should be filtering later on in the process of converting bbcode to html, if that's possible with IPB. Maybe there's something better out there (or someone could whip something up in JavaScript, even)?
it's a problem with IPB. The options are either:
use a content bbcode, like: [profanlty]word[/profanity] or use an option bbcode: [profanlty="word"], the latter is what I'm using now because although it messes up in edit the first messed up even more (it was change a bunch of stuff in the post).
The solution I have is using Javascript; the problem is the fault of those that demanded an optional filter. There is no built in function for it and unless they want to wait weeks/months for developers to get around to it (there's a huge queue) we'll have to stick with the current client side solution I hacked together.
The "perfect" option is to filter "word" into "", which is what I would like, but apparently everyone needs the option to choose, so we have this :)The only plausible solution is for me to have javascript that also removes profanity from quotes, but I don't want to do that because it's messy. Modifying posts input is absurd; display is fine.
In any case if I do need to edit and the profanity tag is put to use, I just remove the old tag and all of that and let the forum take control and add a new one. Otherwise it'll mess itself up by either not working by taking on more tags.
It's not ideal, but it works for me. And it works enough for what it does.
The old rule display (a forum announcement) was inefficient, users had no way to tell if rules were updated and we had no way to see if users read the rules.
When you first join the forum (or when you first see the new system) you'll be shown a welcome message explaining that you need to view the rules, like so:
After viewing the rules via that link the message will disappear. Then whenever the rules are updated the message will come back including a summary of the new rules:
If you have any problems or feedback let me know in this topic.
You can access the rules at any time via rules.mcf.li and you can find the sourcecode (and raw rules) on github.com/minecraftforum. We'll be adding a link to the rules for users to find at all time at some point in the future, still working out where it will fit best.
Hopefully this new rules system is much better for users
Profanity is still not allowed (as in, please do not, but we won't warn you if you do) and we no longer will we warn for it. Any attempt to circumvent the filter will result in a 2 point warning.
I'll post a topic with all the words soon; adding them at the moment.
Side note: if you edit a post containing profanity it'll mess up, you'll need to delete the profanity tag and re-type the word in.
Post w\ord? Add bbcode in the middle of the word:
All manner of things. All of which will result in an instant 2 point infraction
Yes.
"As of today me and twenty other dudes decided that Herobrine is not family friendly. You'll get an option to turn Herobrine sightings on and off."
Evading with the filter is probably going to be doing something like putting spaces between the words (like t h i s.)
Cussing is blocked for people without the censor. Even though I turned my censor to "show profanity" and it won't work.
/test
http://www.shitsu.in...itsu/shitsu-dog
unfortunately there's no proper way for me to do this, so yeah, it has problems like that it would be nice if people were just happy not swearing, but nope! So yeah, we suffer from the scunthorpe problem.
Interesting that we can write "s[profanity="[profanity="[profanity="cunt"]"]"]horpe"
ed: this is not looking too good either =/
...so I guess bypassing the filters is what we need to do to write shitsu and scunthorpe...Incidentally, I turned off the filter but I'm still not seeing the tagged words.
yeah, unfortunately Nobody will warn you for bypassing the filter for legitimate reasons. I recommend:
Alt + 0173. Soft hyphen [profanity="fuck"]s up censors 24/7
Crisis averted.
Now the RP section can go back to our sex racism swear and general unpleasant things that add depth to bad guys.
Welp, back to business.
My DeviantArt, so sexy
it's a problem with IPB. The options are either:
use a content bbcode, like: [profanlty]word[/profanity] or use an option bbcode: [profanlty="word"], the latter is what I'm using now because although it messes up in edit the first messed up even more (it was change a bunch of stuff in the post).
The solution I have is using Javascript; the problem is the fault of those that demanded an optional filter. There is no built in function for it and unless they want to wait weeks/months for developers to get around to it (there's a huge queue) we'll have to stick with the current client side solution I hacked together.
The "perfect" option is to filter "word" into "", which is what I would like, but apparently everyone needs the option to choose, so we have this :)The only plausible solution is for me to have javascript that also removes profanity from quotes, but I don't want to do that because it's messy. Modifying posts input is absurd; display is fine.
It's not ideal, but it works for me. And it works enough for what it does.
My DeviantArt, so sexy
you need to clear your browser cache