CensorShip
CensorShip
Important
This plugin has been updated to version 3.0 (working with 1.7.9/1.7.10 and should work with Glowstone on 1.8, but not tested yet). However I would love to get some support of you guys. To support me you can give feedback in the comments or spend small amounts of money.
Also notice, that the current version is completely rewritten and that there could be some bugs that I did not recognize yet.
CensorShip
This Plugin simply replaces custom words with other custom words, like replacing shit with blah.
You can say what action will be done with the player: kick, ban, tempban or none. There are also penalty-points the players get for using a forbidden word. They also can get muted. A new feature is that you can censor commands like /msg and /r
Adding words | How to start | Commands | Permissions | Configuration
Features
- replacing custom words
- banning/kicking players for using custom words
- adding/removing custom words via commands
- autobanning players for overusing forbidden words
- compact replacement (shit in shitty will be replaced)
- automuting for overusing forbidden words
- supports multiple custom commands
- also replaces words splitted by spaces, dots or commas
- mcbans support
- auto notification
- censoring commands like whispering (THIS is the first and only plugin that does this!!)
- censoring sign text
suggestions are welcome!
ToDo
- new developer API
- more to come
Please report any bugs you encounter. Also, please point out spelling and grammar issues. I am not a native speaker.
Next Update (Upcoming features)
- new developer API
- more in development...
@Bw2801
Getting same error, even on 1.4.2. Error with "?", "!", ".", "," characters. All of my I's are capital. For ex: my ign is mbt15, it will appear as my Ign Is mbt15. Thanks, i know your busy! Take your time!
@trainphreak
Thank you. I will fix this as soon as I can.
@Bw2801
Oops, guess I should read closer. There is no NPE. Here's the errors I'm getting though.
I am running bPermissions v2.9.24 and bChatManager v2.0.1.
When I run CensorShip as the only plugin on a clean install of CraftBukkit 1.3.2-R3.0, I get this: http://pastie.org/5362228
When I run it along with bPermissions and bChatManager, I get this: http://pastie.org/5362236
@trainphreak
Can you send me that error so I can fix it?
@Bw2801
Thanks. Much appreciated to your work
@mbt15
I will do my best as soon as I can.
I know your probably extremely busy, as much as I am, but can you please fix the plugin ASAP? Spams my chat log..! Thanks, and much appreciated with your plugin!
@Bw2801
Oh, yes please. For what it's worth, I was able to use the same trick with the ? to stop the ingame spam, and it replaces correctly, but I still get a NPE with every chat message.
@trainphreak
Very nice idea. But first I have to fix the plugin
Feature request: After a configurable amount of time has passed since a player gained penalty points, their penalty points go down by a configurable amount. This would prevent someone who said the wrong word one time last year to say it again, if they ever forget, without being banned. Obviously, this would also be able to be turned off for less lenient servers.
This plugin is completely broken.
- Broken on both 1.3.1 & 1.3.2 - On chat, over 9,000 errors popup, error: [Could not pass event AsyncPlayerChatEvent to CensorShip]
Windows
@mbt15
it works, to an extent. if they use a replaced with AND a "?", it wont the bad words still show up.
@mbt15
nice, but I'll try to fix it.
@minimonkeyble
Comment below :D
@Bw2801
For now, I found a solution with "?". Mark it as a "innapropiate" word, and make it replaced with "?". That will get rid of the errors.
i see other ppl have had the "?" issue.... is that issue only happening on 1.9.5? if so, should i try having 1.9.4 instead?
@Bw2801 yes, whenever i start the server after adding them they just disappear.
@ObsidianDragons
Do you have reloaded/restartet the server after adding the words in the yml file?
@Bw2801 I have tried to do it straight from the yml file like this:
and i have tried like this
neither of them worked so i tried from the client by doing: /censor add <word> <replace-with-word> but it wont stop giving me that error
@mbt15
I already noticed that error and I'll try to fix it.