BadWords
DO NOT INSTALL / UPGRADE TO VERSION 1.5 (or above) OF BADWORDS UNLESS YOU ARE RUNNING CRAFTBUKKIT 1.7 OR GREATER
An auto censor plugin that enables you to stop worrying about players swearing on your server. The number of warnings can be specified, as can the action that is taken once the warnings are expired (kick or ban).
For Portuguese speaking users, user AbsintoJPl has very kindly provided a video tutorial for Badwords. Thanks AbsintoJ!
Features:
- Individual words or entire phrases supported
- Regular expression support
- Banned words can be substituted for less offensive words
- Admin can define how many warnings players get
- Admin definable punishment (kick or ban)
- Case insensitive matching
- Only whole words or phrases are matched (i.e. "the" would not match in "tether")
- Admin can define who gets notified of profanities
- Nominated players (and op) can be ignored by BadWords
What's new?
- New to 1.52 - Hopefully fixed async kicking bug (Tickets 31, 33 & 34)
- New to 1.52 - Added UUID support (when you first start this version it will migrate your config file to using UUIDs instead of usernames)
- New to 1.52 - Added "reload" command to reload BadWords config
- New to 1.52 - Added "ignore.op" config option which makes BadWords ignore swearing by ops
- New to 1.52 - Added ability to tell BadWords to ignore swearing by nominated players
- New to 1.52 - Added optional auto-update of plugin
- New to 1.52 - Added "update" command to update plugin (if available)
- New to 1.52 - Added "banreason" config option
- New to 1.41 - Fixed bug in warning timestamps
- New to 1.40 - Added functionality that unbans a player when their warnings are reset
- New to 1.40 - Fixed bug that broke update checking enabling/disabling
- New to 1.40 - Fixed bug in "warnings" that would give remaining warnings for non-existant players
- New to 1.40 - Fixed bug preventing commands from being issued on the console
- New to 1.31 - Update checking can now be disabled
- New to 1.30 - Warnings can now be reset by an op
- New to 1.30 - Warnings can be configured to expire after a set time
- New to 1.24 - Fixed bug causing players to be warned of remaining warnings, when warnings -1 was set in config
- New to 1.23 - Fixed bug causing sporadic exception when adding or delete word from banned list in game
- New to 1.22 - Banned words can now be substituted for less offensive words
- New to 1.22 - Changed command from /bw to /badw to avoid collisions with other plugins (e.g. ButtonWarp)
- New to 1.2 - Various admin commands now available in game (see details below)
- New to 1.2 - Log censored messages
- New to 1.2 - Server logs and Ops are now notified when an update to BadWords is available
- New to 1.2 - Permission support
Is this working for 1.8 correctly? My server uses 1.8.7 spigot. It seems to load and it even seems to partially work. However, this doesn't seem to work on ALL of my players, just some. I don't understand why this is. They are not OPs, just normal players.
Do you plan on updating to 1.8? If so when?
@ManBeastPigDev
The problem with players not being kicked should be fixed in 1.5. I've also added /badw reload to 1.5
@ManBeastPigDev
This should now be fixed in 1.5
@ManBeastPigDev
This should now be fixed in 1.5
@LennartPS
This is now fixed in 1.5, you can specify whether ops should be warned & banned or not
@balmoraman
The plugin is designed to not be case sensitive, in what way does this cause you problems?
@zekigames08
SQL is a bit overkill for this plugin, it also adds a dependency that I'd rather not have.
SQL ?
Why do capital letters not count?
People with op will be banned with badwords... that is not very good
Video Tutorial on the Plugin
https://www.youtube.com/watch?v=WBxdd1qRiLU
Credits: (AbsintoJ/BadWords)
Can i add a Message which Word is wrong?
Example: You cannot say that "fu.."
@ManBeastPigDev @ManBeastPigDev @ManBeastPigDev
Hi all
Many thanks for the bug reports. Unfortunately, I don't have any available time to work on the plugin at the moment. I realise that not kicking is a major problem and needs resolving ASAP. I'll try and find some time as soon as possible and get a fix out.
Sorry! ChuckHunky
Error on kick attempt/fail
pastebin.com/iC7pR3dY
CONSOLE: [SEVERE] Could not pass event AsyncPlayerChatEvent to BadWords v1.41 7:58:29 PM CONSOLE: java.lang.IllegalStateException: Asynchronous player kick!
It doesn't kick players when they reach the limit of swears.
My players are on MINUS numbers and still dont get kicked. I noticed one of the response test lines is on 2 lines, maybe its an error in the default config. PS Please add /badw reload or load Its a pain rebooting just for one plugin. thanks
@MALONN
Thanks this has annoyed me from day 1/ Should be in the description.
Just so everyone knows....this is how to make it case-insensitive (because it is NOT obvious)...put (?i) before your word you're trying to replace/censor....example:
will replace all variants of budder with gold. Also, to disable banning AND kicking, in config.yml set:
That will disable kicking and banning completely. Useful when trying to only filter words and not ban/kick anyone for bad language
Finally, +? is also good. Example:
This will replace bUdDer, buddddddder, BUDDDER, and all other variants with gold.
Neither one of these are documented properly and I had to do some guesswork to figure it all out. This plugin is using regex capabilities, so google up "regex tutorial" for a CRAPLOAD of more useful stuff. regex is super powerful.
This is an awesome plugin, as long as you don't have too many words. I have a lengthy list of banned words (over 400 ... words from many different languages). But every time I restart the server, it is overwritten with the default config.yml. Otherwise, it works great... I just need it to work with my list!