Plugins LiteBans 2.18.8

Improvements:

• Updated for Minecraft 1.21.10.
• Fabric versions supported by this update: 1.21.10, 1.21.9, 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.1, 1.20.1
• Added offline player tab completion with built-in name compression. The memory cost of caching thousands of usernames is reduced by up to 70%, depending on random factors.
  • Using tab complete decompresses 25% of the cache, temporarily. The server will reclaim this memory as needed.
  • This compressor is entirely custom designed, and packs itself up while not in use to efficiently reduce memory consumption, unpacking again only when needed.
  • The limit of cached entries can be set with `offline_tab_size` in config.yml.
• Added `{suggest: text}` JSON feature support. Clicking on the text will set the input to the specified command.
• Added `{copy: text}` JSON feature support. Clicking on the text will copy the specified text to the clipboard.
• Added `--delete`, `--skip`, `--hide`, and `--no-queue` command flags.
• The `--delete` flag (`-d`) allows you to delete a specific punishment. This flag erases punishments from history and reverts template progress with /unban, /unmute, /unwarn. Example: `/unban -d 4321`
• The `--skip` flag, intended for templates, allows you to issue "dummy" bans/mutes that advance templates but nothing more.
• The `--hide` flag disables the broadcast entirely. Console will not see it either.
• The `--no-queue` flag disables unban queueing.
• Command flags issued by a template (not specified by user) now have full authority and require no permissions to use.
• Added configurable `broadcast` node to templates. It's now possible to have separate broadcast messages for each template, and for each ladder step. This also makes it possible to disable the broadcast.
• Added configurable hex colour formats for compatibility with third party plugins. By default, the following hex colour formats are included: `&%s`, `<%s>`, `{%s}`

Fixes:

• Paper: Fixed Paper breakage due to breaking changes in Paper once again.
• Fabric: Fixed hex colours in plain chat messages not working as intended.
• Fabric: Fixed config.yml not being copied correctly under specific conditions.
• Proxy: Fixed `litebans.notify.broadcast.local.*` permission nodes not being checked. Other server specific nodes unaffected.
• Fixed staffhistory not being fully ordered by creation time since version 2.17.
• Fixed template flags expecting a list instead of a single string. Either format can now be specified.
• Fixed URL click event validation issues for 1.21.5+.
• Fixed notifications (such as offline warnings) being skipped if users take more than 4 seconds to join the server. (Proxies less affected)

Minor improvements:

• The /staffrollback command now supports server scopes.
• The /alts command will now also check for bans/mutes on the scope of the recipient's current server and not just the global/proxy scope when LiteBans is installed on a proxy instance.
• The modify_success message now factors in all variables affected by the modification, not only reason/dateEnd.
• Added workaround to prevent "zip file closed" in one specific instance. This error is not caused by LiteBans.
• Template actions will now be applied before players are kicked.
• Added infinite loop detection (stack overflow) for recursive templates.
• Added support for non-inline fields.
• Durations can now be specified as 'unlimited'.

Minor fixes:

• Fixed errors caused by incorrectly formatted fields/structures in messages.yml and templates.yml.

Web Interface:

• The web interface now supports both lookup and displaying of random IDs (info_show_random_id).

2.18.1:

Fixes:

• Fabric: Fixed runtime errors since version 2.18 on specific versions (only 1.21.5/1.21.1 affected)
• Fixed an error which could occur in rare cases since version 2.18.

2.18.2:


Fixes:

• Fixed several bugs & errors regarding compression.

2.18.3:

Fixes:

• One more fix for the previous issues.

2.18.4:

Improvements:

• Optimized compression.

Fixes:

• Fixed a bug that was blocking players from using commands after they had used it once since version 2.18.
• Fixed unrecognised flag (`--stack=1` bug) with template actions since version 2.18.
• Fixed a rare ConcurrentModificationException that could happen if both compression and decompression occurred simultaneously.
• Fixed another edge case with compression.

2.18.5:

Improvements:

• Improved performance of decompression & compression.

Fixes:

• Fixed duplicate key/caching issues with 1-10 users.
• Fixed unban/unmute history from console not being displayed.

2.18.6:

Improvements:

• Updated for Minecraft 1.21.9/1.21.10.
• Fabric versions supported by this update: 1.21.10, 1.21.9, 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.1, 1.20.1

Fixes:

• Fixed `--stack=1` flag being passed to other plugin commands in template actions since version 2.18.

2.18.7:

Improvements:

• Messages are now loaded on a separate thread to boost startup time by ~20%.
• Reduced memory usage of messages & random IDs.

Fixes:

• Fixed specifying UUIDs which have never joined the server before in commands not working as intended.
• Fixed unban/checkban errors with specific usernames.
• Fixed a bug from previous optimizations that could cause errors with less than 20 bytes to compress for offline tab.

2.18.8:

Improvements:

• Improved compression ratio with >4000 usernames - the cost-benefit analysis algorithm was completely rewritten and should be significantly more efficient with many thousands of usernames.

Fixes:

• Fixed desync of compression cache causing issues with offline tab completion under certain conditions.
• Fixed more edge cases with URLs specified in reasons/messages causing issues with 1.21.5+ clients.
• Fixed hidden templates appearing in history as the check only applied to IP bans.
• Fixed webhook fields: specifying one line will result in an inline field, two lines for non-inline, not vice versa.
• Fixed InterruptedException error message on shutdown.

Minor improvements:

• Multi-line inline values are now supported for webhook fields.
• Raised 'Database is slow' threshold from 1 second to 4 seconds.

Improvements:

• Updated for Minecraft 1.21.10.
• Fabric versions supported by this update: 1.21.10, 1.21.9, 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.1, 1.20.1
• Added offline player tab completion with built-in name compression. The memory cost of caching thousands of usernames is reduced by up to 70%, depending on random factors.
  • Using tab complete decompresses 25% of the cache, temporarily. The server will reclaim this memory as needed.
  • This compressor is entirely custom designed, and packs itself up while not in use to efficiently reduce memory consumption, unpacking again only when needed.
  • The limit of cached entries can be set with `offline_tab_size` in config.yml.
• Added `{suggest: text}` JSON feature support. Clicking on the text will set the input to the specified command.
• Added `{copy: text}` JSON feature support. Clicking on the text will copy the specified text to the clipboard.
• Added `--delete`, `--skip`, `--hide`, and `--no-queue` command flags.
• The `--delete` flag (`-d`) allows you to delete a specific punishment. This flag erases punishments from history and reverts template progress with /unban, /unmute, /unwarn. Example: `/unban -d 4321`
• The `--skip` flag, intended for templates, allows you to issue "dummy" bans/mutes that advance templates but nothing more.
• The `--hide` flag disables the broadcast entirely. Console will not see it either.
• The `--no-queue` flag disables unban queueing.
• Command flags issued by a template (not specified by user) now have full authority and require no permissions to use.
• Added configurable `broadcast` node to templates. It's now possible to have separate broadcast messages for each template, and for each ladder step. This also makes it possible to disable the broadcast.
• Added configurable hex colour formats for compatibility with third party plugins. By default, the following hex colour formats are included: `&%s`, `<%s>`, `{%s}`

Fixes:

• Paper: Fixed Paper breakage due to breaking changes in Paper once again.
• Fabric: Fixed hex colours in plain chat messages not working as intended.
• Fabric: Fixed config.yml not being copied correctly under specific conditions.
• Proxy: Fixed `litebans.notify.broadcast.local.*` permission nodes not being checked. Other server specific nodes unaffected.
• Fixed staffhistory not being fully ordered by creation time since version 2.17.
• Fixed template flags expecting a list instead of a single string. Either format can now be specified.
• Fixed URL click event validation issues for 1.21.5+.
• Fixed notifications (such as offline warnings) being skipped if users take more than 4 seconds to join the server. (Proxies less affected)

Minor improvements:

• The /staffrollback command now supports server scopes.
• The /alts command will now also check for bans/mutes on the scope of the recipient's current server and not just the global/proxy scope when LiteBans is installed on a proxy instance.
• The modify_success message now factors in all variables affected by the modification, not only reason/dateEnd.
• Added workaround to prevent "zip file closed" in one specific instance. This error is not caused by LiteBans.
• Template actions will now be applied before players are kicked.
• Added infinite loop detection (stack overflow) for recursive templates.
• Added support for non-inline fields.
• Durations can now be specified as 'unlimited'.

Minor fixes:

• Fixed errors caused by incorrectly formatted fields/structures in messages.yml and templates.yml.

Web Interface:

• The web interface now supports both lookup and displaying of random IDs (info_show_random_id).

2.18.1:

Fixes:

• Fabric: Fixed runtime errors since version 2.18 on specific versions (only 1.21.5/1.21.1 affected)
• Fixed an error which could occur in rare cases since version 2.18.

2.18.2:


Fixes:

• Fixed several bugs & errors regarding compression.

2.18.3:

Fixes:

• One more fix for the previous issues.

2.18.4:

Improvements:

• Optimized compression.

Fixes:

• Fixed a bug that was blocking players from using commands after they had used it once since version 2.18.
• Fixed unrecognised flag (`--stack=1` bug) with template actions since version 2.18.
• Fixed a rare ConcurrentModificationException that could happen if both compression and decompression occurred simultaneously.
• Fixed another edge case with compression.

2.18.5:

Improvements:

• Improved performance of decompression & compression.

Fixes:

• Fixed duplicate key/caching issues with 1-10 users.
• Fixed unban/unmute history from console not being displayed.

2.18.6:

Improvements:

• Updated for Minecraft 1.21.9/1.21.10.
• Fabric versions supported by this update: 1.21.10, 1.21.9, 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.1, 1.20.1

Fixes:

• Fixed `--stack=1` flag being passed to other plugin commands in template actions since version 2.18.

2.18.7:

Improvements:

• Messages are now loaded on a separate thread to boost startup time by ~20%.
• Reduced memory usage of messages & random IDs.

Fixes:

• Fixed specifying UUIDs which have never joined the server before in commands not working as intended.
• Fixed unban/checkban errors with specific usernames.
• Fixed a bug from previous optimizations that could cause errors with less than 20 bytes to compress for offline tab.

Improvements:

• Updated for Minecraft 1.21.8.
• Fabric versions supported by this update: 1.21.8, 1.21.7, 1.21.6, 1.21.5, 1.21.1, 1.20.1
• Added offline player tab completion with built-in name compression. The memory cost of caching thousands of usernames is reduced by up to 70%, depending on random factors.
  • Using tab complete decompresses 25% of the cache, temporarily. The server will reclaim this memory as needed.
  • This compressor is entirely custom designed, and packs itself up while not in use to efficiently reduce memory consumption, unpacking again only when needed.
  • The limit of cached entries can be set with `offline_tab_size` in config.yml.
• Added `{suggest: text}` JSON feature support. Clicking on the text will set the input to the specified command.
• Added `{copy: text}` JSON feature support. Clicking on the text will copy the specified text to the clipboard.
• Added `--delete`, `--skip`, `--hide`, and `--no-queue` command flags.
• The `--delete` flag (`-d`) allows you to delete a specific punishment. This flag erases punishments from history and reverts template progress with /unban, /unmute, /unwarn. Example: `/unban -d 4321`
• The `--skip` flag, intended for templates, allows you to issue "dummy" bans/mutes that advance templates but nothing more.
• The `--hide` flag disables the broadcast entirely. Console will not see it either.
• The `--no-queue` flag disables unban queueing.
• Command flags issued by a template (not specified by user) now have full authority and require no permissions to use.
• Added configurable `broadcast` node to templates. It's now possible to have separate broadcast messages for each template, and for each ladder step. This also makes it possible to disable the broadcast.
• Added configurable hex colour formats for compatibility with third party plugins. By default, the following hex colour formats are included: `&%s`, `<%s>`, `{%s}`

Fixes:

• Paper: Fixed Paper breakage due to breaking changes in Paper once again.
• Fabric: Fixed hex colours in plain chat messages not working as intended.
• Fabric: Fixed config.yml not being copied correctly under specific conditions.
• Proxy: Fixed `litebans.notify.broadcast.local.*` permission nodes not being checked. Other server specific nodes unaffected.
• Fixed staffhistory not being fully ordered by creation time since version 2.17.
• Fixed template flags expecting a list instead of a single string. Either format can now be specified.
• Fixed URL click event validation issues for 1.21.5+.
• Fixed notifications (such as offline warnings) being skipped if users take more than 4 seconds to join the server. (Proxies less affected)

Minor improvements:

• The /staffrollback command now supports server scopes.
• The /alts command will now also check for bans/mutes on the scope of the recipient's current server and not just the global/proxy scope when LiteBans is installed on a proxy instance.
• The modify_success message now factors in all variables affected by the modification, not only reason/dateEnd.
• Added workaround to prevent "zip file closed" in one specific instance. This error is not caused by LiteBans.
• Template actions will now be applied before players are kicked.
• Added infinite loop detection (stack overflow) for recursive templates.
• Added support for non-inline fields.
• Durations can now be specified as 'unlimited'.

Minor fixes:

• Fixed errors caused by incorrectly formatted fields/structures in messages.yml and templates.yml.

Web Interface:

• The web interface now supports both lookup and displaying of random IDs (info_show_random_id).

2.18.1:

Fixes:

• Fabric: Fixed runtime errors since version 2.18 on specific versions (only 1.21.5/1.21.1 affected)
• Fixed an error which could occur in rare cases since version 2.18.

Improvements:

• Support Minecraft 1.21.5 (notably, URL click events are working again). This release adds support for the version-specific chat format used in 1.21.5.
• Added Fabric support.

Fixes:

• Fixed the "litebans reload" command on Paper 1.20+ not reloading the configuration (Spigot, Bungee, Velocity & Paper < 1.20 all unaffected). This was due to Paper remapping breaking stuff completely unrelated to NMS mappings.
• Fixed display names being limited by standard character limits for usernames (16 instead of 128 characters) in unban/unmute context.
• Fixed hex colours not working in `banned_message_geoip_blacklist` message.

API changes:

• LiteBans API 0.6.0
• Added template ID to Entry (hasTemplate(), getTemplateID())

Minor improvements:

• The `litebans.exempt` permission no longer grants `dupeip_join` exemption, this node must be granted explicitly.
• Support `templateName`, `templateStep` in broadcast messages and action commands.
• Support `serverOrigin` variable in banned_message_geoip_blacklist.
• Improved blocking of commands for muted players.
• Optimized template group handling.

Minor fixes:

• The /namehistory command will no longer list the same username twice.
• Fixed $active variable in messages not considering whether the entry has recently expired.
• Fixed `/litebans allow` only fetching online-mode UUIDs for users who have never joined the server before.

Notes:

• JSON update works on Spigot, BungeeCord, and Fabric 1.21.5. Velocity currently can't properly deserialize the updated JSON that LiteBans emits for 1.21.5 clients (no errors, though).

Since the Velocity API doesn't accept raw JSON elements, I can't send these to the client without using the protocol.

2.16.5:

Improvements:

• Added `prune` mode for `litebans reset-database`, which, upon use, only removes expired or deactivated punishments.

Fixes:

• Fixed invalid chat signature issue on backend servers triggered under specific conditions with 1.19+ clients. (This change does not affect proxy instances)

Minor fixes:

• Fixed harmless instance of "litebans_config doesn't exist" error when using a new database with an existing setup.

Improvements:

• Added automatic banning of linked accounts. The new `ban_alts` option accepts four different values with escalating levels of enforcement: Disabled, Enabled, Enhanced, and Extreme. By default, it is disabled.
• Added configurable filter duration for linked accounts (`dupeip_scan_filter_duration: 7d`), which is intended to prevent or reduce false positives by ensuring that only recent IP addresses are scanned with /alts, or when banning accounts automatically as mentioned above.
• Added template flags, which can be used to automatically add command flags and server scopes to specific templates and/or ladder steps. For example, you can make a template always execute global and silent punishments by setting `flags: '-g -s'`.
• Added support for webhook inline fields for embeds (optional).
• Added /checkwarn command which allows you to check specific warnings by player name or UUID.
• Added /warnlist command which allows you to scroll through all warnings.
• Added unwarn messages & entries to /history and /staffhistory.
• Added `online_mode` option to config.yml (to specify whether players who have never joined the server before should be handled as premium or non-premium players).
• Added `mode:deactivate` and exclude options for `/litebans reset-database`.
• (BungeeCord) Optimized ServerConnectEvent listener - database queries will no longer be performed in this context under any conditions.

Fixes:

• Fixed unban/unmute/unwarn webhooks inheriting silent state from the punishment instead of checking whether the operation is silent.
• Fixed hex colours not working in lockdown kick messages - reconnect messages unaffected.
• Fixed variables such as `playerBans` not working in webhook embed messages.

Minor improvements:

• Added new reset_database messages to messages.yml.
• Added messages for unsuccessful loading of templates.yml. If templates.yml is invalid, you will receive a message each time commands are used, as a reminder to fix your configuration.
• Added error handling for incorrectly configured URLs from webhooks.yml.
• When a name-banned or name-muted player attempts to join, their punishment ID will be logged to console.
• The `litebans cleariphistory` command has been replaced with the `litebans unlink` command which serves the same purpose.
• When the console receives a click event JSON message, the command or URL will be sent to console with the message.
• Chat event priority used by LiteBans is now low (instead of lowest) on all platforms.

Minor fixes:

• Fixed /banlist and /mutelist displaying one less page (page #0).
• Fixed unban queueing not unbanning accounts when `ban_names` is enabled, a player has a banned name and the UUID joining the server was not banned.
• Fixed permission error message not being updated on reload under Bungee.
• Fixed hex colours not being translated for permission error messages sent by the platform.
• Fixed bracket character being added to `start_no_ip` dupeip-on-join messages (/alts unaffected).
• Fixed a harmless warning message on newly created MariaDB databases.
• Fixed timezone offsets not applying correctly to $timeSince in unban/unmute/unwarn messages.
• Fixed an error caused by empty commands specified in the configuration (none by default).
• Fixed an error caused by server names or scopes that are configured or specified above the already documented 32 character limit.

2.16.1:


Fixes:

• Fixed login timestamps not being updated if the IP is unchanged (missing alts fix).
• Fixed /alts or /dupeip not showing the original account if they haven't joined within `dupeip_scan_filter_duration`.
• Fixed webhook routes handling 'on' / 'true' as an invalid URL.
• Fixed webhook embed messages interpreting colour codes & hex colours which made it impossible to tag channels.
• Fixed a mute bypass involving cheat clients (Velocity only).
• Fixed some notifications being throttled indefinitely (until next reload/restart) if throttling is enabled and the plugin was reloaded.

Minor fixes:

• Fixed /banlist sometimes showing an empty page (only if the number of bans is divisible by the number shown per page) since version 2.16.
• Fixed some caches being kept a few hours longer than intended if the plugin was reloaded.

2.16.2:



Fixes:

• Fixed error on warning modification (`/warn -m`) for players that lack `litebans.group.unlimited` or similar permissions. (Console unaffected)
• Fixed cross-server kicks (via /kick command only) not working as intended on Bedrock users.
• Fixed messages combining hover text and click events (run/url) having bugged text. (Velocity unaffected)

Minor improvements:

• Support MySQL 9.x for creating database indexes (if you recently upgraded from MySQL 8.x, the indexes have likely been created already). This does not impact MariaDB.
• When excluding tables from database reset, the history and config tables will be kept.
• Added additional data limits to prevent errors from incorrect usage of commands. For example, usernames larger than the username character limit will be truncated.
• Embeds can now have no content if inline fields are specified.
• Support player variables in GeoIP messages.
• If delete_warnings_after_action is enabled, warnings will only be cleared upon the final action being executed rather than the first.
• If messages.yml failed to load, you will be notified of this each time a command is used, not only on startup.
• Improved robustness of table upgrade check on servers that cannot upgrade normally under very rare, unknown circumstances (possibly DB crash or hardware error related).

Minor fixes:

• Fixed reset chat colour (&r) appearing specifically in webhook fields when referencing the executor variable.
• Fixed chat colours not being removed (generally from prefixes/suffixes) specifically in embed messages.
• Fixed random ID hex colour prevention (#$id) applying to webhook embed messages, which do not use colours.
• Fixed colour codes not being removed in webhook embed inline fields.
• Fixed IP addresses which have never joined the server before being displayed as #offline# instead of ip_hidden.

2.16.3:
Important fixes:

• Fixed new global punishments not being applied correctly since version 2.16.2 (Velocity unaffected)

Fixes:

• Fixed proxy_switch_banned chat messages not being delivered under Bungee for server scoped bans.

2.16.4:

Fixes:

• Fixed `litebans reset-database` not working since version 2.16.2.
• Fixed disabled webhooks using the default webhook on Bungee/Velocity.

Minor improvements:

• The `litebans reset-database` confirm message now quotes all arguments for confirmation, not just the server scope.
• Added warning message for unrecognized settings (ban_alts)

Minor fixes:

• Fixed hex colour codes not being removed in webhook messages.

Improvements:

• Added automatic banning of linked accounts. The new `ban_alts` option accepts four different values with escalating levels of enforcement: Disabled, Enabled, Enhanced, and Extreme. By default, it is disabled.
• Added configurable filter duration for linked accounts (`dupeip_scan_filter_duration: 7d`), which is intended to prevent or reduce false positives by ensuring that only recent IP addresses are scanned with /alts, or when banning accounts automatically as mentioned above.
• Added template flags, which can be used to automatically add command flags and server scopes to specific templates and/or ladder steps. For example, you can make a template always execute global and silent punishments by setting `flags: '-g -s'`.
• Added support for webhook inline fields for embeds (optional).
• Added /checkwarn command which allows you to check specific warnings by player name or UUID.
• Added /warnlist command which allows you to scroll through all warnings.
• Added unwarn messages & entries to /history and /staffhistory.
• Added `online_mode` option to config.yml (to specify whether players who have never joined the server before should be handled as premium or non-premium players).
• Added `mode:deactivate` and exclude options for `/litebans reset-database`.
• (BungeeCord) Optimized ServerConnectEvent listener - database queries will no longer be performed in this context under any conditions.

Fixes:

• Fixed unban/unmute/unwarn webhooks inheriting silent state from the punishment instead of checking whether the operation is silent.
• Fixed hex colours not working in lockdown kick messages - reconnect messages unaffected.
• Fixed variables such as `playerBans` not working in webhook embed messages.

Minor improvements:

• Added new reset_database messages to messages.yml.
• Added messages for unsuccessful loading of templates.yml. If templates.yml is invalid, you will receive a message each time commands are used, as a reminder to fix your configuration.
• Added error handling for incorrectly configured URLs from webhooks.yml.
• When a name-banned or name-muted player attempts to join, their punishment ID will be logged to console.
• The `litebans cleariphistory` command has been replaced with the `litebans unlink` command which serves the same purpose.
• When the console receives a click event JSON message, the command or URL will be sent to console with the message.
• Chat event priority used by LiteBans is now low (instead of lowest) on all platforms.

Minor fixes:

• Fixed /banlist and /mutelist displaying one less page (page #0).
• Fixed unban queueing not unbanning accounts when `ban_names` is enabled, a player has a banned name and the UUID joining the server was not banned.
• Fixed permission error message not being updated on reload under Bungee.
• Fixed hex colours not being translated for permission error messages sent by the platform.
• Fixed bracket character being added to `start_no_ip` dupeip-on-join messages (/alts unaffected).
• Fixed a harmless warning message on newly created MariaDB databases.
• Fixed timezone offsets not applying correctly to $timeSince in unban/unmute/unwarn messages.
• Fixed an error caused by empty commands specified in the configuration (none by default).
• Fixed an error caused by server names or scopes that are configured or specified above the already documented 32 character limit.

2.16.1:


Fixes:

• Fixed login timestamps not being updated if the IP is unchanged (missing alts fix).
• Fixed /alts or /dupeip not showing the original account if they haven't joined within `dupeip_scan_filter_duration`.
• Fixed webhook routes handling 'on' / 'true' as an invalid URL.
• Fixed webhook embed messages interpreting colour codes & hex colours which made it impossible to tag channels.
• Fixed a mute bypass involving cheat clients (Velocity only).
• Fixed some notifications being throttled indefinitely (until next reload/restart) if throttling is enabled and the plugin was reloaded.

Minor fixes:

• Fixed /banlist sometimes showing an empty page (only if the number of bans is divisible by the number shown per page) since version 2.16.
• Fixed some caches being kept a few hours longer than intended if the plugin was reloaded.

Improvements:

• Webhook routes: Added `webhooks.yml` - this configuration allows you to set webhook URLs for each type of punishment. For example, you can send silent mutes to #silent-mutes and temporary IP bans to #tempipbans.
• Silent punishments and alts scanning (dupeip) notifications will now be broadcasted using Discord Webhooks, if configured to do so.

Fixes:

• Fixed /lockdown error under Spigot since version 2.14 (Folia/Bungee/Velocity...

Improvements:

• Webhook routes: Added `webhooks.yml` - this configuration allows you to set webhook URLs for each type of punishment. For example, you can send silent mutes to #silent-mutes and temporary IP bans to #tempipbans.
• Silent punishments and alts scanning (dupeip) notifications will now be broadcasted using Discord Webhooks, if configured to do so.

Fixes:

• Fixed /lockdown error under Spigot since version 2.14 (Folia/Bungee/Velocity unaffected)
• Fixed /lockdown using `kick_message_global` instead of `kick_message` under Bungee/Velocity for local scopes.
• Fixed /unban returning a permission error message if the target is not currently banned and group weights are enabled.
• Fixed exempt weights being checked for non-player non-console senders such as rcon.
• Fixed limit parameter in history commands being ignored if a type was specified.
• Fixed `litebans reset-database` requiring a reload or server restart if the global scope was cleared since version 2.14.
• Fixed pinging roles in Discord embed messages. (`<@&roleID>`)

Minor improvements:

• Improved performance of template group calculations.
• Exempt bypass permissions will be automatically enabled when group weights are enabled, as these are only required to remove or modify punishments issued by console and are not checked when banning exempt players.
• Added slow database detection & warnings ("Database is slow! Establishing connection took 70 seconds.")
• Raised the default pool timeout from 25 seconds to 95 seconds. As some people are stuck with database servers that only work approximately half of the time, this will give LiteBans the time to reconnect when your server goes down for one minute every two minutes.
• Improved message consistency: replaced instances of `$bannedPlayer`/`$mutedPlayer`/`$warnedPlayer` in messages.yml with `$playerDisplayName`. The former variables will be migrated automatically.
• Renamed `round_down` option to `reduce_to_limit`.
• Further simplified database error messages.
• Added options to disable the /warn and /lockdown commands.

Minor fixes:

• Fixed the `--` flag not working correctly in certain commands.

Improvements:

• Added customizable Discord webhook embed messages.
• When exempt group weights are enabled, punishments created by higher groups cannot be removed or modified by lower groups.
• Added `litebans.notify.broadcast.<server>.<type>` permissions - this allows you to set server and/or type specific broadcasts for specific groups, and the local scope is also checked, which allows you to set up broadcasts to only display on their origin...