2.17.2​

Improvements:

• Added Folia support - disclaimer: since Folia is a work-in-progress, things could break with future updates of Folia, but I will try my best to keep everything up to date as development progresses.
• Added LuckPerms prefix, suffix, and exempt support for Bungee & Velocity. Variables like executorPrefix and executorSuffix from messages.yml can now be used under a proxy instance of LiteBans, and offline players will be exempt from punishments if they have the required permissions.
• Added IP templates - any template with "ip_template: true" set in templates.yml will track each template ladder across all accounts on the same IP. All bans under an IP template will automatically become IP bans.
• Added new variables for messages.yml - $playerBans, $playerMutes, $playerWarnings, $playerKicks. These variables allow you to indicate the total number of punishments for each type tied to the affected player.
• Added template requirements for group limits - if you set `require_template: true` for a group, players from that group must specify a template in order to create a punishment, and will receive an error message otherwise.

Since this is group-based, you can have lower groups that are template-restricted and higher groups that can create custom punishments.

• Updated the AdvancedBan importer for the latest release to support tempbans, IP bans, and punishment history.

Fixes:

• Fixed Bedrock usernames starting with "*" being considered wildcard IP addresses by the new `ipban_command` security option that prevents players from placing wildcard IP bans.
• Fixed certain randomized IDs not working correctly with /checkban, /checkmute, or /unban.
• Fixed the new JSON features (Run Command, Open URL) requiring "litebans.json.hover_text" permission even if the message has no hover text.
• Fixed a startup error which could rarely occur under certain conditions due to a bug in older server versions (1.7 <-> 1.10.2 affected).

API changes:

• Added RandomID class, which allows you to convert random ID strings into numbers and vice versa.
• Added a method to Entry which returns the random ID of the punishment.

Minor improvements:

• Added support for viewing IP bans matching no specific account (e.g. wildcard IP bans) in /history & /staffhistory. By default, only console can view the IP addresses, and players will see ip_hidden instead of the actual IP address.
• Added permission node `litebans.newline` for using newlines ("\n") in punishment reasons.
• Small performance improvements for some commands (/kick, /dupeip, /history, /staffhistory, /checkban, and more).
• The "-g" flag (shortcut for "server:*") now works with all commands that accept server scopes.

Minor fixes:

• Fixed variables such as totalBans not working in /banlist (not configured by default).
• Fixed custom command senders having unbans/unmutes not showing up in /history, and fixed them not being targetable in other commands such as /staffhistory or /staffrollback.
• Fixed server UUIDs being generated twice when server.yml has been created for the first time. This has no major side effects.

I've also completely removed AntiPiracy from the plugin, so it shouldn't connect to the AntiPiracy server and shouldn't throw messages like "Access Disabled".
-ElitePusher

Improvements:

• Added randomized punishment IDs ($idRandom), with configurable seed and a unique algorithm. These reversible and unpredictable IDs can be used in /checkban, /checkmute, or you can use "/litebans reveal" to convert a random ID into a real ID. This feature has practically no overhead for servers not using it, as only the sequential ID is stored in the database, and server resources (CPU/memory) required to obscure these numbers are only claimed upon use of this feature.
• Added unban/unmute/unwarn by-ID support (example: `/unban 1234`). This supports regular punishment IDs, but also directly supports randomized IDs which are added in this update.
• Added the ability to run commands when clicking on messages. Variables that are included in the command will be substituted as well. Example: "Test {run: /command $playerName}"
• Added the ability to open URLs when clicking on messages. Example: "Test {url: https://example.com/}". This is only supported for chat messages, as the equivalent JSON in disconnect messages would have no effect if clicked - alas, a client side limitation.
• Added "expire_ladder" template option. Each template of any type can now have a ladder duration. This allows you to set precisely how long a template ladder will last for. For example, if you set `expire_ladder: 50d`, any punishments older than 50 days will not count towards the template's ladder anymore. This is separate from punishment expiry - when the template ladder expires, all of its issued punishments may still be active.
• Added /namehistory command. This command displays usernames and the last login date of each username linked to each account. This can also be used on IP addresses to get a list of usernames per IP (like /alts, but with a login date for each username).
• Added "punish_ip" option to config.yml. When enabled, all punishments will be IP-based by default, so you can IP-ban players by using the /ban command.
• Added automatic SHA-256 checksum verification for all library dependencies. Note that all dependencies have always been downloaded from the official Maven repository over HTTPS.
• Added support for importing from LibertyBans (supported: temporary bans, permanent bans, IP bans).
• Tab completion will now work for all commands even if Essentials is installed, without additional configuration under Spigot.

Fixes:

• Fixed template steps with permanent duration creating punishments that expire instantly.
• Fixed kick templates not supporting colours & variables in the kick messages.
• Fixed permitted players (via "/litebans allow") being able to join the server even if they have a ban matching their account directly. There was a check for this, but it didn't trigger as intended.
• Fixed short-format durations in the configuration specified in days (e.g. `30d`) being processed as 0 seconds. Other duration units unaffected, and long format (e.g. `30 days`) unaffected.
• Fixed /staffrollback & /prunehistory removing all of the user's punishments if an invalid duration was provided, instead of giving an error message.
• Fixed PostgreSQL startup error ("Something unusual has occurred to cause the driver to fail") due to a bug in the database driver (negative timeout caused by driver calculated integer overflow)

Minor improvements:

• Added locale setting to messages.yml. This option controls the language which dates are represented with, so if your host machine has a different system locale than you wanted and you are unable to change that system locale, you can set it manually instead.
• Templates with no duration option will now permit the duration to be specified manually through the command.
• Under Bungee & Velocity, disabling mutes in the configuration will now let the backend servers handle mute commands instead. This can serve as a workaround for the issue where muted players get kicked if they try to chat while muted under 1.19.2+, if you still need LiteBans to be installed under the proxy.

Minor fixes:

• Reduced unnecessary on-demand Mojang API requests.
• Fixed /ipban requiring `litebans.ban` permission in addition to `litebans.ipban`.
• Fixed JSON hover text not functioning in messages when hover text is configured on a new line with no spaces after the new line.
• Fixed /tempbanip and /tempmuteip checking inconsistent permissions (litebans.tempbanip instead of litebans.ipban) under Bungee & Velocity.
• Fixed mutechat bypass permission only applying when chat messages are sent and not when blacklisted commands are used.
• Fixed an error which could occur specifically under BungeeCord if another plugin stops the server while the server hasn't loaded yet, while LiteBans is attempting to load.
• Fixed punishments of the same type submitted at the exact same time possibly reporting incorrect IDs in immediate post-punishment messages (e.g. broadcasts)
• Fixed "temporary players" error under Spigot again - this error has no side effects and it should also be exceedingly rare.
• Fixed errors caused by having an invalid duration format configured. A warning will be logged, and the default format will be used if the duration format is invalid.
• Fixed malformed configurations causing errors in specific cases.
• Fixed two types of startup errors with unknown causes which could not be replicated. Neither of these errors were reported to occur under Bungee or Velocity.

Improvements:

• Added randomized punishment IDs ($idRandom), with configurable seed and a unique algorithm. These reversible and unpredictable IDs can be used in /checkban, /checkmute, or you can use "/litebans reveal" to convert a random ID into a real ID. This feature has practically no overhead for servers not using it, as only the sequential ID is stored in the database, and server resources (CPU/memory) required to obscure these numbers are only claimed upon use of this feature.
• Added unban/unmute/unwarn by-ID support (example: `/unban 1234`). This supports regular punishment IDs, but also directly supports randomized IDs which are added in this update.
• Added the ability to run commands when clicking on messages. Variables that are included in the command will be substituted as well. Example: "Test {run: /command $playerName}"
• Added the ability to open URLs when clicking on messages. Example: "Test {url: https://example.com/}". This is only supported for chat messages, as the equivalent JSON in disconnect messages would have no effect if clicked - alas, a client side limitation.
• Added "expire_ladder" template option. Each template of any type can now have a ladder duration. This allows you to set precisely how long a template ladder will last for. For example, if you set `expire_ladder: 50d`, any punishments older than 50 days will not count towards the template's ladder anymore. This is separate from punishment expiry - when the template ladder expires, all of its issued punishments may still be active.
• Added /namehistory command. This command displays usernames and the last login date of each username linked to each account. This can also be used on IP addresses to get a list of usernames per IP (like /alts, but with a login date for each username).
• Added "punish_ip" option to config.yml. When enabled, all punishments will be IP-based by default, so you can IP-ban players by using the /ban command.
• Added automatic SHA-256 checksum verification for all library dependencies. Note that all dependencies have always been downloaded from the official Maven repository over HTTPS.
• Added support for importing from LibertyBans (supported: temporary bans, permanent bans, IP bans).
• Tab completion will now work for all commands even if Essentials is installed, without additional configuration under Spigot.

Fixes:

• Fixed template steps with permanent duration creating punishments that expire instantly.
• Fixed kick templates not supporting colours & variables in the kick messages.
• Fixed permitted players (via "/litebans allow") being able to join the server even if they have a ban matching their account directly. There was a check for this, but it didn't trigger as intended.
• Fixed short-format durations in the configuration specified in days (e.g. `30d`) being processed as 0 seconds. Other duration units unaffected, and long format (e.g. `30 days`) unaffected.
• Fixed /staffrollback & /prunehistory removing all of the user's punishments if an invalid duration was provided, instead of giving an error message.
• Fixed PostgreSQL startup error ("Something unusual has occurred to cause the driver to fail") due to a bug in the database driver (negative timeout caused by driver calculated integer overflow)

Minor improvements:

• Added locale setting to messages.yml. This option controls the language which dates are represented with, so if your host machine has a different system locale than you wanted and you are unable to change that system locale, you can set it manually instead.
• Templates with no duration option will now permit the duration to be specified manually through the command.
• Under Bungee & Velocity, disabling mutes in the configuration will now let the backend servers handle mute commands instead. This can serve as a workaround for the issue where muted players get kicked if they try to chat while muted under 1.19.2+, if you still need LiteBans to be installed under the proxy.

Minor fixes:

• Reduced unnecessary on-demand Mojang API requests.
• Fixed /ipban requiring `litebans.ban` permission in addition to `litebans.ipban`.
• Fixed JSON hover text not functioning in messages when hover text is configured on a new line with no spaces after the new line.
• Fixed /tempbanip and /tempmuteip checking inconsistent permissions (litebans.tempbanip instead of litebans.ipban) under Bungee & Velocity.
• Fixed mutechat bypass permission only applying when chat messages are sent and not when blacklisted commands are used.
• Fixed an error which could occur specifically under BungeeCord if another plugin stops the server while the server hasn't loaded yet, while LiteBans is attempting to load.
• Fixed punishments of the same type submitted at the exact same time possibly reporting incorrect IDs in immediate post-punishment messages (e.g. broadcasts)
• Fixed "temporary players" error under Spigot again - this error has no side effects and it should also be exceedingly rare.
• Fixed errors caused by having an invalid duration format configured. A warning will be logged, and the default format will be used if the duration format is invalid.
• Fixed malformed configurations causing errors in specific cases.
• Fixed two types of startup errors with unknown causes which could not be replicated. Neither of these errors were reported to occur under Bungee or Velocity.

2.11.1:

Fixes:

• Fixed kicks matching `ignored_kick_messages` not being processed correctly (kick was broadcasted, and not added to database, but player wasn't kicked).

API changes:

• Fixed punishment IDs being set to -1 on the event API. Entries in-database unaffected.

2.11.2:

Improvements:

• Added support for setting timezones (/litebans timezone) under local H2 database.
• Updated database driver: MariaDB (3.0.7 => 3.1.2). Notably, 3.1.2 includes a fix for an ArrayIndexOutOfBoundsException driver bug.

Fixes:

• Fixed MySQL->H2 self-import searching for uppercase tables that don't exist (H2->MySQL unaffected).
• Fixed templates with names consisting of numbers not working correctly.
• Fixed an edge-case bug with imported bans having invisible staff history until the staff have joined the server for the first time after import.
• Fixed `obscure_seed` not updating correctly when `/litebans reload` is used.

Minor fixes:

• Further reduced unnecessary on-demand Mojang API requests.
• Attempted another fix for an error with unknown causes which could not be replicated.
• Fixed an error which could randomly occur on shutdown ("Interrupted during connection acquisition")
• Fixed short-format durations specified in days (e.g. "30d") not working specifically with the `expire_after` option in config.yml. Long format is used by default ("7 days").

Improvements:

• Added randomized punishment IDs ($idRandom), with configurable seed and a unique algorithm. These reversible and unpredictable IDs can be used in /checkban, /checkmute, or you can use "/litebans reveal" to convert a random ID into a real ID. This feature has practically no overhead for servers not using it, as only the sequential ID is stored in the database, and server resources (CPU/memory) required to obscure these numbers are only claimed upon use of this feature.
• Added unban/unmute/unwarn by-ID support (example: `/unban 1234`). This supports regular punishment IDs, but also directly supports randomized IDs which are added in this update.
• Added the ability to run commands when clicking on messages. Variables that are included in the command will be substituted as well. Example: "Test {run: /command $playerName}"
• Added the ability to open URLs when clicking on messages. Example: "Test {url: https://example.com/}". This is only supported for chat messages, as the equivalent JSON in disconnect messages would have no effect if clicked - alas, a client side limitation.
• Added "expire_ladder" template option. Each template of any type can now have a ladder duration. This allows you to set precisely how long a template ladder will last for. For example, if you set `expire_ladder: 50d`, any punishments older than 50 days will not count towards the template's ladder anymore. This is separate from punishment expiry - when the template ladder expires, all of its issued punishments may still be active.
• Added /namehistory command. This command displays usernames and the last login date of each username linked to each account. This can also be used on IP addresses to get a list of usernames per IP (like /alts, but with a login date for each username).
• Added "punish_ip" option to config.yml. When enabled, all punishments will be IP-based by default, so you can IP-ban players by using the /ban command.
• Added automatic SHA-256 checksum verification for all library dependencies. Note that all dependencies have always been downloaded from the official Maven repository over HTTPS.
• Added support for importing from LibertyBans (supported: temporary bans, permanent bans, IP bans).
• Tab completion will now work for all commands even if Essentials is installed, without additional configuration under Spigot.

Fixes:

• Fixed template steps with permanent duration creating punishments that expire instantly.
• Fixed kick templates not supporting colours & variables in the kick messages.
• Fixed permitted players (via "/litebans allow") being able to join the server even if they have a ban matching their account directly. There was a check for this, but it didn't trigger as intended.
• Fixed short-format durations in the configuration specified in days (e.g. `30d`) being processed as 0 seconds. Other duration units unaffected, and long format (e.g. `30 days`) unaffected.
• Fixed /staffrollback & /prunehistory removing all of the user's punishments if an invalid duration was provided, instead of giving an error message.
• Fixed PostgreSQL startup error ("Something unusual has occurred to cause the driver to fail") due to a bug in the database driver (negative timeout caused by driver calculated integer overflow)

Minor improvements:

• Added locale setting to messages.yml. This option controls the language which dates are represented with, so if your host machine has a different system locale than you wanted and you are unable to change that system locale, you can set it manually instead.
• Templates with no duration option will now permit the duration to be specified manually through the command.
• Under Bungee & Velocity, disabling mutes in the configuration will now let the backend servers handle mute commands instead. This can serve as a workaround for the issue where muted players get kicked if they try to chat while muted under 1.19.2+, if you still need LiteBans to be installed under the proxy.

Minor fixes:

• Reduced unnecessary on-demand Mojang API requests.
• Fixed /ipban requiring `litebans.ban` permission in addition to `litebans.ipban`.
• Fixed JSON hover text not functioning in messages when hover text is configured on a new line with no spaces after the new line.
• Fixed /tempbanip and /tempmuteip checking inconsistent permissions (litebans.tempbanip instead of litebans.ipban) under Bungee & Velocity.
• Fixed mutechat bypass permission only applying when chat messages are sent and not when blacklisted commands are used.
• Fixed an error which could occur specifically under BungeeCord if another plugin stops the server while the server hasn't loaded yet, while LiteBans is attempting to load.
• Fixed punishments of the same type submitted at the exact same time possibly reporting incorrect IDs in immediate post-punishment messages (e.g. broadcasts)
• Fixed "temporary players" error under Spigot again - this error has no side effects and it should also be exceedingly rare.
• Fixed errors caused by having an invalid duration format configured. A warning will be logged, and the default format will be used if the duration format is invalid.
• Fixed malformed configurations causing errors in specific cases.
• Fixed two types of startup errors with unknown causes which could not be replicated. Neither of these errors were reported to occur under Bungee or Velocity.

2.10.4:

Improvements:

• Added a `console_cooldown` option for specific use cases (e.g. throttling anticheat bans), one second by default. Unlike player cooldowns, this does not stop the console from punishing multiple players at once, it only protects players from double punishments.
• Updated database driver: MariaDB (3.0.6 => 3.0.7)

Fixes:

• Fixed ban & mute templates presenting the `message` node based on the ladder step above the one it was intended for. For ban templates, the initial disconnect message was unaffected.
• Fixed `ignored_kick_messages` not working as intended since version 2.10.3.
• Fixed /lockdown kicking players who have litebans.lockdown.bypass (Bungee and Velocity instances are unaffected).
• Fixed kick templates not respecting template permissions.
• Fixed IP bans overriding other IP bans when the same account is already banned but a different IP address is targeted for the IP ban. (only IP bans matching identical UUID+IP will override now)
• Fixed startup errors when upgrading very large databases (> 1M bans) caused by timeout.
• Fixed a J9VM specific error.

Minor improvements:

• Added "afk" to the default ignored_kick_messages list.
• The "tempbanip" and "tempmuteip" command aliases are now supported under Bungee & Velocity.
• The "/litebans allow" command can now be used to allow UUIDs which have never joined the server before, not just names.
• Exempt messages now support more variables (e.g. playerDisplayName).

Minor fixes:

• Fixed a startup warning that occurs under MySQL (but not MariaDB).
• Fixed console bans from proxy instances showing server origin as the network name rather than the target's server name if they are online.
• Fixed ProtocolLib error when using very outdated versions of ProtocolLib.
• Fixed again: permission_error message from messages.yml not being shown instead of the builtin no_permission message from messages.properties in all cases under BungeeCord (Spigot version unaffected)
• Fixed "/litebans allow" error when attempting to allow a user who has never joined the server and doesn't exist either (this operation would fail regardless of the fix).