Bukkit

3.1.0 RC2

• De-color option fixed
• Changed default settings in config.yml (won't affect existing configs)

3.1.0 RC1 Originally planned to be a 3.0.2 release, too many changes had to be made to get proper Async-safe Bukkit API calls.

• Make PwnFilter Async safe, by caching playername, world and permissions for use in async calls.
• Add support for PluginMetrics (You can disable by putting opt-out: true in your PluginMetrics/config.yml file, but we ask you to consider leaving it enabled, so we can get an idea of how many people are using this plugin. )
• /pfreload now loads config.yml as well as rules.txt
• Add Vault Economy support and a "then fine <amount> <message>" action. (Create a swear jar!)
• EXPERIMENTAL: Anvil support. This is a little buggy until we get some fixes in Bukkit. It looks like the item is still on the Anvil inventory, but it's not. We've never seen a duplication though, so it should be safe. Enable/disable with itemfilter:true/false in your config.yml (disabled by default)

3.0.1 Bugfix Release

• Fix bug where "then console" or "conchain" was cancelling the event, but it should not.
• Change debug: from true/false to off/low/medium/high
• Fix bug with Colored Strings that causes formatting to get munged.
• Update Actions so they don't try to perform asynchronous addLogMessages through the Bukkit scheduler. Fixes ConcurrentModificationException's

3.0.0 Release

• Fixed permissions
• Possibly patched a problem that would trigger a ConcurrentModification exception

Note: This is now a bugfix-only release. A new feature update (including anvil support) will be released as 3.1.0 in a few days.

3.0.0-rc3

• Fix issues with too many log entries
• Remove logfilelevel option and replace with loglevel: <info|fine|finer|etc..>
• Fix traceback onDisable
• Implement require / ignore functionality for commands
• Fix spam filters. Now, spamfilter: true will stop a user from sending the same chat message 2x in a row. commandspamfilter: true will do the same for commands. (eg: /me <blah>) TODO: More complete documentation for 3.0.0 release.

3.0.0-rc2

• Use system logger instead of custom file writer.
• No longer clobbers existing PwnFilter.log file (sorry about that)
• New option in config.yml: logfilelevel Set to "info" by default. (similar to old behavior)

3.0.0-rc1 * Alpha Release * This release has passed our basic testing, but it is a major rewrite. We ask you to test it on a development server and give us feedback!

• Complete refactoring of rule processing. Now, instead of being parsed on each event, the whole rules.txt is parsed into a rulechain (faster).
• Added support for filters on signs. You can now limit rules by doing event <sign,command,chat> (see sample rules.txt)
• Added support for colored strings! If users have colors in their chat, the filter will preserve those colors (except where text is being replaced)
• Logging has been changed, use "then log" under specific rules to log those matches. Be sure to back up your pwnfilter.log file before updating!

2.4.2

• Updated for CB 1.5.2-R01
• Fixed a bug in which cancelled chat from other plugins would get uncancelled by PwnFilter, most noticeable with players who had been muted.

2.4.1

• Minor tweaks to listener code
• A small fix for signs and the ignore signs operator

2.4.0

• Revamped permissions structure to add more flexibility, especially for admins.
• Minor config.yml updates, you might want to update to be safe.
• Moved some high level checks to the listeners to improve efficiency.
• Adopted a new file structure and improved priority listener system.
• New Feature: Basic Sign Filter (Will erase sign text if there is a Match)
  • Added "ignore signs" flag for rules that should ignore sign text (CAPS and multiple character spam for example)
• New Feature: Basic anti-spam for commands and chat.
  • Permissions to bypass spam check
  • Command blacklist will bypass spam check
• New Feature: /pfmute now accepts a message instead of announcing player name.
  • /pfmute (optional message to send to server when muting/unmuting)

2.3.5

• Fixed bug in 2.3.4 that caused some of the new features to work improperly.
• Added to config.yml - command blacklist, a list of commands to always ignore in the command filter.
• Features from 2.3.4 - new rules.txt post match operators
  • require command - forces rule to require it to be a command (or list of commands)
  • ignore command - rules will not run for command (or list of commands)
• Last 1.5.x update unless either a major bug is found, or until Bukkit 1.5 RB comes out. Time to actually play some minecraft!

2.3.3

• Added configurable priority to command filter, check updated config.yml
• Added configurable list of commands to check with the filter, check updated config.yml

2.3.2

• Removed bugs/typos from 2.3.1 that we're defective
• Supports Minecraft 1.5.1
• Adds &rawstring feature to command and console post match operators

2.3.0

• Supporting Minecraft 1.5
• Added Command Listener - configurable in config.yml. Add commandfilter:true
• Command listener uses all the same rules.txt as your chat filter..
• Experimental right now, there will be tweaks and fixes i'm sure.

2.2.0

• Added another option to the config.yml for decolor:true/false
• Added extra permission for bypassing the global mute.. pwnfilter.bypassmute
• Added a permission for bypassing decolor if decolor is true. pwnfilter.color
• Toyed with some settings to get color matching to work better, still no go
• Fixed a small bug in the pwnfilter.log

2.1.4

• New addition to config.yml - make sure to update!
• Added configurable setting to the pwnfilter.log in config.yml. If you don't want logging set to false.
• Added date and time to the logfile, this might be useful - probably should have added it in the first place.
• Added console chaining, similar concept to command chaining, with the new rule "then conchain".
• Small fix to the "then deny" rule, removed message replacement because it borks some instances of making cool aliases.
• 1.4.7-R0.1 compatible.

2.1.3

• Built for Bukkit 1.4.6-R0.3
• Added enhanced logging, find pwnfilter.log file in your /plugins/PwnFilter/ folder.
• For rules/matches to be logged you must add "then log" to your rule set. This was in an effort to not spam the log for rules you don't need to log.

2.1.2

• Delete your config.yml for this update to generate a new one, rules.txt can remain.
• Bugfixes on burn, warn, kick and kill messages where replacement text would break.
• Added default messages for warn, burn, kick and kill to the config.yml with color code support.
• Default messages can be overridden via rules.txt, also with color code support.
• More code cleanup for a faster running plugin!

2.1.1

• Build for Craftbukkit 1.4.6-R0.1
• Some small code tweaks for greater efficiency, thanks to Cryptix.

2.1.0

• Build for Craftbukkit 1.4.5-R1.0
• New post match operators:
  • then cmdchain - Allows you to create chained command aliases. Usage: then cmdchain command 1|command 2|command 3
    • Note that these are player issued commands, players will need to have permissions to use commands in the chain.
    • You may use syntax from the standard "then command" operator like &player, &world and &string for data replacement in the chains.
• New command and permission node
  • /pfmute - permission: pwnfilter.pfmute - description: Globally mute the entire server (regular chat only not PM's or emotes). Using this command will cancel ALL chat events until this command is run again.
• A long awaited addition for pwnfilter finally added: configurable plugin priority.
  • Important You should delete your existing config.yml for this update.
  • Edit the config.yml "priority" with choice of lowest, low, normal, high, highest. Default is lowest.
  • If Pwnfilter is not working well with any of your other chat related plugins, you may change the priority in order to resolve conflicts. Contact your chat control plugin maker to find out what priority their "listener" runs on.

2.0.0

• New post match operators:
  • then randrep - replaces matching regex from a pipe separate list of potential replacements!
  • then lower - replaces matching regex with the same matching regex, forced to lower case! (Basically, CAPS Replacer)
• Removed the [PwnFilter] prefix from warning, burn and kill messages. You may now use your own warning message from scratch, with color code support!
• Please review the PwnFilter Pages for updated material on the 2.0 update!

1.9.3

• Added "then kill" and "then burn" as optional punishments related to a match. See post match operators page for usage.

1.9.2

• Updated for CB 1.4.5-R0.2
• Fixed bug with PwnFilter player kicks and asynPlayerChatEvent.

1.9.1

• PwnFilter for Craftbukkit 1.4.2-R0.2 and reverted to Java 6. If you prefer for any reason, Java7, 1.9.0 will also work on 1.4.2 servers.

1.9.0

• Built for CraftBukkit 1.3.2-R1.0 (Also works on 1.3.2-R2.0, 1.3.2-R3.0 and 1.4.2 dev builds - so far)
• Now using Java7, if you have any issues let me know and I'll refactor on Java6.

1.8.0

• Fixed console unable to execute rules reload.
• Changed "/pwnfilter reload" to a more simple "/pfreload"
• Added new feature "/pfcls" by request: will clear all players chat screens to remove unwanted ads, swears from sight
• Code cleanup for handling commands and permissions

1.7

• Updated for CraftBukkit 1.3.1 new AsyncPlayerChatEvent. This will NO LONGER WORK on 1.2.5!
• Code cleanup for enabling and disabling plugin, code cleanup on chat listener.
• Removed some unused libraries.

1.6

• Added new permission node pwnfilter.bypass to give to users or groups who should not be affected at all by pwnfilter.
• Built against Bukkit 1.2.5R 5.0 and tested compatible.

1.5

• Adjusting PwnFilter's event.priority to lowest setting in attempt to avoid conflicts with other chat control plugins.
• Updated the default "rules.txt" file with changes seen since 1.2

1.4

• Added requested option "ignore string" which will ignore a match if it contains the defined string.
• Removed "ignore group" and "require group" in lieu of permissions, basically redundant code.
• Upgraded plugin from "Beta" to "Release"

1.3

• Added "ignore permission" and "require permission" rules.
• Added "then rewrite" rule for soft replacement, ignoring color codes.
• Edited "then replace" rule for hard replacement, stripping color codes.
• Added new variable "&string" to rules for "command" & "console". Use &string to insert chat message into your rule.
• Added the "&player" and "&world" variables to "command" as well as "console".
• Fixed "command" to ignore chat message unless given "&string" as a variable, great for making aliases.

1.2

• Improved detection and replacement of messages for users with colored chat enabled. This would be difficult if not impossible using rules.txt so I built it into the filter.
• Was told I should include a LICENSE file in my source file so I did.

1.1

• Updated default rules.txt
• Minor code cleanup
• Added permission node pwnfilter.reload (no longer OP only)

1.0

• Built original plugin against CraftBukkit 1.2.5-R4.0
• Added in bukkit.ChatColor support
• Fixed /pwnfilter reload function, actually works now, and reloads the rules.txt
• Added rules.txt chat color support for &(0-F) color codes. These previously worked in the old version but derped somewhere along the way with CB updates and changes.
• Renamed plugin from RegexFilter to PwnFilter with intention of eventual code overhaul.

Anti-spam feature may conflict with other anti-spam plugins, you should really only use 1 anti-spam plugin, PwnFilters anti-spam can be disabled in config.yml

Anti-spam command feature may conflict with commands that use a cooldown/warmup system, in the event of conflict, add those commands to blacklist.

PF Has not been fully tested with all channel based chat plugins. Some chat plugins may require changes in priority settings.

Some reports say that the Spigot fork of Bukkit is not fully compatible with PwnFilter. (PwnFilter 3.0.0-rc3 appears to work on a dev spigot server but currently only Bukkit is officially supported)

New logging system starts *should not* start a new pwnfilter.log. Be sure to back it up anyway, before updating, as this 3.0.0 version will may overwrite it and create a new one. (should not happen with rc2 anymore, please let us know if it does)