MC Plugin LiteBans 2.15.0

A complete, modern, cross-server banning solution (Spigot, Bungee, Velocity).

2.10.3:
Improvements:

• Templates assigned permissions now also require that permission for the template to be used or tab completed.
• Added ladder support for kick templates.

Fixes:

• Fixed certain Unicode characters causing database errors, because `utf8_unicode_ci` was the default encoding instead of `utf8mb4_unicode_ci`. This fix drops support for older 5.x MySQL servers which don't support this encoding.
• Warning templates will no longer present the `message` node based on the ladder step above the one it was intended for. Other nodes (reason, permission, duration, actions) unaffected, and other types (ban, mute, kick) also unaffected.
• Fixed error handling for invalid configurations under Bungee/Velocity broken since 2.10.0.
• Fixed errors related to switching database types without restarting the server.

Minor improvements:

• Players without "litebans.admin" permission will no longer be able to close hover text using "}" in ban reasons.

Minor fixes:

• Fixed Public Key Retrieval error helper not running if the connection fails on startup.

Improvements:

• Added Java 18 support.
• Added a powerful punishment template system for bans and mutes, which allows you to specify incremental punishment durations, specific punishment messages, permission-guarded punishments, and more. Templates are explained on the wiki.
• Added "/litebans allow" command, which allows you to permit specific players to join while IP-banned or GeoIP-blocked. This is UUID-based, not IP-based, so each account must be permitted separately.
• Optimized cross-server synchronization - when a punishment is issued, each server that the punished player is not present on will no longer perform a database check.
• Optimized mutes and IP mutes - removed a database check on each involved player when a new mute is applied.
• Changed default ipreport_minimum_accounts (1 => 2) in line with previous default behaviour before version 2.8.13. Previously, online accounts were not counted against this option.
• Added "require_kick_reason" option to enforce requirement of kick reasons.
• Added "dateRemoved" variable to messages.yml to indicate when a punishment was removed.
• Durations in the configuration can now be specified in short form (e.g. "7d" instead of "7 days").

Fixes:

• Fixed "/litebans unlink" only unlinking the last IP address that a user joined with (all IP addresses will be unlinked now).
• Fixed kick cooldowns not working as expected.
• Fixed "/banip" alias requiring "litebans.banip" permission instead of "litebans.ipban" under Bungee/Velocity. Also fixed other alias permissions (ban-ip, muteip)
• Fixed cross-instance synchronization not working under PostgreSQL. (This issue mainly affects the Spigot version, Bungee/Velocity versions are less impacted)

Minor fixes:

• Fixed "$timeSince" in unban/unmute history indicating the time since the ban was placed instead of when the unban was performed (this variable is not configured by default)
• Fixed /prunehistory not working on recently expired punishments.
• Fixed "temporary players" error under Spigot - this error has no side effects and it should also be exceedingly rare.
• Fixed "durationermanent" possibly not working as intended

Important fixes:

• Fixed "Queue full" configuration error occurring on recent builds of Spigot. This error was caused by a recent breaking Spigot change ("Comment support for YAML files") on 20 December 2021, because LiteBans depended on the old behaviour to add comments to the configuration.

Improvements:

• Optimization: Velocity version of LiteBans now performs login handling asynchronously via Continuation API. This only affects ban & GeoIP checks, as all other tasks fired upon server switch are already handled by other threads.

Fixes:

• Fixed tab completion for certain commands (not all commands) not working under Velocity if the backend server does not have LiteBans installed. ** Properly fixed and tested.

Minor improvements:

• LiteBans won't log the database connection info on successful startup at debug level 0. Only the database type (e.g. MySQL) will be logged. This makes it easier to share log files without worrying about sensitive information.

Minor fixes:

• Fixed time_format in messages.yml not being updated on "/litebans reload".

2.8.12:

Fixes:

• Fixed a database related error which, under Spigot, could sometimes occur on shutdown (but not on reload) under certain conditions.
• Fixed another startup error which does not occur on my testing servers.

2.8.13:

Fixes:

• Fixed a Java 18 specific startup error which didn't occur under Java 17.
• Fixed /ipreport and dupeip-on-join only counting offline players when checking account thresholds.
• Fixed MySQL import error under Velocity.
• Fixed /mutechat broadcast not being sent when "local_messages: false" is set.

Minor improvements:

• Added command aliases (/checkalts => /dupeip; /banip, /ban-ip => /ipban; /muteip => /ipmute) for Bungee/Velocity.
• The `ignored_history_servers` option has been renamed to `ignored_iphistory_servers`.
• Further simplified database connection error messages.

Important fixes:

• Fixed "Queue full" configuration error occurring on recent builds of Spigot. This error was caused by a recent breaking Spigot change ("Comment support for YAML files") on 20 December 2021, because LiteBans depended on the old behaviour to add comments to the configuration.

Improvements:

• Optimization: Velocity version of LiteBans now performs login handling asynchronously via Continuation API. This only affects ban & GeoIP checks, as all other tasks fired upon server switch are already handled by other threads.

Fixes:

• Fixed tab completion for certain commands (not all commands) not working under Velocity if the backend server does not have LiteBans installed. ** Properly fixed and tested.

Minor improvements:

• LiteBans won't log the database connection info on successful startup at debug level 0. Only the database type (e.g. MySQL) will be logged. This makes it easier to share log files without worrying about sensitive information.

Minor fixes:

• Fixed time_format in messages.yml not being updated on "/litebans reload".

2.8.12:

Fixes:

• Fixed a database related error which, under Spigot, could sometimes occur on shutdown (but not on reload) under certain conditions.
• Fixed another startup error which does not occur on my testing servers.

2.8.13:

Fixes:

• Fixed a Java 18 specific startup error which didn't occur under Java 17.
• Fixed /ipreport and dupeip-on-join only counting offline players when checking account thresholds.
• Fixed MySQL import error under Velocity.
• Fixed /mutechat broadcast not being sent when "local_messages: false" is set.

Minor improvements:

• Added command aliases (/checkalts => /dupeip; /banip, /ban-ip => /ipban; /muteip => /ipmute) for Bungee/Velocity.
• The `ignored_history_servers` option has been renamed to `ignored_iphistory_servers`.
• Further simplified database connection error messages.

Click to expand...

Important fixes:

• Fixed "Queue full" configuration error occurring on recent builds of Spigot. This error was caused by a recent breaking Spigot change ("Comment support for YAML files") on 20 December 2021, because LiteBans depended on the old behaviour to add comments to the configuration.

Improvements:

• Optimization: Velocity version of LiteBans now performs login handling asynchronously via Continuation API. This only affects ban & GeoIP checks, as all other tasks fired upon server switch are already handled by other threads.

Fixes:

• Fixed tab completion for certain commands (not all commands) not working under Velocity if the backend server does not have LiteBans installed. ** Properly fixed and tested.

Minor improvements:

• LiteBans won't log the database connection info on successful startup at debug level 0. Only the database type (e.g. MySQL) will be logged. This makes it easier to share log files without worrying about sensitive information.

Minor fixes:

• Fixed time_format in messages.yml not being updated on "/litebans reload".

2.8.12:

Fixes:

• Fixed a database related error which, under Spigot, could sometimes occur on shutdown (but not on reload) under certain conditions.
• Fixed another startup error which does not occur on my testing servers.

Click to expand...