Improvements:
By popular demand, I have added options (enabled by default) to prevent players from viewing IP addresses.
By default, it will no longer be possible for ingame players to use "/litebans sqlexec", /iphistory, or for players to see IP addresses in /dupeip, even if they have permissions.

Fixes:
Exempt checks no longer apply to unbans / unmutes.

Fixed "$command" not being replaced in /dupeip usage message.

Fixed MySQL->H2 imports failing due to uppercase table names ( #62).

Minor fixes:
Commands will no longer malfunction when provided redundant spaces (double spaces, triple spaces, etc). Blank arguments are ignored.

Notes:
New options in config.yml:
2.3.11:

Minor improvements:
Added compatibility for pre-1.7.10 versions of BungeeCord (before commit https://github.com/SpigotMC/BungeeCord/commit/cf722de1d25b092c745eae7d1acabf702683c71e)

2.3.12:

Fixes:
Fixed plugin failing to start under Spigot if ProtocolLib wasn't installed since version 2.3.11 (last version).

2.3.13:

Improvements:
Added full support for 1.13 command suggestions; commands that players don't have permission to use will no longer be suggested to them.
This also prevents players from viewing most LiteBans commands via "/help" or "/?" or tab completion.
^ Minor caveat: the /ban and /mute commands may still be suggested to all players if you are using ViaVersion (untested).

2.3.14:

Fixes:
Fixed the "unbanned by name" always being shown as the creator of the punishment instead of the one who removed it.

2.3.15:

Improvements:
The `litebans.clearchat.bypass` permission is now locked behind a config option due to the immense amount of confusion caused by its existence. Out of the box, players with OP or * permission now will have their own chat cleared by /clearchat.

Database driver updates. These will occur automatically after updating LiteBans.
Updated MySQL driver: 8.0.11 -> 8.0.15
Updated MariaDB driver: 2.0.3 -> 2.4.0
Updated H2 driver: 1.4.196 -> 1.4.197

Minor fixes:
Possibly fixed a rare bug involving plugin conflicts when another plugin provides an outdated version of a database driver (e.g. H2) -- as Java does not provide any useful relevant information when class loading conflicts occur (such as the jar file paths of both classes in the conflict if they differ), I do not know which plugins create such conflicts, so I can't replicate this and check if it's been fixed or not.

Fixed warning `Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'.`.

Fixed "$command" in "/litebans import" usage message.