Major MySQL performance improvements and optimizations:
Changed default MySQL database type to InnoDB. The plugin will automatically attempt to migrate existing MyISAM tables to InnoDB if 'engine: MyISAM' is set in the configuration.
Added indexes to optimize lookups.
Set primary key `id` on each table.
Removed "allow_duplicate_history" option since it could lead to significant performance loss if accidentally enabled, and this option is incompatible with unique indexing on the table.

If you've ever had issues with the plugin's MySQL performance, this update is definitely for you.

Added an option to the configuration to use display names (changed nicknames) wherever possible.

Added /clearchat command. This command can be bypassed with the "litebans.clearchat.bypass" permission, and players with the "litebans.notify.clearchat" permission will be notified when chat is cleared.

Warning actions will now inherit the silent flag from the warning itself. This means that if a player was warned silently and gets kicked or banned, it will be silent as well.
For existing configurations, this requires you to add "-s:$silent" to each warning action handled by LiteBans. See the new default configuration.

The web interface (litebans-php) has been updated: performance improvements, UUID compatibility fixes.

Cleaned up the default configuration.

Added "ban_names" configuration option to allow case-insensitive name bans for offline-mode servers.


Minor fixes:

Fixed /kick response being sent before the player is actually kicked.

The /mute command will now provide an error if mutes have been disabled in the configuration, instead of silently failing to work.

Fixed variables ($bannedUntil, etc) in ban broadcasts not being replaced in certain cases.

The history table will now be imported properly when importing from LiteBans.

1.8.1:
Fixed unmute broadcasts with the default messages.yml.