CurseBan
Current Version: 1.3.2.1
Recommended Build: 1.3.2-R1 (Craftbukkit build - 2377)
IMPORTANT: With 2.3.1b, matching has been changed. Please see the release notes for additional information
About
What is this?
Ever had a player flaming constantly? Or maybe you want to have a family-friendly server? Or you want to stop people from asking for diamonds? Now you don't have to worry about that anymore: CurseBan allows you to add "stalk words" - Whenever a player mentions one of them, he gets kicked. At the same time, the plugin keeps track of a "curse value" for every stalked words. This curse value is added to the players point count every time he uses such a word. You can define commands that should be executed once a user reaches a certain threshold, and a cooldown to remove points.
How does it work?
Every curse/banned word is assigned a certain point value. Every time a player uses one of these words, the word's point value is added to that players total count. Then, the command associated with that total value is executed. If none is associated, the next lowest is executed.
Commands, Permissions and Examples
Commands
- /cb - Displays help
- /cb list - Lists the current stalk words
- /cb add [word] <threshold> - Adds the word with that ban threshold to the list. If no threshold is given, 5 is used
- /cb remove [word] - Removes that word from the list
- /cb pardon [player] - Sets that player's kick count to 0 (Note: Will not unban if he has been banned)
- /cb pardon-all - Sets the kick count of all players to 0( Note: Will not unban if they have been banned)
- /cb save - Save all files to the disk. Handle with care, this will overwrite and changes made to the files that have not yet been reloaded.
- /cb set value [curse] [value] - Sets the curse point value of the curse
- /cb set matching [curse] [matchtype] - Sets the matching for this curse (Allowed: default, default-ignorecase, literal, literal-ignorecase, regex, regex-all-lower)
- /cb set kick [message] - Sets the default kick message
- /cb set command [value] [command] - Sets the command to be executed whenever a player reaches or passes value
- /cb listpoints [player] - displays points for a specific player (case sensitive)
Permission nodes
(Note that any node can be represented by its parent node - You can use cb.admin.* instead of typing in every node one by one)
- cb.admin.ignore - You won't get kicked for cursing
- cb.admin.pardon.all - Will set the kick count of all players back to zero. Will not unban them
- cb.admin.pardon.single - Will pardon single player. Also no unban
- cb.admin.add - Add curses to the list
- cb.admin.remove - D'uh
- cb.admin.save - Allows to save files
- cb.admin.set.value - Allows to set the curse points value of a banned word
- cb.admin.set.matching - Allows to set matching for a word
- cb.admin.set.kick - Allows to set the default kick message
- cb.admin.set.command - Allows to set a new or existing command to be executed when a point value is reached
- cb.list - Allows to see a list of all stalked curses
Example Usages
- Stop cursing: /cb add shit
- Stop people from typing in ALL CAPS: /cb add r:[A-Z]{3} will kick for 3 or more consecutive uppercase letters
- Give people diamonds if they say "supercalifragilistic": /cb add i:supercalifragilistic 9000, in the config file, put 9000: give %name% diamond 64;cb pardon %name%
Examples
/cb add shit - The list now contains the word shit, with default value 5
/cb list -> "[shit]"
/cb add fuck 10 - The list now contains the word fuck, with a value of 10
/cb list -> "[shit, fuck]"
/cb set command 0 kick %name% - Kicks a player whenever he swears and has more than 0 points (Basically, always) (Note that %name% is a variable used to represent the player's name)
/cb set command 10 jail %name% - Jails a player whenever he swears and has more than 10 points
Player A joins...
A: "This server is shit!" -> "shit" has a value of 5 -> A now has 5 points -> 0 < 5 < 10, so the "kick" command is executed
A rejoins...
A: "What the fuck, man?" -> "fuck" has a value of 10 -> A now has 15 points -> 10 < 15, so the "jail" command is executed
All this can also be done by editing the yaml files created in /plugin/CurseBan - see this page for more information: http://dev.bukkit.org/server-mods/curseban/pages/how-to-use-the-yml-files/
Misc
ToDo
- Add the ability to tell the player their bad word they said using %word% (You'd be able to add this to the jail sign (IE - Swearing: 'shit' ))
- Stop the server from overwriting files saved to the server by the server owner after a restart.
Changelog
v1.3.2.1:
- Changed version number to reflect current MC version it is configured for. (1.3.2) with additional build number for this (.1)
- Fixed issue 18 and 20 for issues with PlayerChatEvent (essentially replaced this even with AsycPlayerChatEvent) This seems to have resolved this issue, but I'm not entirely sure to be honest. Please report any issues you find to the ticket system. Do not post here.
Note this version will NOT work with tekkit servers. Use version 2.5.0 for Tekkit version 3.1.2.
v 2.5.0: -First release by new project owner GokouZWAR
- Fixed points being added to players instead of taking them away over time.
- Added console tracking for player's points so you can see when the system takes away player points, and how much was removed and when.
- Updated for Craftbukkit 1.2.5 - R4
- Added a few things on this page (commands that were missing, comments, and old missing revision information)
v 2.4.0: - (don't know if all these were added but I found these on the update page, possibly things he wanted added or had fixed in this version, not entirely sure. They were marked 2.4 so I'm going with this as the last updates. -GokouZWAR)
- (Hopefully) Fixed config not being saved on shutdown
- Fixed /cb set matching setting the wrong option
- Added: Logging to save methods
- Added: Reload command (/cb reload <all/config/curse/count>). Permission node: cb.admin.reload (alternatively, permission for one file only can be given by cb.admin.reload.<file>)
- Added: List command (/cb listpoints [player] - Player is optionally, omitting it will display all). Permission node: cb.admin.listpoints
- Added: Config option "save": Determines how files should be saved, in addition to the shutdown save:
- always: Save every file whenever it is modified
- config: Save the config file when modified
- curse: Save the curse file when modified
- count: Save the count file when modified
- Multiple options are possible: "save: config,curse"
v 2.3.3:
- Update to CraftBukkit 1.2.5-R1.0 (Phew, finally)
- Extended logging to include the message in which the word was found.
v 2.3.2:
- Updated to R6/1.2.3-R01
- Removed any deprecated API
- Included new matching, see release notes for more information
v 2.3.0:
- Added variable for the config file: %points% is replaced by the number of points the player has
- Implemented http://dev.bukkit.org/server-mods/curseban/tickets/8-log-chat-entry/ : Added "log-actions" option to the config file (default: true). This logs: The name of the player, the word that triggered the filter, the commands issued in return and the points of the player.
v 2.2.10:
- Moved the always-kick check behind any executed commands - This should fix bug #6 (http://dev.bukkit.org/server-mods/curseban/tickets/6-still-wont-ban-no-obvious-errors-tho/) which caused the plugin to not perma-ban people
v 2.2.9:
- Updated to 1.1-R3
v 2.2.8:
- Security patches
v 2.2.7:
- Command lists are now separated by both ";" and " ;"
- Version number displayed on startup and shutdown
v 2.2.6:
- Fixed Bug #2 (#3, #4): NullPointerException in onClientChat
v 2.2.5:
- Changed indenting of the .yml files
v 2.2.4:
- Fixed null-pointer-exception after using /cb pardon-all
- Added support for multiple commands
- Added /cb save
v 2.2.3:
- Updated to MC 1.0.* / CB 1.0.1-R1
v 1.2.3:
- Added cooldown (See: "How to use the .yml files")
- Added command: /cb set literal [curse] [true/false]
- Added permission node: cb.admin.set.literal
v 1.2.2 (Final and beta release notes merged):
- Updated to RB 1337
- Rework of the curse punishment system
- Switched everything to Yaml
- Added literal matching: A * in front of the word if using ingame commands, or the "literal-match" option in the Curses.yml
- Fixed Curses not being loaded properly (If you already added curses, but they arent showing up ingame, rename "Curse Point Value.yml" to "Curses.yml"
- Custom commands possible
v1.1.2:
- Updated to RB 1317
- Hopefully fixed PEX issue
- Skipped v1.1.1, derp
v1.1.0:
- Updated to RB 1240
v1.0.0:
- First release
Contact
Ticket here or contact me on www.mcnations.net. Email: administrator at mcnations Dot Net. Latest version in use will be on server.mcnations.net:25599 - running Tekkit.
@csminecraft
Mine look like:
<word>: {matching: default-ignorecase, value: '5'}
<word>: {matching: literal-ignorecase, value: '5'}
I'm running 2.3.4.
Is anyone experiencing issues with the matching of default-ignorecase or literal-ignorecase? I have tried clearing out my curses.yml and re-adding them to the list. For instance when I add the word fuck I use the command /cb add fuck and /cb set matching fuck default-ignorecase or /cb set matching fuck literal-ignorecase. When I save the curses.yml shows fuck: {matching: default, value: '5', literal-match: literal-ignorecase}. In game when I say fuck I get kicked as expected by when I try Fuck it goes straight to chat. Am I doing something incorrectly or configuring it in the wrong way? I have also tried deleting the .jar and using a fresh download. Thanks for any help.
bukkit 1.2.5r1.0 curseban 2.3.4
@Boreeas
Yes, the values all stay 0 after restart. The config file has the default settings.
@paulj1x
Late reply to this, but... The values are the default ones: cooldown-time-min: '10', cooldown-stepsize: '10'
@JadoJodo
Right now, the only options are cancelling the chat or letting it go through. Garbling and censoring may be worth thinking about, though, thanks.
Is there any possibility the offending text can be garbled?
@sillyrosster
The config get saved when the server shuts down, so any modifications made while the server is running will be overwritten.
@Boreeas
Also, whenever I edit the config itself, it never saves correctly. Even on a restart, it just resets to what it was previously.
@sillyrosster That would only block *s*h*i*t*, s h i t, and combinations thereof, with any number of spaces and/or stars between them. Also, a * is a 'match-all' character. You would need to escape it by putting a backslash before it. Try changing [ \*]+ to ([ \*]+)?. Also, take a look at this tutorial for more information on regex.
@Boreeas
So, if I do: '[ *]+[sS][ *]+[hH][ *]+[iI][ *]+[tT][ *]+': {matching: regex, value: '15'} will that block sh*t and other forms or just *s*h*i*t*?
2012-04-17 10:28:22 [INFO] This server is running CraftBukkit version git-Bukkit-1.2.5-R1.0-b2149jnks (MC: 1.2.5)
2012-04-17 10:28:22 [INFO] [Curseban] Loading Curseban v2.3.3
2012-04-17 10:28:23 [INFO] [TownyChat] Loading TownyChat v0.24
If someone curses, it doesnt kick the user or block the text.
This error pops up into the console:
2012-04-17 10:30:32 [SEVERE] Could not pass event PlayerChatEvent to Curseban org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:303) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:459) at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:786) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764) at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34) at net.minecraft.server.NetworkManager.b(NetworkManager.java:229) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.util.MissingFormatArgumentException: Format specifier 's' at java.util.Formatter.format(Unknown Source) at java.util.Formatter.format(Unknown Source) at java.lang.String.format(Unknown Source) at de.boreeas.curseban.listeners.CBChatListener.onPlayerChat(CBChatListener.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:301) ... 11 more
@sillyrosster
With regex, you can: If you want for example to block "bitch", you could add a pattern like "[ _]+[bB][ _]+[iI][ _]+[tT][ _]+[cC][ _]+[hH][ _]+"
Is there a way to block it when they space and _ and stuff?
Finally got around to update to the latest CB version, though the plugin should've worked fine anyways. Also added logging of the message in which the word was found.
@paulj1x
A workaround with CurseBan would be setting an extremely high point value for the word "lag". With that point values, associate all the command you want to execute, followed by "cb pardon %name%". A side effect would be that anyone with a high value could just say "lag" to reset their points. A separate plugin would therefor be better suited for this.
Glad you like it!
One interesting feature would be as follows:
People complain a lot about lag, thinking it's the server when it's really their computer along with Java memory leaks. I installed a new plugin called LagMeter which measures the server's lag. What I would like is for every time a player says the word "lag", it tells them they can run /lag, it runs /lag for them and tells them if the number is greater than 16 the problem is with their computer and they should restart minecraft or reboot their computer. But this should not kick them. It also shouldn't add to their point value but that's easy to do. So I would like one set of actions for the curse words and a different set of actions for other words. Maybe a separate plugin?
Loving CurseBan!!!!!!!!!!!!!!!!!
@wzehrung
What are your cooldown-time-min and cooldown-stepsize values?
@wzehrung
This would be since the curse counts are only saved to the file once the server shuts down. If it is still 0 after a server shutdown, please check if cooldown is enabled, and if it is not, please file a bug report.
Using Curseban 2.3.2 and everything seems to be working, except that in the Player Curse Count.yml file, no matter how much someone curses, the values are always 0. Tried to look through previous posts to find and answer, but didn't locate anything related.
I've also had this problem on a test server with a fresh install of Curseban.
Am I missing something?
Thanks :)
Is anyone else getting an error from this plugin, everytime someone says something?
Running version 2.3.2, #Bukkit 2151