OpAskBan

Now builds using Gradle instead of Maven Now compatible with multiple Minecraft versions

This version adds a new config option! Ignore Non-Alphabetic Characters Default: true This new config will remove all non-alphabetic characters both from messages sent and from Bannable Messages! (For checking purposes only, the sent messages WILL NOT VISIBLY CHANGE and neither will the config) This effect stacks with Ignored Characters, meaning both can be enabled at once. Additionally, Ignored Characters has been updated to also removed Ignored Characters from Bannable Messages. This means you can ignore any character ever, as opposed to only YAML-allowed characters. (Note: !# are no longer automatically removed from messages for checking purposes) Example: Ignore Non-Alphabetic Characters: true Bannable Messages: can i have op? Player-sent message: "can i have [email protected]$^%##@$%$^&^&" Player has been banned.

BUG FIX Config updates were messed up, this should fix it. Sorry about that.

In this update, a new config option "OP Asked" was added. This will send a message to any operator who sends a message included in "Bannable Messages" This update also reconfigures the config.yml file to look more consistent. All paths have been updated to include spaces between words and capitalize the first letter of each word. The current config options will most likely never change after this update, and all new config options will be added according to this style. The new default config.yml is shown on the main Spigot page. (If you do not want any messages sent to operators who send Bannable Messages, insert '' into the OP Asked line)

This update adds a new config option! Ignore Characters Default: blank Usage: Add any number of YAML-approved characters. These characters will not be considered during checking if a player is sending a bannableMessage. Example: ignore Characters: xX bannableMessages: can i have op? Player sends: xXcan i have op?Xx Player is banned for asking for OP. Notes: Certain characters are automatically filtered out: !# These characters cannot go into the config.yml file If you filter out every character, then no messages will be "asking for OP". This is because the plugin does not filter the characters out of the bannableMessages (Although it might in the future...) If you want a message to be bannable but also want to ignore a character, just exclued that character from the bannableMessages Example: Ignored Characters: ? bannableMessages: can i have op Player sends: can i have op? Player is banned for asking for OP. If you do not want to ignore any characters (besides the default !#) simply do not put anything into the Ignored Characters config. The plugin will work exactly as it did before.

This release adds tab completion for both /config and /status commands

This release adds the Code (Text): /config remove command. Usage: Code (Text): /config remove "message" Message will be removed from the config Also, Code (Text): /config overwrite has been aliased to Code (Text): /config set for ease of use

Adds the permission "OPAsk.bypass" This permission will prevent the player from being banned by the plugin (Operators have this permission by default)

This update adds the /config (/opaskban config) command The /config command can be used to add or overwrite bannable messages without restarting or reloading your server Usage: /config get Sends a message to the user listing every bannable message /config add message Adds message to bannableMessages /config overwrite message Replaces the bannableMessages with message Future updates: /config remove Used to remove a message from bannableMessages

This release removes the Spigot API from the .jar file This drastically reduces the file size, as well as makes the plugin much less illegal Also it loads much faster now Special thanks to @Datatags for pointing out this issue. All instances of the plugin before this release have been removed.

This version adds comments throughout the source code (available on GitHub) It also adds the config options deleteBannableMessages and logDeletedMessages with default values of true and false respectively Additionally, it renames the opInquiry config to bannableMessages the version number is now 0.1.4

This release replaces the deprecated PlayerChatEvent with AsyncPlayerChatEvent and fixes the version detector to no longer warn you to update when your version is newer than the latest available on Spigot The version detector was updated both in the /opaskban:status command and in the startup command line output

Fixes a few possible NullPointer Exceptions and contains a few small optimizations Known issue: PlayerChatEvent is deprecated The plugin still works despite this issue

This update adds a few minor UpdateChecker related features, including a change to the /opaskban status command

The second major release, v0.1.0 adds several new features. -BanTime config option -banMessage config option -kickMessage config option -UpdateChecker -Removal of unnecessary welcome message -announcePlugin now accepts the String value "op" -plugin.yml version updated to 0.1.0