ВЕРСИИ (327)

This update is bumping Dependencies, namely cloud-paper, to support 26.3, which didn't reliably work due to errors. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating on my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any person who donated will be mentioned in the next release, if their name isn't inapropriate.

This update is bumping Dependencies, namely cloud-paper, to support 26.3, which didn't reliably work due to errors. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating on my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any person who donated will be mentioned in the next release, if their name isn't inapropriate.

# PLEASE READ BEFORE UPDATING! This update brings various important changes alongside a known issue/limitation on Paper Servers (More below). Please make sure to read this update completely before deciding to update. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating on my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any person who donated will be mentioned in the next release, if their name isn't inapropriate. ## Removal of BungeeCord support Due to recent dependency issues and the fact that a [long standing issue blocking Dialog support for ASL on BungeeCord](https://github.com/SpigotMC/BungeeCord/issues/3871) hasn't been addressed yet after almost a year, did I decide to finally drop BungeeCord support. This means that with this version onwards, will ASL only support Paper, Velocity and possibly forks of these two (If they do not bring breaking API changes). I'm sorry about this sudden change, but I simply cannot see a reason to support a dated, inefficient Proxy software like this anymore. ## Paper: Known issues The dialog system for `/asl profiles edit <profile>` will not display content of a profile correctly on versions prior to 26.x (Encountered on 1.21.11). I cannot currently think of a possible solution other than distribution a separate jar build using the 1.21.11 API of Paper. Dialogs seem to work fine on 26.x (Tested on 26.2). ## Changes ### Improvements of Commands The commands have been organized into their own set of record classes, to allow easier maintenance and overall better organisation. Function-wise should there've been no notable changes. ### 26.x support The plugin uses the 26.1.2 API of Paper and should work on these versions alongside 26.2. ### Dependency updates Several dependencies have been updated.

# PLEASE READ BEFORE UPDATING! This update brings various important changes alongside a known issue/limitation on Paper Servers (More below). Please make sure to read this update completely before deciding to update. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating on my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any person who donated will be mentioned in the next release, if their name isn't inapropriate. ## Removal of BungeeCord support Due to recent dependency issues and the fact that a [long standing issue blocking Dialog support for ASL on BungeeCord](https://github.com/SpigotMC/BungeeCord/issues/3871) hasn't been addressed yet after almost a year, did I decide to finally drop BungeeCord support. This means that with this version onwards, will ASL only support Paper, Velocity and possibly forks of these two (If they do not bring breaking API changes). I'm sorry about this sudden change, but I simply cannot see a reason to support a dated, inefficient Proxy software like this anymore. ## Paper: Known issues The dialog system for `/asl profiles edit <profile>` will not display content of a profile correctly on versions prior to 26.x (Encountered on 1.21.11). I cannot currently think of a possible solution other than distribution a separate jar build using the 1.21.11 API of Paper. Dialogs seem to work fine on 26.x (Tested on 26.2). ## Changes ### Improvements of Commands The commands have been organized into their own set of record classes, to allow easier maintenance and overall better organisation. Function-wise should there've been no notable changes. ### 26.x support The plugin uses the 26.1.2 API of Paper and should work on these versions alongside 26.2. ### Dependency updates Several dependencies have been updated.

This is a small update that bumps the version of the ExpressionParser to v1.7.0-b1 which allows ASL to provide custom extra arguments to the parser without the need of using a hacky workaround. Additionally is the condition parsing now wrapped in a try-catch to prevent stacktraces from filling your console if someone with f.e. a wrong/malformed protocol version (A bot?) pings your server and the parser fails due to an unexpected exception. It will now only print a warning with the exception reason. When `debug` is enabled will it also give the Stacktrace. ## Ko-fi supporters This update was supported by... **JW**! If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent.

This is a small update that bumps the version of the ExpressionParser to v1.7.0-b1 which allows ASL to provide custom extra arguments to the parser without the need of using a hacky workaround. Additionally is the condition parsing now wrapped in a try-catch to prevent stacktraces from filling your console if someone with f.e. a wrong/malformed protocol version (A bot?) pings your server and the parser fails due to an unexpected exception. It will now only print a warning with the exception reason. When `debug` is enabled will it also give the Stacktrace. ## Ko-fi supporters This update was supported by... **JW**! If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent.

This is a small update that bumps the version of the ExpressionParser to v1.7.0-b1 which allows ASL to provide custom extra arguments to the parser without the need of using a hacky workaround. Additionally is the condition parsing now wrapped in a try-catch to prevent stacktraces from filling your console if someone with f.e. a wrong/malformed protocol version (A bot?) pings your server and the parser fails due to an unexpected exception. It will now only print a warning with the exception reason. When `debug` is enabled will it also give the Stacktrace. ## Ko-fi supporters This update was supported by... **JW**! If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent.

This update brings two smaller changes alongside smaller dependency updates: 1. The PAPIUtil now uses a CacheKey created from the Player's UUID and the text to parse, to properly separate individual text with placeholders to parse. This should fix errors like the Favicon option suddenly having MOTD text present, causing errors. 2. The FaviconHandler now only prints stacktraces for its errors, if the `debug` option was enabled. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks.

This update brings two smaller changes alongside smaller dependency updates: 1. The PAPIUtil now uses a CacheKey created from the Player's UUID and the text to parse, to properly separate individual text with placeholders to parse. This should fix errors like the Favicon option suddenly having MOTD text present, causing errors. 2. The FaviconHandler now only prints stacktraces for its errors, if the `debug` option was enabled. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks.

This update brings two smaller changes alongside smaller dependency updates: 1. The PAPIUtil now uses a CacheKey created from the Player's UUID and the text to parse, to properly separate individual text with placeholders to parse. This should fix errors like the Favicon option suddenly having MOTD text present, causing errors. 2. The FaviconHandler now only prints stacktraces for its errors, if the `debug` option was enabled. ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks.

This patch update fixes a bad argument length check for the date placeholder, specifically the isBefore, isExact and isAfter placeholders. This fix was done by @UninenVille. Thanks! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks.

This patch update fixes a bad argument length check for the date placeholder, specifically the isBefore, isExact and isAfter placeholders. This fix was done by @UninenVille. Thanks! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks.

This patch update fixes a bad argument length check for the date placeholder, specifically the isBefore, isExact and isAfter placeholders. This fix was done by @UninenVille. Thanks! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks.

Happy new year everyone! This small update fixes a NullPointer issue reported in #537 where using `/asl profiles set` would give a NullPointerException. This was caused due to a missing Meta Key to set the command type (Whether it can only be used by player or also console). Thanks to @UninenVille for reporting! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks. ## Updates - Fix #537 (NullPointerException for `/asl profiles set`)

Happy new year everyone! This small update fixes a NullPointer issue reported in #537 where using `/asl profiles set` would give a NullPointerException. This was caused due to a missing Meta Key to set the command type (Whether it can only be used by player or also console). Thanks to @UninenVille for reporting! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks. ## Updates - Fix #537 (NullPointerException for `/asl profiles set`)

Happy new year everyone! This small update fixes a NullPointer issue reported in #537 where using `/asl profiles set` would give a NullPointerException. This was caused due to a missing Meta Key to set the command type (Whether it can only be used by player or also console). Thanks to @UninenVille for reporting! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks. ## Updates - Fix #537 (NullPointerException for `/asl profiles set`)

It has been a long time since a proper release was made, so I now decided to make one and actually make it a proper release, instead of a beta, as I haven't heard about any issues with the Dialog system on Paper and consider it stable. As a quick note, I do plan to implement Dialog support into BungeeCord as a last, final update for the platform, before finally dropping support for it. But until an [annoying issue is fixed](https://github.com/SpigotMC/BungeeCord/issues/3871) am I unable to ship this feature for people to use. If you know possible causes and/or ways to fix it, maybe contribute to BungeeCord (Or this plugin if it actually is a mistake on my end) to get it fixed! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks. ## Updates ### Support for newer MC versions Newer MC versions (1.21.11 for example) should now be properly supported by the plugin. They weren't due to dependencies, namely Adventure, not being updated, which should now be the case. ### LuckPerms Addon A new Addon, namely the [LuckPerms Addon](https://asl.andre601.ch/addons/first-party/luckperms/), has been created and is now available to use. It will provide placeholders to use in conditions to check for things such as the player's primary group, if it has a specific group or if it has a specific permission. This addon does has some downsides tho, namely the fact that LP's retrieval of User data is asynchronous, but due to various issues and limitations, the addon forces the data to be given synchronous, causing possible lag. This is mitigated by caching the data for 1 minute. ### New `date` placeholder set A new placeholder set named [`date`](https://asl.andre601.ch/profiles/placeholders/#date) is available for use. It allows you things related to dates such as getting the current date, whether it is before, excactly or after the specified date. Each placeholder accepts an optional pattern to represent the date with. As an example, `${date current dd/MM/yyyy` would return `19/12/2025` for the current date of this release. ### MiniPlaceholders support This version brings (experimental) support for MiniPlaceholders on Paper and Velocity. Note that only global placeholders/tags, meaning those not requiring a player, are actively supported, as per-player tags aren't due to various limitations. Also, just as with PAPI placeholders are MiniPlaceholders tags not supported in the `condition` option. I do hope this feature is working well for you.

It has been a long time since a proper release was made, so I now decided to make one and actually make it a proper release, instead of a beta, as I haven't heard about any issues with the Dialog system on Paper and consider it stable. As a quick note, I do plan to implement Dialog support into BungeeCord as a last, final update for the platform, before finally dropping support for it. But until an [annoying issue is fixed](https://github.com/SpigotMC/BungeeCord/issues/3871) am I unable to ship this feature for people to use. If you know possible causes and/or ways to fix it, maybe contribute to BungeeCord (Or this plugin if it actually is a mistake on my end) to get it fixed! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks. ## Updates ### Support for newer MC versions Newer MC versions (1.21.11 for example) should now be properly supported by the plugin. They weren't due to dependencies, namely Adventure, not being updated, which should now be the case. ### LuckPerms Addon A new Addon, namely the [LuckPerms Addon](https://asl.andre601.ch/addons/first-party/luckperms/), has been created and is now available to use. It will provide placeholders to use in conditions to check for things such as the player's primary group, if it has a specific group or if it has a specific permission. This addon does has some downsides tho, namely the fact that LP's retrieval of User data is asynchronous, but due to various issues and limitations, the addon forces the data to be given synchronous, causing possible lag. This is mitigated by caching the data for 1 minute. ### New `date` placeholder set A new placeholder set named [`date`](https://asl.andre601.ch/profiles/placeholders/#date) is available for use. It allows you things related to dates such as getting the current date, whether it is before, excactly or after the specified date. Each placeholder accepts an optional pattern to represent the date with. As an example, `${date current dd/MM/yyyy` would return `19/12/2025` for the current date of this release. ### MiniPlaceholders support This version brings (experimental) support for MiniPlaceholders on Paper and Velocity. Note that only global placeholders/tags, meaning those not requiring a player, are actively supported, as per-player tags aren't due to various limitations. Also, just as with PAPI placeholders are MiniPlaceholders tags not supported in the `condition` option. I do hope this feature is working well for you.

It has been a long time since a proper release was made, so I now decided to make one and actually make it a proper release, instead of a beta, as I haven't heard about any issues with the Dialog system on Paper and consider it stable. As a quick note, I do plan to implement Dialog support into BungeeCord as a last, final update for the platform, before finally dropping support for it. But until an [annoying issue is fixed](https://github.com/SpigotMC/BungeeCord/issues/3871) am I unable to ship this feature for people to use. If you know possible causes and/or ways to fix it, maybe contribute to BungeeCord (Or this plugin if it actually is a mistake on my end) to get it fixed! ## Ko-fi supporters This update was supported by... nobody ;-; If you can, consider donating to my [ko-fi](https://ko-fi.com/andre_601) to support this project. Any donators will have their names mentioned in the next release of this plugin as a thank you. Note that I may not mention your name, if it appears to be inapropriate or otherwise indecent. ## Before updating... It's recommended to always make backups before updating the plugins. While I try to test features, I cannot test everything due to a lack of a proper server setup with active players on it. As such can bugs and issues appear. Always [report them on Codeberg](https://codeberg.org/Andre601/AdvancedServerList/issues) when you find them. Thanks. ## Updates ### Support for newer MC versions Newer MC versions (1.21.11 for example) should now be properly supported by the plugin. They weren't due to dependencies, namely Adventure, not being updated, which should now be the case. ### LuckPerms Addon A new Addon, namely the [LuckPerms Addon](https://asl.andre601.ch/addons/first-party/luckperms/), has been created and is now available to use. It will provide placeholders to use in conditions to check for things such as the player's primary group, if it has a specific group or if it has a specific permission. This addon does has some downsides tho, namely the fact that LP's retrieval of User data is asynchronous, but due to various issues and limitations, the addon forces the data to be given synchronous, causing possible lag. This is mitigated by caching the data for 1 minute. ### New `date` placeholder set A new placeholder set named [`date`](https://asl.andre601.ch/profiles/placeholders/#date) is available for use. It allows you things related to dates such as getting the current date, whether it is before, excactly or after the specified date. Each placeholder accepts an optional pattern to represent the date with. As an example, `${date current dd/MM/yyyy` would return `19/12/2025` for the current date of this release. ### MiniPlaceholders support This version brings (experimental) support for MiniPlaceholders on Paper and Velocity. Note that only global placeholders/tags, meaning those not requiring a player, are actively supported, as per-player tags aren't due to various limitations. Also, just as with PAPI placeholders are MiniPlaceholders tags not supported in the `condition` option. I do hope this feature is working well for you.

This update fixes a `NoClassDefFoundError` on Paper versions before 1.21.7 (Before their implementation of a Dialog API). The entire Dialog handling was rewritten in the process, making it a lot more platform-agnostic too, allowing future expansion into other platforms (Velocity) once API becomes available.

This update fixes a `NoClassDefFoundError` on Paper versions before 1.21.7 (Before their implementation of a Dialog API). The entire Dialog handling was rewritten in the process, making it a lot more platform-agnostic too, allowing future expansion into other platforms (Velocity) once API becomes available.

This update fixes a `NoClassDefFoundError` on Paper versions before 1.21.7 (Before their implementation of a Dialog API). The entire Dialog handling was rewritten in the process, making it a lot more platform-agnostic too, allowing future expansion into other platforms (Velocity) once API becomes available.

This beta introduces a new command allowing you to edit profiles ingame using the new Dialog feature, and also announces the planned discontinuation of BungeeCord support. ## New Dialog-based edit feature A new command called `/asl profiles edit <profile>` was added to allow editing of profiles ingame using the Dialog feature introduced in MC 1.21.6. ### IMPORTANT This feature currently **only** supports Paper Builds 17 and newer for 1.21.7 due to older builds not having the necessary API and Velocity having no Dialog support yet. Once Velocity provides Dialog support will it be added to the plugin. ## Discontinuation of BungeeCord support `v5.7.0` will be the final version of AdvancedServerList that will support BungeeCord. I simply cannot see any good reason for keeping support given the existance of Velocity - a far superior Proxy. Note that the plugin *can* work on future BungeeCord versions, especially due to their attempts at keeping backwards compatability, but it's not guaranteed. This means, that once `v5.7.0` has been released, there will be no future updates -including bug fixes - for it anymore.

This beta introduces a new command allowing you to edit profiles ingame using the new Dialog feature, and also announces the planned discontinuation of BungeeCord support. ## New Dialog-based edit feature A new command called `/asl profiles edit <profile>` was added to allow editing of profiles ingame using the Dialog feature introduced in MC 1.21.6. ### IMPORTANT This feature currently **only** supports Paper Builds 17 and newer for 1.21.7 due to older builds not having the necessary API and Velocity having no Dialog support yet. Once Velocity provides Dialog support will it be added to the plugin. ## Discontinuation of BungeeCord support `v5.7.0` will be the final version of AdvancedServerList that will support BungeeCord. I simply cannot see any good reason for keeping support given the existance of Velocity - a far superior Proxy. Note that the plugin *can* work on future BungeeCord versions, especially due to their attempts at keeping backwards compatability, but it's not guaranteed. This means, that once `v5.7.0` has been released, there will be no future updates -including bug fixes - for it anymore.

This beta introduces a new command allowing you to edit profiles ingame using the new Dialog feature, and also announces the planned discontinuation of BungeeCord support. ## New Dialog-based edit feature A new command called `/asl profiles edit <profile>` was added to allow editing of profiles ingame using the Dialog feature introduced in MC 1.21.6. ### IMPORTANT This feature currently **only** supports Paper Builds 17 and newer for 1.21.7 due to older builds not having the necessary API and Velocity having no Dialog support yet. Once Velocity provides Dialog support will it be added to the plugin. ## Discontinuation of BungeeCord support `v5.7.0` will be the final version of AdvancedServerList that will support BungeeCord. I simply cannot see any good reason for keeping support given the existance of Velocity - a far superior Proxy. Note that the plugin *can* work on future BungeeCord versions, especially due to their attempts at keeping backwards compatability, but it's not guaranteed. This means, that once `v5.7.0` has been released, there will be no future updates -including bug fixes - for it anymore.

As promised last time is here a proper release of `v5.6.0` which I call the "Favicon Overhaul". This update provides significant changes to the FaviconHandler, providing a new feature in the form of Favicon merging and also a config.yml option to set how ASL should handle images with sizes that aren't exactly 64x64 pixels. ## FaviconHandler improvements The FaviconHandler has received major improvements. First of all are PlaceholderAPI placeholders now supported. Additionally was the async handling of Favicon creation simplified, as it was overcomplicated before. ## Favicon merging A new feature was added called favicon merging. With this feature are you able to combine multiple sources into a single favicon, allowing more complex, dynamic favicons to be created. To merge favicons, add new entries to the String separated by semicolons. As an example `${player uuid};border.png` would first place the Player head followed by putting `border.png` over it. The result would be similar to this:  ## Favicon resizing A new option called `faviconStrategy` was added to the `config.yml`. This option allows you to set how ASL should handle Images that have a size that isn't `64x64` pixels. The default option is `resize` but can be changed to `center` and `none`: - `center` does not resize the image, but instead centers it as good as possible in the Favicon. - `none` does not resize the image, nor move it. The image will simply placed at 0,0, which is the top-left corner of the Favicon. With these features should you be able to create some really cool Favicons for your server.

As promised last time is here a proper release of `v5.6.0` which I call the "Favicon Overhaul". This update provides significant changes to the FaviconHandler, providing a new feature in the form of Favicon merging and also a config.yml option to set how ASL should handle images with sizes that aren't exactly 64x64 pixels. ## FaviconHandler improvements The FaviconHandler has received major improvements. First of all are PlaceholderAPI placeholders now supported. Additionally was the async handling of Favicon creation simplified, as it was overcomplicated before. ## Favicon merging A new feature was added called favicon merging. With this feature are you able to combine multiple sources into a single favicon, allowing more complex, dynamic favicons to be created. To merge favicons, add new entries to the String separated by semicolons. As an example `${player uuid};border.png` would first place the Player head followed by putting `border.png` over it. The result would be similar to this:  ## Favicon resizing A new option called `faviconStrategy` was added to the `config.yml`. This option allows you to set how ASL should handle Images that have a size that isn't `64x64` pixels. The default option is `resize` but can be changed to `center` and `none`: - `center` does not resize the image, but instead centers it as good as possible in the Favicon. - `none` does not resize the image, nor move it. The image will simply placed at 0,0, which is the top-left corner of the Favicon. With these features should you be able to create some really cool Favicons for your server.

As promised last time is here a proper release of `v5.6.0` which I call the "Favicon Overhaul". This update provides significant changes to the FaviconHandler, providing a new feature in the form of Favicon merging and also a config.yml option to set how ASL should handle images with sizes that aren't exactly 64x64 pixels. ## FaviconHandler improvements The FaviconHandler has received major improvements. First of all are PlaceholderAPI placeholders now supported. Additionally was the async handling of Favicon creation simplified, as it was overcomplicated before. ## Favicon merging A new feature was added called favicon merging. With this feature are you able to combine multiple sources into a single favicon, allowing more complex, dynamic favicons to be created. To merge favicons, add new entries to the String separated by semicolons. As an example `${player uuid};border.png` would first place the Player head followed by putting `border.png` over it. The result would be similar to this:  ## Favicon resizing A new option called `faviconStrategy` was added to the `config.yml`. This option allows you to set how ASL should handle Images that have a size that isn't `64x64` pixels. The default option is `resize` but can be changed to `center` and `none`: - `center` does not resize the image, but instead centers it as good as possible in the Favicon. - `none` does not resize the image, nor move it. The image will simply placed at 0,0, which is the top-left corner of the Favicon. With these features should you be able to create some really cool Favicons for your server.

This update adds a `faviconStrategy: <string>` option to the config.yml This option allows you to change how AdvancedServerList should handle images for a favicon, that do not have a size of 64x64 pixels. The following Options are available: - `resize` (Default): Resizes the image to fit the 64x64 pixels area. - `center`: Doesn't resize the image, but instead centers it as good as possible. - `none`: Doesn't resize nor center the image. It simply puts it at 0,0 (top-left corner of the favicon) unchanged. Note that the favicon itself is always 64x64, even if the images depicted in it are smaller. This is simply due to Minecraft requiring such a size. This option should allow some creative aproaches with Favicons, especially when combined with the favicon merging published in the previous beta. Should there be no reports of bugs or similar do I plan to publish a proper release during the next week.

This update adds a `faviconStrategy: <string>` option to the config.yml This option allows you to change how AdvancedServerList should handle images for a favicon, that do not have a size of 64x64 pixels. The following Options are available: - `resize` (Default): Resizes the image to fit the 64x64 pixels area. - `center`: Doesn't resize the image, but instead centers it as good as possible. - `none`: Doesn't resize nor center the image. It simply puts it at 0,0 (top-left corner of the favicon) unchanged. Note that the favicon itself is always 64x64, even if the images depicted in it are smaller. This is simply due to Minecraft requiring such a size. This option should allow some creative aproaches with Favicons, especially when combined with the favicon merging published in the previous beta. Should there be no reports of bugs or similar do I plan to publish a proper release during the next week.

This update adds a `faviconStrategy: <string>` option to the config.yml This option allows you to change how AdvancedServerList should handle images for a favicon, that do not have a size of 64x64 pixels. The following Options are available: - `resize` (Default): Resizes the image to fit the 64x64 pixels area. - `center`: Doesn't resize the image, but instead centers it as good as possible. - `none`: Doesn't resize nor center the image. It simply puts it at 0,0 (top-left corner of the favicon) unchanged. Note that the favicon itself is always 64x64, even if the images depicted in it are smaller. This is simply due to Minecraft requiring such a size. This option should allow some creative aproaches with Favicons, especially when combined with the favicon merging published in the previous beta. Should there be no reports of bugs or similar do I plan to publish a proper release during the next week.

This Beta brings support for PlaceholderAPI placeholders in the Favicon and a new feature of Favicon merging! ### PlaceholderAPI support in favicon For whatever reason did the plugin not support placeholders from PlaceholderAPI in the favicon option. This has been changed now. ### Favicon merging The Favicon option now allows you to merge multiple values into a single Favicon to display. To use this option, separate each part with a semicolon. Each part supports the same options as a normal favicon, meaning you can use URLs, a placeholder that turns into a player name/UUID or an image name maching one in the favicons folder. As an example, setting `${player uuid};border.png` can return a favicon like this:  This should allow you to create more unique Favicons to display to players. Keep in mind, that each part follows the same rules as a normal favicon, meaning that images not having a size of 64x64 pixels will be resized accordingly. Also, the creation of such a Favicon is done asynchronously, similar to Favicons from a URL/placeholder. As such can it take a while for a Favicon to be displayed and may require more than one ping of the server. Please let me know about any issues you may encounter with this feature.

This Beta brings support for PlaceholderAPI placeholders in the Favicon and a new feature of Favicon merging! ### PlaceholderAPI support in favicon For whatever reason did the plugin not support placeholders from PlaceholderAPI in the favicon option. This has been changed now. ### Favicon merging The Favicon option now allows you to merge multiple values into a single Favicon to display. To use this option, separate each part with a semicolon. Each part supports the same options as a normal favicon, meaning you can use URLs, a placeholder that turns into a player name/UUID or an image name maching one in the favicons folder. As an example, setting `${player uuid};border.png` can return a favicon like this:  This should allow you to create more unique Favicons to display to players. Keep in mind, that each part follows the same rules as a normal favicon, meaning that images not having a size of 64x64 pixels will be resized accordingly. Also, the creation of such a Favicon is done asynchronously, similar to Favicons from a URL/placeholder. As such can it take a while for a Favicon to be displayed and may require more than one ping of the server. Please let me know about any issues you may encounter with this feature.

This Beta brings support for PlaceholderAPI placeholders in the Favicon and a new feature of Favicon merging! ### PlaceholderAPI support in favicon For whatever reason did the plugin not support placeholders from PlaceholderAPI in the favicon option. This has been changed now. ### Favicon merging The Favicon option now allows you to merge multiple values into a single Favicon to display. To use this option, separate each part with a semicolon. Each part supports the same options as a normal favicon, meaning you can use URLs, a placeholder that turns into a player name/UUID or an image name maching one in the favicons folder. As an example, setting `${player uuid};border.png` can return a favicon like this:  This should allow you to create more unique Favicons to display to players. Keep in mind, that each part follows the same rules as a normal favicon, meaning that images not having a size of 64x64 pixels will be resized accordingly. Also, the creation of such a Favicon is done asynchronously, similar to Favicons from a URL/placeholder. As such can it take a while for a Favicon to be displayed and may require more than one ping of the server. Please let me know about any issues you may encounter with this feature.

Fixes a NoClassDefFoundError you encounter on Paper. This was due to the fact that the cloud-paper dependency wasn't shaded into the jar itself.

Fixes a NoClassDefFoundError you encounter on Paper. This was due to the fact that the cloud-paper dependency wasn't shaded into the jar itself.

Fixes a NoClassDefFoundError you encounter on Paper. This was due to the fact that the cloud-paper dependency wasn't shaded into the jar itself.

This update brings three significant changes: The addition of new operands for the condition option, the move to cloud for command handling and some new commands. **Please note that I tried my best in testing these changes, but given I do not have an actual server can there be bugs and issues. Please report them to me if you encounter them!** Also, do note that the plugin now compiles against Java 21. But given there being no stats listing Java 16 should this not be an issue here. If it is for you, update your Java version please. ### New operands There are three new operands that can be used within your conditions: - `|~` Starts with (Ignoring case) - `~|` Ends with (Ignoring case) - `<~` Contains (Ignoring case) ### Move to cloud command framework The plugin is now shading in and using the Cloud command framework by incendo, to have some better overall handling of commands, including improved tab completion. The `/asl help` command has also been changed. It now uses the `MinecraftHelp` class from cloud to display a list of all available commands with hover and click actions. It also allows you to provide a query to search for specific commands (Has suggestions and tab completion available). ### New commands New commands have been added to further improve the handling of profiles in the plugin: `/asl profiles info <profile>` This command provides you with information regarding the selected profile. The returned tree will be a representation of the profile's options, including whether they are set or not and what value they may have. Additionally do most of these options have click actions to receive a matching `/asl profiles set` command to set or reset the value accordingly. `/asl profiles set <profile> <option> [value]` This command allows you to update an option's value. What values you can set depends on the provided option (i.e. `priority` only allows whole number values). The options `motd` and `playercount.hover` allow you to set multiple lines by using either `\n` or `<newline>` in the text. Finally can you also leave `[value]` blank to reset the option to its default value, which usually is an empty String or List. Note that the returned success response has a hover for the mentioned option that shows the old and new values you have set.

This update brings three significant changes: The addition of new operands for the condition option, the move to cloud for command handling and some new commands. **Please note that I tried my best in testing these changes, but given I do not have an actual server can there be bugs and issues. Please report them to me if you encounter them!** Also, do note that the plugin now compiles against Java 21. But given there being no stats listing Java 16 should this not be an issue here. If it is for you, update your Java version please. ### New operands There are three new operands that can be used within your conditions: - `|~` Starts with (Ignoring case) - `~|` Ends with (Ignoring case) - `<~` Contains (Ignoring case) ### Move to cloud command framework The plugin is now shading in and using the Cloud command framework by incendo, to have some better overall handling of commands, including improved tab completion. The `/asl help` command has also been changed. It now uses the `MinecraftHelp` class from cloud to display a list of all available commands with hover and click actions. It also allows you to provide a query to search for specific commands (Has suggestions and tab completion available). ### New commands New commands have been added to further improve the handling of profiles in the plugin: `/asl profiles info <profile>` This command provides you with information regarding the selected profile. The returned tree will be a representation of the profile's options, including whether they are set or not and what value they may have. Additionally do most of these options have click actions to receive a matching `/asl profiles set` command to set or reset the value accordingly. `/asl profiles set <profile> <option> [value]` This command allows you to update an option's value. What values you can set depends on the provided option (i.e. `priority` only allows whole number values). The options `motd` and `playercount.hover` allow you to set multiple lines by using either `\n` or `<newline>` in the text. Finally can you also leave `[value]` blank to reset the option to its default value, which usually is an empty String or List. Note that the returned success response has a hover for the mentioned option that shows the old and new values you have set.

This update brings three significant changes: The addition of new operands for the condition option, the move to cloud for command handling and some new commands. **Please note that I tried my best in testing these changes, but given I do not have an actual server can there be bugs and issues. Please report them to me if you encounter them!** Also, do note that the plugin now compiles against Java 21. But given there being no stats listing Java 16 should this not be an issue here. If it is for you, update your Java version please. ### New operands There are three new operands that can be used within your conditions: - `|~` Starts with (Ignoring case) - `~|` Ends with (Ignoring case) - `<~` Contains (Ignoring case) ### Move to cloud command framework The plugin is now shading in and using the Cloud command framework by incendo, to have some better overall handling of commands, including improved tab completion. The `/asl help` command has also been changed. It now uses the `MinecraftHelp` class from cloud to display a list of all available commands with hover and click actions. It also allows you to provide a query to search for specific commands (Has suggestions and tab completion available). ### New commands New commands have been added to further improve the handling of profiles in the plugin: `/asl profiles info <profile>` This command provides you with information regarding the selected profile. The returned tree will be a representation of the profile's options, including whether they are set or not and what value they may have. Additionally do most of these options have click actions to receive a matching `/asl profiles set` command to set or reset the value accordingly. `/asl profiles set <profile> <option> [value]` This command allows you to update an option's value. What values you can set depends on the provided option (i.e. `priority` only allows whole number values). The options `motd` and `playercount.hover` allow you to set multiple lines by using either `\n` or `<newline>` in the text. Finally can you also leave `[value]` blank to reset the option to its default value, which usually is an empty String or List. Note that the returned success response has a hover for the mentioned option that shows the old and new values you have set.

This is just a small fix to add `hidePlayersHover` to the `ignoreMaintenance` option in the config.yml alongside adding the option to the default.yml file. As usual should the plugin make a backup and migrate the config.yml on its own.

This is just a small fix to add `hidePlayersHover` to the `ignoreMaintenance` option in the config.yml alongside adding the option to the default.yml file. As usual should the plugin make a backup and migrate the config.yml on its own.

This is just a small fix to add `hidePlayersHover` to the `ignoreMaintenance` option in the config.yml alongside adding the option to the default.yml file. As usual should the plugin make a backup and migrate the config.yml on its own.

This update brings two changes to the plugin, the first being a new `playerCount` option called `hidePlayersHover` and the second being a small refactoring of the command usage output. ## New `hidePlayersHover` option This option is part of the `playerCount` option, similar to `hidePlayers`. When set to true will it remove the list of players (or custom text if `hover` is used) from the player count when hovering over it. Do note that I couldn't test this option properly, as I do not have a server with players on it to test, but it seems to work. Do also note, that enabling this will automatically disable the `hover` option. ## Smaller refactoring of the Command usage text The commands displayed when f.e. running `/asl help` is now a bit more detailed in terms of hovering over it. Individual arguments will now have a hover describing their purpose. Here are some screenshots:  

This update brings two changes to the plugin, the first being a new `playerCount` option called `hidePlayersHover` and the second being a small refactoring of the command usage output. ## New `hidePlayersHover` option This option is part of the `playerCount` option, similar to `hidePlayers`. When set to true will it remove the list of players (or custom text if `hover` is used) from the player count when hovering over it. Do note that I couldn't test this option properly, as I do not have a server with players on it to test, but it seems to work. Do also note, that enabling this will automatically disable the `hover` option. ## Smaller refactoring of the Command usage text The commands displayed when f.e. running `/asl help` is now a bit more detailed in terms of hovering over it. Individual arguments will now have a hover describing their purpose. Here are some screenshots:  

This update brings two changes to the plugin, the first being a new `playerCount` option called `hidePlayersHover` and the second being a small refactoring of the command usage output. ## New `hidePlayersHover` option This option is part of the `playerCount` option, similar to `hidePlayers`. When set to true will it remove the list of players (or custom text if `hover` is used) from the player count when hovering over it. Do note that I couldn't test this option properly, as I do not have a server with players on it to test, but it seems to work. Do also note, that enabling this will automatically disable the `hover` option. ## Smaller refactoring of the Command usage text The commands displayed when f.e. running `/asl help` is now a bit more detailed in terms of hovering over it. Individual arguments will now have a hover describing their purpose. Here are some screenshots:  

This update brings basic support for SayanVanish to the BungeeCord and Velocity versions of AdvancedServerList. ### What does this mean? Should a player be vanished through this plugin will AdvancedServerList not count it for the online player count, similar to how it did this for PremiumVanish already.

This update brings basic support for SayanVanish to the BungeeCord and Velocity versions of AdvancedServerList. ### What does this mean? Should a player be vanished through this plugin will AdvancedServerList not count it for the online player count, similar to how it did this for PremiumVanish already.

This update brings basic support for SayanVanish to the BungeeCord and Velocity versions of AdvancedServerList. ### What does this mean? Should a player be vanished through this plugin will AdvancedServerList not count it for the online player count, similar to how it did this for PremiumVanish already.

## Styled Log messages The plugin now makes use of the ComponentLogger provided by Kyori Adventure, allowing to have more styled messages. This Library was implemented into Paper around 2 years ago and into Velocity 3.2.0-SNAPSHOT. This means should you be using older versions will the plugin not function properly. BungeeCord won't use the componentlogger and therefore won't have styled log entries. ## Added `printBanner` config option The config.yml now has a `printBanner` boolean option. When set to false will the plugin no longer print the "ASL" ASCI art in the console. I personally can't see why this logo should bother you so much, but here you go if it really bothers you... As usual should the plugin automatically create a backup and migrate the config for you. If not present will the option default to `true`. ## Reduced startup messages The number of text printed in console on startup has been reduced. Some messages were removed, while others got moved into debug, meaning they only display when `debug` is enabled in the config.yml file.

## Styled Log messages The plugin now makes use of the ComponentLogger provided by Kyori Adventure, allowing to have more styled messages. This Library was implemented into Paper around 2 years ago and into Velocity 3.2.0-SNAPSHOT. This means should you be using older versions will the plugin not function properly. BungeeCord won't use the componentlogger and therefore won't have styled log entries. ## Added `printBanner` config option The config.yml now has a `printBanner` boolean option. When set to false will the plugin no longer print the "ASL" ASCI art in the console. I personally can't see why this logo should bother you so much, but here you go if it really bothers you... As usual should the plugin automatically create a backup and migrate the config for you. If not present will the option default to `true`. ## Reduced startup messages The number of text printed in console on startup has been reduced. Some messages were removed, while others got moved into debug, meaning they only display when `debug` is enabled in the config.yml file.

## Styled Log messages The plugin now makes use of the ComponentLogger provided by Kyori Adventure, allowing to have more styled messages. This Library was implemented into Paper around 2 years ago and into Velocity 3.2.0-SNAPSHOT. This means should you be using older versions will the plugin not function properly. BungeeCord won't use the componentlogger and therefore won't have styled log entries. ## Added `printBanner` config option The config.yml now has a `printBanner` boolean option. When set to false will the plugin no longer print the "ASL" ASCI art in the console. I personally can't see why this logo should bother you so much, but here you go if it really bothers you... As usual should the plugin automatically create a backup and migrate the config for you. If not present will the option default to `true`. ## Reduced startup messages The number of text printed in console on startup has been reduced. Some messages were removed, while others got moved into debug, meaning they only display when `debug` is enabled in the config.yml file.

Bit of an early christmas present for you all. This update provides a feature some of you have been waiting for: Center support for `motd`! It also has some notable changes making it incompatible with older Paper servers. ## MOTD Centering The feature is relatively simple. Start a line with `<center>` and the plugin will try to center it as good as possible using spaces. Example: ```yaml priority: 0 motd: - '<center><grey>This is <bold>centered</bold> Text!' - '<aqua>And I am not!' ``` Result:  The text is processed before centering, meaning that placeholders will be parsed first to get the actual text-width before centering. **Important:** Centering text uses specific hardcoded values and only supports a specific set of fonts. Namely: - Max width of MOTD is set to 270. - Spaces are set to a value of 4. - Supported fonts are `minecraft:default`, `minecraft:alt` and `minecraft:uniform` Because of these factors can the centering look not quite right on specific UI scales or with specific custom fonts used by the client. Nothing I can change on my end. ## plugin.yml removal I decided to remove the `plugin.yml` file from the Paper version of the Plugin. This means that if you were using the plugin on a version that doesn't support the `paper-plugin.yml` file, meaning only using the `plugin.yml`, this update won't work for you anymore. The `paper-plugin.yml` was introduced (And subsequently supported by AdvancedServerList) in 1.19 builds of Paper, tho notable breaking changes regarding dependencies were introduced in later 1.19.4 builds of Paper. To be on the safe side here will releases on Modrinth and Hangar now only list 1.20+ versions as supported.

Bit of an early christmas present for you all. This update provides a feature some of you have been waiting for: Center support for `motd`! It also has some notable changes making it incompatible with older Paper servers. ## MOTD Centering The feature is relatively simple. Start a line with `<center>` and the plugin will try to center it as good as possible using spaces. Example: ```yaml priority: 0 motd: - '<center><grey>This is <bold>centered</bold> Text!' - '<aqua>And I am not!' ``` Result:  The text is processed before centering, meaning that placeholders will be parsed first to get the actual text-width before centering. **Important:** Centering text uses specific hardcoded values and only supports a specific set of fonts. Namely: - Max width of MOTD is set to 270. - Spaces are set to a value of 4. - Supported fonts are `minecraft:default`, `minecraft:alt` and `minecraft:uniform` Because of these factors can the centering look not quite right on specific UI scales or with specific custom fonts used by the client. Nothing I can change on my end. ## plugin.yml removal I decided to remove the `plugin.yml` file from the Paper version of the Plugin. This means that if you were using the plugin on a version that doesn't support the `paper-plugin.yml` file, meaning only using the `plugin.yml`, this update won't work for you anymore. The `paper-plugin.yml` was introduced (And subsequently supported by AdvancedServerList) in 1.19 builds of Paper, tho notable breaking changes regarding dependencies were introduced in later 1.19.4 builds of Paper. To be on the safe side here will releases on Modrinth and Hangar now only list 1.20+ versions as supported.

Bit of an early christmas present for you all. This update provides a feature some of you have been waiting for: Center support for `motd`! It also has some notable changes making it incompatible with older Paper servers. ## MOTD Centering The feature is relatively simple. Start a line with `<center>` and the plugin will try to center it as good as possible using spaces. Example: ```yaml priority: 0 motd: - '<center><grey>This is <bold>centered</bold> Text!' - '<aqua>And I am not!' ``` Result:  The text is processed before centering, meaning that placeholders will be parsed first to get the actual text-width before centering. **Important:** Centering text uses specific hardcoded values and only supports a specific set of fonts. Namely: - Max width of MOTD is set to 270. - Spaces are set to a value of 4. - Supported fonts are `minecraft:default`, `minecraft:alt` and `minecraft:uniform` Because of these factors can the centering look not quite right on specific UI scales or with specific custom fonts used by the client. Nothing I can change on my end. ## plugin.yml removal I decided to remove the `plugin.yml` file from the Paper version of the Plugin. This means that if you were using the plugin on a version that doesn't support the `paper-plugin.yml` file, meaning only using the `plugin.yml`, this update won't work for you anymore. The `paper-plugin.yml` was introduced (And subsequently supported by AdvancedServerList) in 1.19 builds of Paper, tho notable breaking changes regarding dependencies were introduced in later 1.19.4 builds of Paper. To be on the safe side here will releases on Modrinth and Hangar now only list 1.20+ versions as supported.

This small update should *hopefully* fix an issue where a `IndexOutOfBoundsException` could be raised in Conditions if only using a placeholder. Truth be told, I'm not sure if this issue is fixed for good or not, as I wasn't really able to properly reproduce it. But the way I understand it is this: I had a system in place where the index (Current position in the full text) would be increased by one, if the placeholder was parsed in a condition. This had a unwanted side-effect here, where if you only used a Placeholder for the condition, it could cause the aforementioned exception. It could also happen, if the condition ended with a placeholder. As an example, here are the indexes indicated on a condition after handling the placeholder: ``` # This one is fine. ${player name} != "Anonymous" ^ # This one is Out of bounds ${player isWhitelisted} ^ # This one is also Out of bounds "Anonymous" != ${player name} ^ ``` I really hope this issue is now fixed, as I otherwise have no idea what could be the problem.

This small update should *hopefully* fix an issue where a `IndexOutOfBoundsException` could be raised in Conditions if only using a placeholder. Truth be told, I'm not sure if this issue is fixed for good or not, as I wasn't really able to properly reproduce it. But the way I understand it is this: I had a system in place where the index (Current position in the full text) would be increased by one, if the placeholder was parsed in a condition. This had a unwanted side-effect here, where if you only used a Placeholder for the condition, it could cause the aforementioned exception. It could also happen, if the condition ended with a placeholder. As an example, here are the indexes indicated on a condition after handling the placeholder: ``` # This one is fine. ${player name} != "Anonymous" ^ # This one is Out of bounds ${player isWhitelisted} ^ # This one is also Out of bounds "Anonymous" != ${player name} ^ ``` I really hope this issue is now fixed, as I otherwise have no idea what could be the problem.

This small update should *hopefully* fix an issue where a `IndexOutOfBoundsException` could be raised in Conditions if only using a placeholder. Truth be told, I'm not sure if this issue is fixed for good or not, as I wasn't really able to properly reproduce it. But the way I understand it is this: I had a system in place where the index (Current position in the full text) would be increased by one, if the placeholder was parsed in a condition. This had a unwanted side-effect here, where if you only used a Placeholder for the condition, it could cause the aforementioned exception. It could also happen, if the condition ended with a placeholder. As an example, here are the indexes indicated on a condition after handling the placeholder: ``` # This one is fine. ${player name} != "Anonymous" ^ # This one is Out of bounds ${player isWhitelisted} ^ # This one is also Out of bounds "Anonymous" != ${player name} ^ ``` I really hope this issue is now fixed, as I otherwise have no idea what could be the problem.

This is a small update that only changes the MiniMOTD Migrator. It now also converts "random" being set as favicon option given the recent update of allowing random favicon to be set in AdvancedServerList. Only other changes are some dependency bumps.

This is a small update that only changes the MiniMOTD Migrator. It now also converts "random" being set as favicon option given the recent update of allowing random favicon to be set in AdvancedServerList. Only other changes are some dependency bumps.

This is a small update that only changes the MiniMOTD Migrator. It now also converts "random" being set as favicon option given the recent update of allowing random favicon to be set in AdvancedServerList. Only other changes are some dependency bumps.

This update adds the option to set `random` as the favicon option. Doing so will make AdvancedServerList pick a random image from its favicons folder, if any are available. This can be useful for setups, where you want a randomized MOTD and Favicon without having to make `profiles` entries for every possible combination.

This update adds the option to set `random` as the favicon option. Doing so will make AdvancedServerList pick a random image from its favicons folder, if any are available. This can be useful for setups, where you want a randomized MOTD and Favicon without having to make `profiles` entries for every possible combination.

This update adds the option to set `random` as the favicon option. Doing so will make AdvancedServerList pick a random image from its favicons folder, if any are available. This can be useful for setups, where you want a randomized MOTD and Favicon without having to make `profiles` entries for every possible combination.

AdvancedServerList now caches the CompletableFuture PAPIProxyBridge gives for finding servers, rather than the actual result (which may be null). This should hopefully help in improving compatability of the plugin without having to block threads, causing larger delays.

AdvancedServerList now caches the CompletableFuture PAPIProxyBridge gives for finding servers, rather than the actual result (which may be null). This should hopefully help in improving compatability of the plugin without having to block threads, causing larger delays.

AdvancedServerList now caches the CompletableFuture PAPIProxyBridge gives for finding servers, rather than the actual result (which may be null). This should hopefully help in improving compatability of the plugin without having to block threads, causing larger delays.

Due to an oversights was hover text not being sent through PAPIProxyBridge to be parsed by PlaceholderAPI. This should now be fixed.

Due to an oversights was hover text not being sent through PAPIProxyBridge to be parsed by PlaceholderAPI. This should now be fixed.

Due to an oversights was hover text not being sent through PAPIProxyBridge to be parsed by PlaceholderAPI. This should now be fixed.

There is no longer a warning whenever the plugin is unable to ping a server. Other than that was there only some smaller code cleanup.

There is no longer a warning whenever the plugin is unable to ping a server. Other than that was there only some smaller code cleanup.

There is no longer a warning whenever the plugin is unable to ping a server. Other than that was there only some smaller code cleanup.

Another small fix for the BanPlugins Addon. This update fixes a wrong name for the Paper version, where the plugin expects AdvancedBans when it should be AdvancedBan.

Another small fix for the BanPlugins Addon. This update fixes a wrong name for the Paper version, where the plugin expects AdvancedBans when it should be AdvancedBan.

Another small fix for the BanPlugins Addon. This update fixes a wrong name for the Paper version, where the plugin expects AdvancedBans when it should be AdvancedBan.

This is a small bugfix correcting a wrongly set main class for the paper version of the BanPlugins Addon.

This is a small bugfix correcting a wrongly set main class for the paper version of the BanPlugins Addon.

This is a small bugfix correcting a wrongly set main class for the paper version of the BanPlugins Addon.

This is a major plugin release, meaning it has breaking changes due to API changes, making it incompatible with plugins using the v3 API of ASL. ## Breaking Changes - API was bumped to v4 due to major breaking changes: - `ProfileEntry#extraPlayersCount()` and `ProfileEntry#maxPlayersCount()` now return a String instead of an Integer. - Methods in `ProfileEntry.Builder` to set max and extra players count also have changed to accept Strings instead of Integers. - Deprecated methods in `ProfileEntry.Builder` have been removed. ## Additions - New Server List Profile Option `OnlinePlayers` - It allows to modify the online player count to any number value you like. - It has the same structure as the `ExtraPlayers` and `MaxPlayers` option, meaning it's under `PlayerCount` and has the options `Enabled: <boolean>` and `Amount: <String>` - Should an invalid number be provided will it default to the current online player counts. - **IMPORTANT:** Similar to `ExtraPlayers` and `MaxPlayers` influencing `${server playersMax}` does using this option modify `${server playersOnline}` (Except when used in `Condition`). It also alters the output of `ExtraPlayers` due to it adding `x` number to online players. - New `${proxy ...}` placeholders were added for the BungeeCord and Velocity version of the plugin. - These allow you to retrieve the motd, online players, max players, etc. of a Server connected to the proxy. - This system uses pinging servers every 10 seconds, so it may take a while for values to update properly. ## Changes - `ExtraPlayers` and `MaxPlayers` options now accept a String instead of an Integer. - This allows the usage of placeholders that return a number. - All `${server ...}` placeholders now return an empty String instead of `null`. - This should avoid random situations of some placeholders being treated as "invalid" despite being a supported placeholder. See [#317](https://codeberg.org/Andre601/AdvancedServerList/issues/317) for such a case. - Actually unknown placeholder values (i.e. `${server invalidValue}`) will still return `null` and be therefore treated as invalid.

This is a major plugin release, meaning it has breaking changes due to API changes, making it incompatible with plugins using the v3 API of ASL. ## Breaking Changes - API was bumped to v4 due to major breaking changes: - `ProfileEntry#extraPlayersCount()` and `ProfileEntry#maxPlayersCount()` now return a String instead of an Integer. - Methods in `ProfileEntry.Builder` to set max and extra players count also have changed to accept Strings instead of Integers. - Deprecated methods in `ProfileEntry.Builder` have been removed. ## Additions - New Server List Profile Option `OnlinePlayers` - It allows to modify the online player count to any number value you like. - It has the same structure as the `ExtraPlayers` and `MaxPlayers` option, meaning it's under `PlayerCount` and has the options `Enabled: <boolean>` and `Amount: <String>` - Should an invalid number be provided will it default to the current online player counts. - **IMPORTANT:** Similar to `ExtraPlayers` and `MaxPlayers` influencing `${server playersMax}` does using this option modify `${server playersOnline}` (Except when used in `Condition`). It also alters the output of `ExtraPlayers` due to it adding `x` number to online players. - New `${proxy ...}` placeholders were added for the BungeeCord and Velocity version of the plugin. - These allow you to retrieve the motd, online players, max players, etc. of a Server connected to the proxy. - This system uses pinging servers every 10 seconds, so it may take a while for values to update properly. ## Changes - `ExtraPlayers` and `MaxPlayers` options now accept a String instead of an Integer. - This allows the usage of placeholders that return a number. - All `${server ...}` placeholders now return an empty String instead of `null`. - This should avoid random situations of some placeholders being treated as "invalid" despite being a supported placeholder. See [#317](https://codeberg.org/Andre601/AdvancedServerList/issues/317) for such a case. - Actually unknown placeholder values (i.e. `${server invalidValue}`) will still return `null` and be therefore treated as invalid.

This is a major plugin release, meaning it has breaking changes due to API changes, making it incompatible with plugins using the v3 API of ASL. ## Breaking Changes - API was bumped to v4 due to major breaking changes: - `ProfileEntry#extraPlayersCount()` and `ProfileEntry#maxPlayersCount()` now return a String instead of an Integer. - Methods in `ProfileEntry.Builder` to set max and extra players count also have changed to accept Strings instead of Integers. - Deprecated methods in `ProfileEntry.Builder` have been removed. ## Additions - New Server List Profile Option `OnlinePlayers` - It allows to modify the online player count to any number value you like. - It has the same structure as the `ExtraPlayers` and `MaxPlayers` option, meaning it's under `PlayerCount` and has the options `Enabled: <boolean>` and `Amount: <String>` - Should an invalid number be provided will it default to the current online player counts. - **IMPORTANT:** Similar to `ExtraPlayers` and `MaxPlayers` influencing `${server playersMax}` does using this option modify `${server playersOnline}` (Except when used in `Condition`). It also alters the output of `ExtraPlayers` due to it adding `x` number to online players. - New `${proxy ...}` placeholders were added for the BungeeCord and Velocity version of the plugin. - These allow you to retrieve the motd, online players, max players, etc. of a Server connected to the proxy. - This system uses pinging servers every 10 seconds, so it may take a while for values to update properly. ## Changes - `ExtraPlayers` and `MaxPlayers` options now accept a String instead of an Integer. - This allows the usage of placeholders that return a number. - All `${server ...}` placeholders now return an empty String instead of `null`. - This should avoid random situations of some placeholders being treated as "invalid" despite being a supported placeholder. See [#317](https://codeberg.org/Andre601/AdvancedServerList/issues/317) for such a case. - Actually unknown placeholder values (i.e. `${server invalidValue}`) will still return `null` and be therefore treated as invalid.

This update fixes an issue, where the FaviconHandler stores local favicons using their non-lowercased file-names, while checking for an all-lowercased filename when getting it. This means, if you had a file named `Example.png` would the FaviconHandler save it as such but always check for `example.png`, which results in it failing. This has now been fixed.

This update fixes an issue, where the FaviconHandler stores local favicons using their non-lowercased file-names, while checking for an all-lowercased filename when getting it. This means, if you had a file named `Example.png` would the FaviconHandler save it as such but always check for `example.png`, which results in it failing. This has now been fixed.

This update fixes an issue, where the FaviconHandler stores local favicons using their non-lowercased file-names, while checking for an all-lowercased filename when getting it. This means, if you had a file named `Example.png` would the FaviconHandler save it as such but always check for `example.png`, which results in it failing. This has now been fixed.

A new Placeholder called `${maintenance maintenanceEnabled}` was added to the plugin. It gets registered when the [Maintenance Plugin](https://hangar.papermc.io/kennytv/Maintenance) by KennyTV is present on the server/proxy and allows you to return true or false based on if the global maintenance mode is active or not. Other than that have there mostly been some smaller code improvements to the plugin. You should (hopefully) not notice a difference.

A new Placeholder called `${maintenance maintenanceEnabled}` was added to the plugin. It gets registered when the [Maintenance Plugin](https://hangar.papermc.io/kennytv/Maintenance) by KennyTV is present on the server/proxy and allows you to return true or false based on if the global maintenance mode is active or not. Other than that have there mostly been some smaller code improvements to the plugin. You should (hopefully) not notice a difference.

A new Placeholder called `${maintenance maintenanceEnabled}` was added to the plugin. It gets registered when the [Maintenance Plugin](https://hangar.papermc.io/kennytv/Maintenance) by KennyTV is present on the server/proxy and allows you to return true or false based on if the global maintenance mode is active or not. Other than that have there mostly been some smaller code improvements to the plugin. You should (hopefully) not notice a difference.

The UpdateChecker has received some improvements to hopefully help in fixing lag and slowdowns in case the Modrinth API is down or struggling. The HTTPClient used now times out after 5 seconds of no response. In addition is the message players receive on join (if they have permissions) done inside a CompletableFuture's `whenComplete(...)` method, meaning the sending of the message is done outside the main thread itself, which should help reducing the load on the main thread.

The UpdateChecker has received some improvements to hopefully help in fixing lag and slowdowns in case the Modrinth API is down or struggling. The HTTPClient used now times out after 5 seconds of no response. In addition is the message players receive on join (if they have permissions) done inside a CompletableFuture's `whenComplete(...)` method, meaning the sending of the message is done outside the main thread itself, which should help reducing the load on the main thread.

The UpdateChecker has received some improvements to hopefully help in fixing lag and slowdowns in case the Modrinth API is down or struggling. The HTTPClient used now times out after 5 seconds of no response. In addition is the message players receive on join (if they have permissions) done inside a CompletableFuture's `whenComplete(...)` method, meaning the sending of the message is done outside the main thread itself, which should help reducing the load on the main thread.

This update fixes an issue, where the hover did not work when using the plugin on a 1.21 Paper Server. The reason was breaking changes within Paper's code (Which afaik go even back to the latest 1.20.6 builds) that made AdvancedServerList's way of updating the hover no longer functional. I've implemented a fix for this now. The plugin *should* also still work on older Server versions, but I want to emphasize that I do not guarantee this and should this old API be removed in the future, will I not implement a hacky backwards aproach but instead simply remove this old code. With that said will I still try to fix smaller issues with this hover, if they are within my skillset to do so.

This update fixes an issue, where the hover did not work when using the plugin on a 1.21 Paper Server. The reason was breaking changes within Paper's code (Which afaik go even back to the latest 1.20.6 builds) that made AdvancedServerList's way of updating the hover no longer functional. I've implemented a fix for this now. The plugin *should* also still work on older Server versions, but I want to emphasize that I do not guarantee this and should this old API be removed in the future, will I not implement a hacky backwards aproach but instead simply remove this old code. With that said will I still try to fix smaller issues with this hover, if they are within my skillset to do so.

This update fixes an issue, where the hover did not work when using the plugin on a 1.21 Paper Server. The reason was breaking changes within Paper's code (Which afaik go even back to the latest 1.20.6 builds) that made AdvancedServerList's way of updating the hover no longer functional. I've implemented a fix for this now. The plugin *should* also still work on older Server versions, but I want to emphasize that I do not guarantee this and should this old API be removed in the future, will I not implement a hacky backwards aproach but instead simply remove this old code. With that said will I still try to fix smaller issues with this hover, if they are within my skillset to do so.

This is a small update that only updates some dependencies which also adds proper support for 1.20.6 in BungeeCord (Which wasn't the case before, because apparently adventure platform bungeecord wasn't supporting it.)

This is a small update that only updates some dependencies which also adds proper support for 1.20.6 in BungeeCord (Which wasn't the case before, because apparently adventure platform bungeecord wasn't supporting it.)

This is a small update that only updates some dependencies which also adds proper support for 1.20.6 in BungeeCord (Which wasn't the case before, because apparently adventure platform bungeecord wasn't supporting it.)

This update reworks the command handling a bit while also adding a new sub-command called `profiles`. ### Command overhaul The command system has been tweaked to add some quality of life changes. Namely, the help command now contains hover and click actions for the listed commands, to show usage of command, permission required and description respectively, while also putting the sub-command into your chat-bar when clicking it. ### Profiles sub-command A new `profiles` sub-command has been added. It allows you an easier creation of new profiles. There are the following options available: - `/asl profiles add <profile>` - Create a new Profile with file name `<profile>` - `/asl profiles copy <profile> <name>` - Make a copy of `<profile>` and save it as file `<name>` - `/asl profiles list` - Show all loaded profiles. This list has hover text showing priority, condition and whether the profile is considered valid. ### Screenshots Here are some screenshots showing all the changes.  

This update reworks the command handling a bit while also adding a new sub-command called `profiles`. ### Command overhaul The command system has been tweaked to add some quality of life changes. Namely, the help command now contains hover and click actions for the listed commands, to show usage of command, permission required and description respectively, while also putting the sub-command into your chat-bar when clicking it. ### Profiles sub-command A new `profiles` sub-command has been added. It allows you an easier creation of new profiles. There are the following options available: - `/asl profiles add <profile>` - Create a new Profile with file name `<profile>` - `/asl profiles copy <profile> <name>` - Make a copy of `<profile>` and save it as file `<name>` - `/asl profiles list` - Show all loaded profiles. This list has hover text showing priority, condition and whether the profile is considered valid. ### Screenshots Here are some screenshots showing all the changes.  

This update reworks the command handling a bit while also adding a new sub-command called `profiles`. ### Command overhaul The command system has been tweaked to add some quality of life changes. Namely, the help command now contains hover and click actions for the listed commands, to show usage of command, permission required and description respectively, while also putting the sub-command into your chat-bar when clicking it. ### Profiles sub-command A new `profiles` sub-command has been added. It allows you an easier creation of new profiles. There are the following options available: - `/asl profiles add <profile>` - Create a new Profile with file name `<profile>` - `/asl profiles copy <profile> <name>` - Make a copy of `<profile>` and save it as file `<name>` - `/asl profiles list` - Show all loaded profiles. This list has hover text showing priority, condition and whether the profile is considered valid. ### Screenshots Here are some screenshots showing all the changes.  

This update adds MiniMOTD as a supported migration option to the plugin, meaning you can now migrate from MiniMOTD to AdvancedServerList. It is important to note, that only the `main.conf` will be migrated as of right now. The positive side however, is that the MiniMOTD plugin does not need to be present for migration. Only its `main.conf` file in the `MiniMOTD` (or `minimotd-velocity` on Velocity) folder has to be present. As a final note do I want to mention, that the plugin will download and use the configurate-hocon library when you start your migration. This is similar to the BungeeCord version downloading necessary libraries on startup, but a bit more dynamic.

This update adds MiniMOTD as a supported migration option to the plugin, meaning you can now migrate from MiniMOTD to AdvancedServerList. It is important to note, that only the `main.conf` will be migrated as of right now. The positive side however, is that the MiniMOTD plugin does not need to be present for migration. Only its `main.conf` file in the `MiniMOTD` (or `minimotd-velocity` on Velocity) folder has to be present. As a final note do I want to mention, that the plugin will download and use the configurate-hocon library when you start your migration. This is similar to the BungeeCord version downloading necessary libraries on startup, but a bit more dynamic.

This update adds MiniMOTD as a supported migration option to the plugin, meaning you can now migrate from MiniMOTD to AdvancedServerList. It is important to note, that only the `main.conf` will be migrated as of right now. The positive side however, is that the MiniMOTD plugin does not need to be present for migration. Only its `main.conf` file in the `MiniMOTD` (or `minimotd-velocity` on Velocity) folder has to be present. As a final note do I want to mention, that the plugin will download and use the configurate-hocon library when you start your migration. This is similar to the BungeeCord version downloading necessary libraries on startup, but a bit more dynamic.

This update bumps the API version used for the Paper version to 1.20.6. With that said should the plugin remain backwards compatible (Tested on a 1.20.4 Paper Server). This update also uses the new BuildInfo class introduced in Paper that will display more useful information at startup, namely, if present will the plugin now print either `Platform: Paper (ID: papermc:paper, Version: 1.20.6, Build: 79)` if a build number is known or `Platform: Paper (ID: papermc:paper, Version: 1.20.6)` if no build is known. On older versions will it print out the previous info. Finally, this version also fixes a small bug where a backup is created of the config.yml on first creation due to it using `config-version` instead of the expected `configVersion` key.

This update bumps the API version used for the Paper version to 1.20.6. With that said should the plugin remain backwards compatible (Tested on a 1.20.4 Paper Server). This update also uses the new BuildInfo class introduced in Paper that will display more useful information at startup, namely, if present will the plugin now print either `Platform: Paper (ID: papermc:paper, Version: 1.20.6, Build: 79)` if a build number is known or `Platform: Paper (ID: papermc:paper, Version: 1.20.6)` if no build is known. On older versions will it print out the previous info. Finally, this version also fixes a small bug where a backup is created of the config.yml on first creation due to it using `config-version` instead of the expected `configVersion` key.

This update bumps the API version used for the Paper version to 1.20.6. With that said should the plugin remain backwards compatible (Tested on a 1.20.4 Paper Server). This update also uses the new BuildInfo class introduced in Paper that will display more useful information at startup, namely, if present will the plugin now print either `Platform: Paper (ID: papermc:paper, Version: 1.20.6, Build: 79)` if a build number is known or `Platform: Paper (ID: papermc:paper, Version: 1.20.6)` if no build is known. On older versions will it print out the previous info. Finally, this version also fixes a small bug where a backup is created of the config.yml on first creation due to it using `config-version` instead of the expected `configVersion` key.

This is a small update adding the missing `${litebans muteDuration}` and `${litebans banDuration}` placeholders to the BanPlugins Addon.

This is a small update adding the missing `${litebans muteDuration}` and `${litebans banDuration}` placeholders to the BanPlugins Addon.

This is a small update adding the missing `${litebans muteDuration}` and `${litebans banDuration}` placeholders to the BanPlugins Addon.

This update is solely for the BanPlugins Addon, by bringing support for [LiteBans](https://www.spigotmc.org/resources/3715/) alongside some fixes with the Velocity site.

This update is solely for the BanPlugins Addon, by bringing support for [LiteBans](https://www.spigotmc.org/resources/3715/) alongside some fixes with the Velocity site.

This update is solely for the BanPlugins Addon, by bringing support for [LiteBans](https://www.spigotmc.org/resources/3715/) alongside some fixes with the Velocity site.

This is the stable release of the previous Beta releases of the plugin, bringing support for migrating from ServerListPlus to AdvancedServerList, fixing an issue on more recent Paper releases and updating PAPIProxyBridge support. Speaking of, this and future updates will **only be compatible with PAPIProxyBridge 1.6.1 and newer**. This is due to changes in their API that makes supporting it more complicated, if backwards compat is wanted. ### Changes from previous beta releases: - `v4.8.0-b1`: Add support to migrate from ServerListPlus to AdvancedServerList - `v4.8.0-b2`: Updating Adventure dependencies for proper 1.20.5/6 support. - `v4.8.0-b3`: Fix plugin creating a single, empty profiles entry on migration. - `v4.8.0-b4`: Fix IllegalArgumentException when using Strings longer than 16 characters for hover. - `v4.8.0-b5`: Fix a breaking change in latest PAPIProxyBridge update. - `v4.8.0-b6`: Fix player count text being broken and add workaround for the 16 character limit.

This is the stable release of the previous Beta releases of the plugin, bringing support for migrating from ServerListPlus to AdvancedServerList, fixing an issue on more recent Paper releases and updating PAPIProxyBridge support. Speaking of, this and future updates will **only be compatible with PAPIProxyBridge 1.6.1 and newer**. This is due to changes in their API that makes supporting it more complicated, if backwards compat is wanted. ### Changes from previous beta releases: - `v4.8.0-b1`: Add support to migrate from ServerListPlus to AdvancedServerList - `v4.8.0-b2`: Updating Adventure dependencies for proper 1.20.5/6 support. - `v4.8.0-b3`: Fix plugin creating a single, empty profiles entry on migration. - `v4.8.0-b4`: Fix IllegalArgumentException when using Strings longer than 16 characters for hover. - `v4.8.0-b5`: Fix a breaking change in latest PAPIProxyBridge update. - `v4.8.0-b6`: Fix player count text being broken and add workaround for the 16 character limit.

This is the stable release of the previous Beta releases of the plugin, bringing support for migrating from ServerListPlus to AdvancedServerList, fixing an issue on more recent Paper releases and updating PAPIProxyBridge support. Speaking of, this and future updates will **only be compatible with PAPIProxyBridge 1.6.1 and newer**. This is due to changes in their API that makes supporting it more complicated, if backwards compat is wanted. ### Changes from previous beta releases: - `v4.8.0-b1`: Add support to migrate from ServerListPlus to AdvancedServerList - `v4.8.0-b2`: Updating Adventure dependencies for proper 1.20.5/6 support. - `v4.8.0-b3`: Fix plugin creating a single, empty profiles entry on migration. - `v4.8.0-b4`: Fix IllegalArgumentException when using Strings longer than 16 characters for hover. - `v4.8.0-b5`: Fix a breaking change in latest PAPIProxyBridge update. - `v4.8.0-b6`: Fix player count text being broken and add workaround for the 16 character limit.

This update fixes a mistake I made, causing the Player count text to display wrong (I removed a method that was still used. Oops). But more importantly does this add a temporary workaround for paper servers to not have the 16 character limit on the hover, meaning you should now be able again to have text that is longer than 16 characters. There is a small chance that in the future, Paper will implement something on their end too, so that this "hack" isn't required. Since BungeeCord and Velocity don't have these checks (yet) did I also remove the limit on their end with no other changes.

This update fixes a mistake I made, causing the Player count text to display wrong (I removed a method that was still used. Oops). But more importantly does this add a temporary workaround for paper servers to not have the 16 character limit on the hover, meaning you should now be able again to have text that is longer than 16 characters. There is a small chance that in the future, Paper will implement something on their end too, so that this "hack" isn't required. Since BungeeCord and Velocity don't have these checks (yet) did I also remove the limit on their end with no other changes.

This update fixes a mistake I made, causing the Player count text to display wrong (I removed a method that was still used. Oops). But more importantly does this add a temporary workaround for paper servers to not have the 16 character limit on the hover, meaning you should now be able again to have text that is longer than 16 characters. There is a small chance that in the future, Paper will implement something on their end too, so that this "hack" isn't required. Since BungeeCord and Velocity don't have these checks (yet) did I also remove the limit on their end with no other changes.

And another update due to breaking changes. This time is PAPIProxyBridge the issue. The plugin introduced a breaking change in its latest update, that hasn't been mentioned at all. The change was that `findServers()` - a method to get all servers with PAPIProxyBridge on it - now returns a `Set<String>` instead of a `List<String>`, which breaks AdvancedServerList's compat with it. Why this breaking change was made and why it wasn't mentioned in the changelogs is beyond my understanding, but the issue *should* be fixed, while the plugin keeps compatability with older versions...

And another update due to breaking changes. This time is PAPIProxyBridge the issue. The plugin introduced a breaking change in its latest update, that hasn't been mentioned at all. The change was that `findServers()` - a method to get all servers with PAPIProxyBridge on it - now returns a `Set<String>` instead of a `List<String>`, which breaks AdvancedServerList's compat with it. Why this breaking change was made and why it wasn't mentioned in the changelogs is beyond my understanding, but the issue *should* be fixed, while the plugin keeps compatability with older versions...

And another update due to breaking changes. This time is PAPIProxyBridge the issue. The plugin introduced a breaking change in its latest update, that hasn't been mentioned at all. The change was that `findServers()` - a method to get all servers with PAPIProxyBridge on it - now returns a `Set<String>` instead of a `List<String>`, which breaks AdvancedServerList's compat with it. Why this breaking change was made and why it wasn't mentioned in the changelogs is beyond my understanding, but the issue *should* be fixed, while the plugin keeps compatability with older versions...

Paper introduced a change **unannounced** where creating a Player Profile with a name that is longer than 16 characters will give an error back. Given that AdvancedServerList is creating fake Player Profiles for the hover text feature, does this break it unintentionally. To fix this does the plugin now limit the text size to 16 characters at most. Keep in mind that the text length is checked **after** color and formatting codes and placeholders have been parsed, so a text like `<gold>Hello ${player name}` would be parsed to `§6Hello Andre_601` which counts as 17 characters, so the text used would be `§6Hello Andre_60`. This is nothing I have control over and sadly something you can blame Mojang for, as Paper had to adabt to their changes here...

Paper introduced a change **unannounced** where creating a Player Profile with a name that is longer than 16 characters will give an error back. Given that AdvancedServerList is creating fake Player Profiles for the hover text feature, does this break it unintentionally. To fix this does the plugin now limit the text size to 16 characters at most. Keep in mind that the text length is checked **after** color and formatting codes and placeholders have been parsed, so a text like `<gold>Hello ${player name}` would be parsed to `§6Hello Andre_601` which counts as 17 characters, so the text used would be `§6Hello Andre_60`. This is nothing I have control over and sadly something you can blame Mojang for, as Paper had to adabt to their changes here...

Paper introduced a change **unannounced** where creating a Player Profile with a name that is longer than 16 characters will give an error back. Given that AdvancedServerList is creating fake Player Profiles for the hover text feature, does this break it unintentionally. To fix this does the plugin now limit the text size to 16 characters at most. Keep in mind that the text length is checked **after** color and formatting codes and placeholders have been parsed, so a text like `<gold>Hello ${player name}` would be parsed to `§6Hello Andre_601` which counts as 17 characters, so the text used would be `§6Hello Andre_60`. This is nothing I have control over and sadly something you can blame Mojang for, as Paper had to adabt to their changes here...

The migrator will no longer create a `profiles` option with a single entry containing empty options. Only when there are at least two entries of one option will a profiles option be generated. The Migration page also has been updated with some better explanations and examples. Finally, should there not be any reports within the next couple of days will I consider this version stable and create a proper release for it.

The migrator will no longer create a `profiles` option with a single entry containing empty options. Only when there are at least two entries of one option will a profiles option be generated. The Migration page also has been updated with some better explanations and examples. Finally, should there not be any reports within the next couple of days will I consider this version stable and create a proper release for it.

The migrator will no longer create a `profiles` option with a single entry containing empty options. Only when there are at least two entries of one option will a profiles option be generated. The Migration page also has been updated with some better explanations and examples. Finally, should there not be any reports within the next couple of days will I consider this version stable and create a proper release for it.

This is a small update that only updates some dependencies, namely MiniMessage and the legacy Serializer, while also improving the messages for migrating from ServerListPlus. This should also be the first release that officially supports 1.20.5/6 thanks to the aforementioned dependencies updating.

This is a small update that only updates some dependencies, namely MiniMessage and the legacy Serializer, while also improving the messages for migrating from ServerListPlus. This should also be the first release that officially supports 1.20.5/6 thanks to the aforementioned dependencies updating.

This is a small update that only updates some dependencies, namely MiniMessage and the legacy Serializer, while also improving the messages for migrating from ServerListPlus. This should also be the first release that officially supports 1.20.5/6 thanks to the aforementioned dependencies updating.

This update brings a huge change to the plugin. Namely, you are now able to migrate your pre-existing ServerListPlus configuration over to AdvancedServerList! The migration supports the configuration types `Default`, `Personalized` and `Banned`, creating separate files for each if present. To migrate, make sure that ServerListPlus is present on your server/proxy alongside AdvancedServerList. Then, run `/asl migrate serverlistplus` to start the migration process. If everything goes well should you get new YAML files in the `profiles` folder with names `slp_<type>.yml`. See the new [Migration page](https://asl.andre601.ch/migration/serverlistplus/) for more details, like what placeholders and patterns get converted. ### Other changes The library loader on the bungeecord version has been adjusted to now use a internal JSON file for the dependency resolving. Nothing should change for you on the outside.

This update brings a huge change to the plugin. Namely, you are now able to migrate your pre-existing ServerListPlus configuration over to AdvancedServerList! The migration supports the configuration types `Default`, `Personalized` and `Banned`, creating separate files for each if present. To migrate, make sure that ServerListPlus is present on your server/proxy alongside AdvancedServerList. Then, run `/asl migrate serverlistplus` to start the migration process. If everything goes well should you get new YAML files in the `profiles` folder with names `slp_<type>.yml`. See the new [Migration page](https://asl.andre601.ch/migration/serverlistplus/) for more details, like what placeholders and patterns get converted. ### Other changes The library loader on the bungeecord version has been adjusted to now use a internal JSON file for the dependency resolving. Nothing should change for you on the outside.

This update brings a huge change to the plugin. Namely, you are now able to migrate your pre-existing ServerListPlus configuration over to AdvancedServerList! The migration supports the configuration types `Default`, `Personalized` and `Banned`, creating separate files for each if present. To migrate, make sure that ServerListPlus is present on your server/proxy alongside AdvancedServerList. Then, run `/asl migrate serverlistplus` to start the migration process. If everything goes well should you get new YAML files in the `profiles` folder with names `slp_<type>.yml`. See the new [Migration page](https://asl.andre601.ch/migration/serverlistplus/) for more details, like what placeholders and patterns get converted. ### Other changes The library loader on the bungeecord version has been adjusted to now use a internal JSON file for the dependency resolving. Nothing should change for you on the outside.

The BungeeCord version of AdvancedServerList now uses a library loader to download and apply necessary libraries not present within the proxy itself. Namely, the plugin will now download the following libraries into `/plugins/AdvancedServerList/libs/` on load: - Adventure-API - Adventure-text-minimessage (MiniMessage API) - Adventure-platform-bungeecord (BungeeCord compat API) - Configurate-yaml (YAML configuration library)

The BungeeCord version of AdvancedServerList now uses a library loader to download and apply necessary libraries not present within the proxy itself. Namely, the plugin will now download the following libraries into `/plugins/AdvancedServerList/libs/` on load: - Adventure-API - Adventure-text-minimessage (MiniMessage API) - Adventure-platform-bungeecord (BungeeCord compat API) - Configurate-yaml (YAML configuration library)

The BungeeCord version of AdvancedServerList now uses a library loader to download and apply necessary libraries not present within the proxy itself. Namely, the plugin will now download the following libraries into `/plugins/AdvancedServerList/libs/` on load: - Adventure-API - Adventure-text-minimessage (MiniMessage API) - Adventure-platform-bungeecord (BungeeCord compat API) - Configurate-yaml (YAML configuration library)

The ExpressionParser library used in AdvancedSercerList has been updated to fix a possible NumberFormatException from appear in specific scenarios (i.e. a number with 2 dots). Nothing else has changed.

The ExpressionParser library used in AdvancedSercerList has been updated to fix a possible NumberFormatException from appear in specific scenarios (i.e. a number with 2 dots). Nothing else has changed.

The ExpressionParser library used in AdvancedSercerList has been updated to fix a possible NumberFormatException from appear in specific scenarios (i.e. a number with 2 dots). Nothing else has changed.

AdvancedServerList will now inform you about new updates being available when you join your server. To get these notifications, you need to have the new `advancedserverlist.updatecheck` permission, or the main `advancedserverlist.admin` permission. It also won't display anything if you disabled update checking.

AdvancedServerList will now inform you about new updates being available when you join your server. To get these notifications, you need to have the new `advancedserverlist.updatecheck` permission, or the main `advancedserverlist.admin` permission. It also won't display anything if you disabled update checking.

AdvancedServerList will now inform you about new updates being available when you join your server. To get these notifications, you need to have the new `advancedserverlist.updatecheck` permission, or the main `advancedserverlist.admin` permission. It also won't display anything if you disabled update checking.

This is a rather embarassing update for me... AdvancedServerList has been using the wrong protocol version for the `${player protocol}` placeholder. Instead of actually using the protocol the player uses, it used the protocol the proxy was using. This could mean that the protocol returned could be different, depending on whether servers were connected to the proxy or not. This should hopefully be fixed now. ### Clarification on BungeeCord/Waterfall support My last post on this was unfortunately not to well written and may have caused confusion, so I take the oportunity to clarify this a bit now: AdvancedServerList will keep support for BungeeCord, Waterfall and whatever other fork it may support here. **However!** Should there be any major breaking changes in the future (Which I doubt given BungeeCords conservative aproach on those) will I not try to fix those breaking changes and instead drop support altogether. This means that for as long as the API doesn't introduce breaking changes, AdvancedServerList will support it.

This is a rather embarassing update for me... AdvancedServerList has been using the wrong protocol version for the `${player protocol}` placeholder. Instead of actually using the protocol the player uses, it used the protocol the proxy was using. This could mean that the protocol returned could be different, depending on whether servers were connected to the proxy or not. This should hopefully be fixed now. ### Clarification on BungeeCord/Waterfall support My last post on this was unfortunately not to well written and may have caused confusion, so I take the oportunity to clarify this a bit now: AdvancedServerList will keep support for BungeeCord, Waterfall and whatever other fork it may support here. **However!** Should there be any major breaking changes in the future (Which I doubt given BungeeCords conservative aproach on those) will I not try to fix those breaking changes and instead drop support altogether. This means that for as long as the API doesn't introduce breaking changes, AdvancedServerList will support it.

This is a rather embarassing update for me... AdvancedServerList has been using the wrong protocol version for the `${player protocol}` placeholder. Instead of actually using the protocol the player uses, it used the protocol the proxy was using. This could mean that the protocol returned could be different, depending on whether servers were connected to the proxy or not. This should hopefully be fixed now. ### Clarification on BungeeCord/Waterfall support My last post on this was unfortunately not to well written and may have caused confusion, so I take the oportunity to clarify this a bit now: AdvancedServerList will keep support for BungeeCord, Waterfall and whatever other fork it may support here. **However!** Should there be any major breaking changes in the future (Which I doubt given BungeeCords conservative aproach on those) will I not try to fix those breaking changes and instead drop support altogether. This means that for as long as the API doesn't introduce breaking changes, AdvancedServerList will support it.

There was a mistake in the LibertyBans placeholder, which would've resulted in the placeholder not being handled properly. It should be fixed now. ### State on BungeeCord/Waterfall support PaperMC announced the [End of Life for Waterfall](https://forums.papermc.io/threads/1088/), meaning it won't receive proper updates and/or support anymore. Regarding AdvancedServerList's support for it will I say this: BungeeCord and Waterfall remain supported by me, but I may not work on proper updates in the future, should there be breaking changes. If you can, use Velocity instead, as it offers much better performance and security compared to BungeeCord.

There was a mistake in the LibertyBans placeholder, which would've resulted in the placeholder not being handled properly. It should be fixed now. ### State on BungeeCord/Waterfall support PaperMC announced the [End of Life for Waterfall](https://forums.papermc.io/threads/1088/), meaning it won't receive proper updates and/or support anymore. Regarding AdvancedServerList's support for it will I say this: BungeeCord and Waterfall remain supported by me, but I may not work on proper updates in the future, should there be breaking changes. If you can, use Velocity instead, as it offers much better performance and security compared to BungeeCord.

There was a mistake in the LibertyBans placeholder, which would've resulted in the placeholder not being handled properly. It should be fixed now. ### State on BungeeCord/Waterfall support PaperMC announced the [End of Life for Waterfall](https://forums.papermc.io/threads/1088/), meaning it won't receive proper updates and/or support anymore. Regarding AdvancedServerList's support for it will I say this: BungeeCord and Waterfall remain supported by me, but I may not work on proper updates in the future, should there be breaking changes. If you can, use Velocity instead, as it offers much better performance and security compared to BungeeCord.

This update adds a new Event called `PostServerListSetEvent` to the plugin. Its main purpose is to allow other plugins to know when AdvancedServerList is "done" with updating the Server List. It also provides a Getter to retrieve the ProfileEntry that was used during the PingEvent. Do note tho that said ProfileEntry is not a representation of the final server list content, but just what has been used during the PingEvent. It can also be null, should the PingEvent handling get cancelled.

This update adds a new Event called `PostServerListSetEvent` to the plugin. Its main purpose is to allow other plugins to know when AdvancedServerList is "done" with updating the Server List. It also provides a Getter to retrieve the ProfileEntry that was used during the PingEvent. Do note tho that said ProfileEntry is not a representation of the final server list content, but just what has been used during the PingEvent. It can also be null, should the PingEvent handling get cancelled.

This update adds a new Event called `PostServerListSetEvent` to the plugin. Its main purpose is to allow other plugins to know when AdvancedServerList is "done" with updating the Server List. It also provides a Getter to retrieve the ProfileEntry that was used during the PingEvent. Do note tho that said ProfileEntry is not a representation of the final server list content, but just what has been used during the PingEvent. It can also be null, should the PingEvent handling get cancelled.

New config options have been added to allow you to set what options of a server list profile AdvancedServerList should not modify when the Maintenance plugin is active (Maintenance is enabled). These are the new options and their default values: ```yaml disableDuringMaintenance: motd: true favicon: true hidePlayers: true playerCountText: true playerCountHover: true extraPlayers: true maxPlayers: true ``` The config should, as always, be automatically migrated and these new options added. And to be clear: Setting an option to `true` **disables** it while maintenance mode is active. Thanks to EpicPlayerA10 on Codeberg for the initial Pull request and idea.

New config options have been added to allow you to set what options of a server list profile AdvancedServerList should not modify when the Maintenance plugin is active (Maintenance is enabled). These are the new options and their default values: ```yaml disableDuringMaintenance: motd: true favicon: true hidePlayers: true playerCountText: true playerCountHover: true extraPlayers: true maxPlayers: true ``` The config should, as always, be automatically migrated and these new options added. And to be clear: Setting an option to `true` **disables** it while maintenance mode is active. Thanks to EpicPlayerA10 on Codeberg for the initial Pull request and idea.

New config options have been added to allow you to set what options of a server list profile AdvancedServerList should not modify when the Maintenance plugin is active (Maintenance is enabled). These are the new options and their default values: ```yaml disableDuringMaintenance: motd: true favicon: true hidePlayers: true playerCountText: true playerCountHover: true extraPlayers: true maxPlayers: true ``` The config should, as always, be automatically migrated and these new options added. And to be clear: Setting an option to `true` **disables** it while maintenance mode is active. Thanks to EpicPlayerA10 on Codeberg for the initial Pull request and idea.

The `${server playersOnline}` placeholder now won't include players anymore, which are currently vanished. Right now does only the Paper version support most vanish plugins, by checking for the `vanished` Metadata in the player. The BungeeCord and Velocity version use the API of PremiumVanish for this, so keep this in mind. Additionally has the way of parsing own placeholders been merged, as it was separated for conditions and everything else. I tested it and it works, but I would appreciate if you can report any issues to me, should you encounter some strange parsing errors.

The `${server playersOnline}` placeholder now won't include players anymore, which are currently vanished. Right now does only the Paper version support most vanish plugins, by checking for the `vanished` Metadata in the player. The BungeeCord and Velocity version use the API of PremiumVanish for this, so keep this in mind. Additionally has the way of parsing own placeholders been merged, as it was separated for conditions and everything else. I tested it and it works, but I would appreciate if you can report any issues to me, should you encounter some strange parsing errors.

The `${server playersOnline}` placeholder now won't include players anymore, which are currently vanished. Right now does only the Paper version support most vanish plugins, by checking for the `vanished` Metadata in the player. The BungeeCord and Velocity version use the API of PremiumVanish for this, so keep this in mind. Additionally has the way of parsing own placeholders been merged, as it was separated for conditions and everything else. I tested it and it works, but I would appreciate if you can report any issues to me, should you encounter some strange parsing errors.

This is a smaller update that changes how AdvancedServerList reports wrong/invalid conditions when evaluating them. The new error is now one of two possible structures. It's either: ``` [00:00:00 WARN]: [AdvancedServerList] Encountered 1 Error(s) while parsing condition for file 'default.yml': [00:00:00 WARN]: [AdvancedServerList] - "Something" == ${invalid placeholder} [00:00:00 WARN]: [AdvancedServerList] -> Placeholder '${invalid placeholder}' does not have any available PlaceholderProvider ``` when no exact location is known or ``` [00:00:00 WARN]: [AdvancedServerList] Encountered 1 Error(s) while parsing condition for file 'default.yml': [00:00:00 WARN]: [AdvancedServerList] - At Position 15: [00:00:00 WARN]: [AdvancedServerList] "Something" == ${invalid placeholder} [00:00:00 WARN]: [AdvancedServerList] ^ [00:00:00 WARN]: [AdvancedServerList] -> Placeholder '${invalid placeholder}' does not have any available PlaceholderProvider ``` if the location is known.

This is a smaller update that changes how AdvancedServerList reports wrong/invalid conditions when evaluating them. The new error is now one of two possible structures. It's either: ``` [00:00:00 WARN]: [AdvancedServerList] Encountered 1 Error(s) while parsing condition for file 'default.yml': [00:00:00 WARN]: [AdvancedServerList] - "Something" == ${invalid placeholder} [00:00:00 WARN]: [AdvancedServerList] -> Placeholder '${invalid placeholder}' does not have any available PlaceholderProvider ``` when no exact location is known or ``` [00:00:00 WARN]: [AdvancedServerList] Encountered 1 Error(s) while parsing condition for file 'default.yml': [00:00:00 WARN]: [AdvancedServerList] - At Position 15: [00:00:00 WARN]: [AdvancedServerList] "Something" == ${invalid placeholder} [00:00:00 WARN]: [AdvancedServerList] ^ [00:00:00 WARN]: [AdvancedServerList] -> Placeholder '${invalid placeholder}' does not have any available PlaceholderProvider ``` if the location is known.

This is a smaller update that changes how AdvancedServerList reports wrong/invalid conditions when evaluating them. The new error is now one of two possible structures. It's either: ``` [00:00:00 WARN]: [AdvancedServerList] Encountered 1 Error(s) while parsing condition for file 'default.yml': [00:00:00 WARN]: [AdvancedServerList] - "Something" == ${invalid placeholder} [00:00:00 WARN]: [AdvancedServerList] -> Placeholder '${invalid placeholder}' does not have any available PlaceholderProvider ``` when no exact location is known or ``` [00:00:00 WARN]: [AdvancedServerList] Encountered 1 Error(s) while parsing condition for file 'default.yml': [00:00:00 WARN]: [AdvancedServerList] - At Position 15: [00:00:00 WARN]: [AdvancedServerList] "Something" == ${invalid placeholder} [00:00:00 WARN]: [AdvancedServerList] ^ [00:00:00 WARN]: [AdvancedServerList] -> Placeholder '${invalid placeholder}' does not have any available PlaceholderProvider ``` if the location is known.

The BanPlugins addon has been updated to now also support [LibertyBans](https://libertybans.org). This also add support for the Velocity platform in the plugin by supporting LibertyBans. Please report any issues you encounter with this add-on as adding support was a bit complicated for me due to LibertyBans significantly more complex API.

The BanPlugins addon has been updated to now also support [LibertyBans](https://libertybans.org). This also add support for the Velocity platform in the plugin by supporting LibertyBans. Please report any issues you encounter with this add-on as adding support was a bit complicated for me due to LibertyBans significantly more complex API.

The BanPlugins addon has been updated to now also support [LibertyBans](https://libertybans.org). This also add support for the Velocity platform in the plugin by supporting LibertyBans. Please report any issues you encounter with this add-on as adding support was a bit complicated for me due to LibertyBans significantly more complex API.

This update separates the Expression system used by AdvancedServerList into its own project. You can find and use it [here](https://github.com/Andre601/ExpressionParser). Other than that has nothing really changed.

This update separates the Expression system used by AdvancedServerList into its own project. You can find and use it [here](https://github.com/Andre601/ExpressionParser). Other than that has nothing really changed.

This update separates the Expression system used by AdvancedServerList into its own project. You can find and use it [here](https://github.com/Andre601/ExpressionParser). Other than that has nothing really changed.

The FaviconHandler received significant changes to improve the loading of local images, meaning the PNG files located in the plugin's `favicon` folder, while also allowing to adjust the cache time for dynamic images. ## Faster loading of local Favicon images Images located in the `favicons` folder are now loaded at startup of the plugin and whenever you reload it and converted into Favicon files. This allows the plugin to retrieve and use them faster without first having to go through retrieving them, converting them and then applying them (On top of all being done async so often times it's not done before the event continues). They are not included in the cache, since they are static and don't really change unlike the URL and/or player name/UUID option may do. ## Cache time option A new config option named `faviconCacheTime` is now available. It accepts a number from 1 (Which is also the default) to any positive number and sets the time in minutes for the cache to keep a Favicon stored.

The FaviconHandler received significant changes to improve the loading of local images, meaning the PNG files located in the plugin's `favicon` folder, while also allowing to adjust the cache time for dynamic images. ## Faster loading of local Favicon images Images located in the `favicons` folder are now loaded at startup of the plugin and whenever you reload it and converted into Favicon files. This allows the plugin to retrieve and use them faster without first having to go through retrieving them, converting them and then applying them (On top of all being done async so often times it's not done before the event continues). They are not included in the cache, since they are static and don't really change unlike the URL and/or player name/UUID option may do. ## Cache time option A new config option named `faviconCacheTime` is now available. It accepts a number from 1 (Which is also the default) to any positive number and sets the time in minutes for the cache to keep a Favicon stored.

The FaviconHandler received significant changes to improve the loading of local images, meaning the PNG files located in the plugin's `favicon` folder, while also allowing to adjust the cache time for dynamic images. ## Faster loading of local Favicon images Images located in the `favicons` folder are now loaded at startup of the plugin and whenever you reload it and converted into Favicon files. This allows the plugin to retrieve and use them faster without first having to go through retrieving them, converting them and then applying them (On top of all being done async so often times it's not done before the event continues). They are not included in the cache, since they are static and don't really change unlike the URL and/or player name/UUID option may do. ## Cache time option A new config option named `faviconCacheTime` is now available. It accepts a number from 1 (Which is also the default) to any positive number and sets the time in minutes for the cache to keep a Favicon stored.

This is a major release due to a breaking change, which is the removal of the deprecated `conditions` option, meaning that from now on only the `condition` option will be usable. This update also brings an important bug fix just recently (like a few hours ago) found, a brand new addon to use and some improvements on error reporting for expressions. ## Breaking changes The `conditions` option has been removed from server list profile files. This means any profile that still uses it won't work as expected anymore. Please make sure to switch over to the newer and much more powerful `condition` option. ## Bug fix There was an oversight on my end, that caused Placeholders who return numbers to return the wrong value. As an example, assuming a player with protocol version 756 pings the server and you use the expression `${player protocol} < 756`. The result would be `true`. Why? That's because instead of taking the number a placeholder may return, the expression engine used the text-length, meaning that the expression turned into `3 < 756`. This issue has been fixed now and placeholders should always return the right number value now when parsed. Text-based placeholder outputs still will use their text length here. ## New Addon The first official addon for AdvancedServerList has been made. It's called `ASLBanPluginsAddon` and adds placeholders you can use for different ban plugins to get whether a player is banned, what the reason was, how long they stay banned, etc. Right now does it only provide placeholders for AdvancedBan, but I'm open to support more plugins. Feel free to suggest some, or even suggest separate addons to make (Or submit your own to add to the documentation.) ## Expression warning improvements The plugin should now (hopefully) give better warnings for when an expression is invalid for some reason. A possible error output may look like this: ``` [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: Encountered 1 issues while parsing expression '${something jadajada} < 758' [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: - At Position 21: ... < 758 [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: Cause: Placeholder '${something jadajada}' does not have an available PlaceholderProvider. ``` I hope this helps in finding possible issues.

This is a major release due to a breaking change, which is the removal of the deprecated `conditions` option, meaning that from now on only the `condition` option will be usable. This update also brings an important bug fix just recently (like a few hours ago) found, a brand new addon to use and some improvements on error reporting for expressions. ## Breaking changes The `conditions` option has been removed from server list profile files. This means any profile that still uses it won't work as expected anymore. Please make sure to switch over to the newer and much more powerful `condition` option. ## Bug fix There was an oversight on my end, that caused Placeholders who return numbers to return the wrong value. As an example, assuming a player with protocol version 756 pings the server and you use the expression `${player protocol} < 756`. The result would be `true`. Why? That's because instead of taking the number a placeholder may return, the expression engine used the text-length, meaning that the expression turned into `3 < 756`. This issue has been fixed now and placeholders should always return the right number value now when parsed. Text-based placeholder outputs still will use their text length here. ## New Addon The first official addon for AdvancedServerList has been made. It's called `ASLBanPluginsAddon` and adds placeholders you can use for different ban plugins to get whether a player is banned, what the reason was, how long they stay banned, etc. Right now does it only provide placeholders for AdvancedBan, but I'm open to support more plugins. Feel free to suggest some, or even suggest separate addons to make (Or submit your own to add to the documentation.) ## Expression warning improvements The plugin should now (hopefully) give better warnings for when an expression is invalid for some reason. A possible error output may look like this: ``` [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: Encountered 1 issues while parsing expression '${something jadajada} < 758' [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: - At Position 21: ... < 758 [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: Cause: Placeholder '${something jadajada}' does not have an available PlaceholderProvider. ``` I hope this helps in finding possible issues.

This is a major release due to a breaking change, which is the removal of the deprecated `conditions` option, meaning that from now on only the `condition` option will be usable. This update also brings an important bug fix just recently (like a few hours ago) found, a brand new addon to use and some improvements on error reporting for expressions. ## Breaking changes The `conditions` option has been removed from server list profile files. This means any profile that still uses it won't work as expected anymore. Please make sure to switch over to the newer and much more powerful `condition` option. ## Bug fix There was an oversight on my end, that caused Placeholders who return numbers to return the wrong value. As an example, assuming a player with protocol version 756 pings the server and you use the expression `${player protocol} < 756`. The result would be `true`. Why? That's because instead of taking the number a placeholder may return, the expression engine used the text-length, meaning that the expression turned into `3 < 756`. This issue has been fixed now and placeholders should always return the right number value now when parsed. Text-based placeholder outputs still will use their text length here. ## New Addon The first official addon for AdvancedServerList has been made. It's called `ASLBanPluginsAddon` and adds placeholders you can use for different ban plugins to get whether a player is banned, what the reason was, how long they stay banned, etc. Right now does it only provide placeholders for AdvancedBan, but I'm open to support more plugins. Feel free to suggest some, or even suggest separate addons to make (Or submit your own to add to the documentation.) ## Expression warning improvements The plugin should now (hopefully) give better warnings for when an expression is invalid for some reason. A possible error output may look like this: ``` [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: Encountered 1 issues while parsing expression '${something jadajada} < 758' [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: - At Position 21: ... < 758 [23:20:50] [Netty Worker IO Thread #2/WARN] [AdvancedServerList]: Cause: Placeholder '${something jadajada}' does not have an available PlaceholderProvider. ``` I hope this helps in finding possible issues.

This is another breaking change to the expression system. Namely, this one changes the `~=` operand to `=~` while also adding `~` as another way for an equal ignore case check. The reason is to make it more consistent with the `==` and `=` operands and to also have it be more consistent with `!=` and `!~`. This update also tries to publish to Hangar again... So if you see this on Hangar does it mean the upload worked.

This is another breaking change to the expression system. Namely, this one changes the `~=` operand to `=~` while also adding `~` as another way for an equal ignore case check. The reason is to make it more consistent with the `==` and `=` operands and to also have it be more consistent with `!=` and `!~`. This update also tries to publish to Hangar again... So if you see this on Hangar does it mean the upload worked.

This is another breaking change to the expression system. Namely, this one changes the `~=` operand to `=~` while also adding `~` as another way for an equal ignore case check. The reason is to make it more consistent with the `==` and `=` operands and to also have it be more consistent with `!=` and `!~`. This update also tries to publish to Hangar again... So if you see this on Hangar does it mean the upload worked.

This update only affects people who use the "contains" operand in their conditions. Previously was the pattern used `<-` which was taken from TAB. But a possible issue has been brought up, where a condition such as `-2<-1` could be treated as `-2 <- 1` when the goal was to have `-2 < -1` as expression. Because of this did I change the pattern to `<_` to avoid this possible issue. So if you used `<-` in your conditions, switch it over to `<_` to have it working.

This update only affects people who use the "contains" operand in their conditions. Previously was the pattern used `<-` which was taken from TAB. But a possible issue has been brought up, where a condition such as `-2<-1` could be treated as `-2 <- 1` when the goal was to have `-2 < -1` as expression. Because of this did I change the pattern to `<_` to avoid this possible issue. So if you used `<-` in your conditions, switch it over to `<_` to have it working.

This update only affects people who use the "contains" operand in their conditions. Previously was the pattern used `<-` which was taken from TAB. But a possible issue has been brought up, where a condition such as `-2<-1` could be treated as `-2 <- 1` when the goal was to have `-2 < -1` as expression. Because of this did I change the pattern to `<_` to avoid this possible issue. So if you used `<-` in your conditions, switch it over to `<_` to have it working.

This release adds 3 new Operands to use, adobted from the TAB plugin: - `|-` to check if the left value starts with the right value - `-|` to check if the left value ends with the right value - `<-` to check if the left value contains the right value I also consider the plugin stable now, as I haven't been reported any issues with the expression system so far, so 3.7.0 is now here!

This release adds 3 new Operands to use, adobted from the TAB plugin: - `|-` to check if the left value starts with the right value - `-|` to check if the left value ends with the right value - `<-` to check if the left value contains the right value I also consider the plugin stable now, as I haven't been reported any issues with the expression system so far, so 3.7.0 is now here!

This release adds 3 new Operands to use, adobted from the TAB plugin: - `|-` to check if the left value starts with the right value - `-|` to check if the left value ends with the right value - `<-` to check if the left value contains the right value I also consider the plugin stable now, as I haven't been reported any issues with the expression system so far, so 3.7.0 is now here!

This update removes OkHttp as the library used for performing requests to the Modrinth API for update checks and instead uses the HTTPClient available since Java 11. The reason for this change is an exception caused by the kotlin library - which OkHttp uses - not being relocated in ASL, causing conflicts with other plugins that may use libraries also utilizing the kotlin library.

This update removes OkHttp as the library used for performing requests to the Modrinth API for update checks and instead uses the HTTPClient available since Java 11. The reason for this change is an exception caused by the kotlin library - which OkHttp uses - not being relocated in ASL, causing conflicts with other plugins that may use libraries also utilizing the kotlin library.

This update removes OkHttp as the library used for performing requests to the Modrinth API for update checks and instead uses the HTTPClient available since Java 11. The reason for this change is an exception caused by the kotlin library - which OkHttp uses - not being relocated in ASL, causing conflicts with other plugins that may use libraries also utilizing the kotlin library.

This is a bug fix release that only affects the Velocity version of the plugin. I accidentally left in a relocation for Configurate - config library used - for the Velocity version, causing a NoClassDefFoundError to appear on enable. This should be fixed now. If you still get such errors, make sure to use the latest Velocity jar file, as the one you use might be outdated and not have the necessary classes.

This is a bug fix release that only affects the Velocity version of the plugin. I accidentally left in a relocation for Configurate - config library used - for the Velocity version, causing a NoClassDefFoundError to appear on enable. This should be fixed now. If you still get such errors, make sure to use the latest Velocity jar file, as the one you use might be outdated and not have the necessary classes.

This is a bug fix release that only affects the Velocity version of the plugin. I accidentally left in a relocation for Configurate - config library used - for the Velocity version, causing a NoClassDefFoundError to appear on enable. This should be fixed now. If you still get such errors, make sure to use the latest Velocity jar file, as the one you use might be outdated and not have the necessary classes.

## This is a Beta release. Make backups of your plugin configuration for safety. This update brings significant changes to how AdvancedServerList is handling conditions. The old conditions system, while functional, had one main flaw, which was that all listed conditions are ANDed, meaning only if all are true will the profile be displayed. This is rather limiting in terms of making complex conditions and requires you to make duplicate profiles, if you want to display the same content for multiple possible conditions. With this update, the old conditions options is being deprecated in favour of a new option called condition. Unlike the old option is this one using a single string. Said string can contain multiple conditions and special operands such as `and` or `or` to make more complex expressions. The system was taken from BungeeTabListPlus, which uses it to parse their own complex conditions. Be aware that while I did some basic tests, including some with placeholders, can I not guarantee that this is working flawlessly (Hence this being a beta). This is why I want you to report any issues you encounter with this system in my [Discord Server](https://discord.gg/6dazXp6), so that I can try to fix it. The documentation has been updated with the new condition option, including [all available operands](https://asl.andre601.ch/profiles/#condition-operands).

## This is a Beta release. Make backups of your plugin configuration for safety. This update brings significant changes to how AdvancedServerList is handling conditions. The old conditions system, while functional, had one main flaw, which was that all listed conditions are ANDed, meaning only if all are true will the profile be displayed. This is rather limiting in terms of making complex conditions and requires you to make duplicate profiles, if you want to display the same content for multiple possible conditions. With this update, the old conditions options is being deprecated in favour of a new option called condition. Unlike the old option is this one using a single string. Said string can contain multiple conditions and special operands such as `and` or `or` to make more complex expressions. The system was taken from BungeeTabListPlus, which uses it to parse their own complex conditions. Be aware that while I did some basic tests, including some with placeholders, can I not guarantee that this is working flawlessly (Hence this being a beta). This is why I want you to report any issues you encounter with this system in my [Discord Server](https://discord.gg/6dazXp6), so that I can try to fix it. The documentation has been updated with the new condition option, including [all available operands](https://asl.andre601.ch/profiles/#condition-operands).

## This is a Beta release. Make backups of your plugin configuration for safety. This update brings significant changes to how AdvancedServerList is handling conditions. The old conditions system, while functional, had one main flaw, which was that all listed conditions are ANDed, meaning only if all are true will the profile be displayed. This is rather limiting in terms of making complex conditions and requires you to make duplicate profiles, if you want to display the same content for multiple possible conditions. With this update, the old conditions options is being deprecated in favour of a new option called condition. Unlike the old option is this one using a single string. Said string can contain multiple conditions and special operands such as `and` or `or` to make more complex expressions. The system was taken from BungeeTabListPlus, which uses it to parse their own complex conditions. Be aware that while I did some basic tests, including some with placeholders, can I not guarantee that this is working flawlessly (Hence this being a beta). This is why I want you to report any issues you encounter with this system in my [Discord Server](https://discord.gg/6dazXp6), so that I can try to fix it. The documentation has been updated with the new condition option, including [all available operands](https://asl.andre601.ch/profiles/#condition-operands).

This is a small update that adds a debug option to the config.yml of AdvancedServerList. The plugin should automatically migrate your old config to the new version. A backup will be made for safety. Also, comments will be removed through the migration.

This is a small update that adds a debug option to the config.yml of AdvancedServerList. The plugin should automatically migrate your old config to the new version. A backup will be made for safety. Also, comments will be removed through the migration.

This is a small update that adds a debug option to the config.yml of AdvancedServerList. The plugin should automatically migrate your old config to the new version. A backup will be made for safety. Also, comments will be removed through the migration.

Long time no update ey? This update brings an important change to the project. Namely, the Spigot platform will no longer be supported by AdvancedServerList. There are many reasons, but the main one is, that I don't like having to rely on a 3rd-party plugin for features that other servers provide out of the box. It stops my plugin from working on newer versions on Spigot because I have to wait for the dependency to update, which may also bring breaking changes, making it possibly incompatible with former server versions. The plugin will now print a huge warning and disable itself should it not detect specific classes present in Paper, so make sure your server is paper-compatible. ## Other changes There also were some other changes. One is in fact a breaking one and related to the `${server ...}` placeholders. Previously, the `${server playersOnline}` would allow a space-separated list of server or world names to count the players in and display. Issue is that I messed it up and didn't really split the string up at the spaces (Or rather I limited it to two parts: `playersOnline` and whatever followed it afterwards). Also, using spaces feels weird... So I now changed it to split at commas. This means that instead of `${server playersOnline lobby1 lobby2}` the new syntax would be `${server playersOnline lobby1,lobby2}`

Long time no update ey? This update brings an important change to the project. Namely, the Spigot platform will no longer be supported by AdvancedServerList. There are many reasons, but the main one is, that I don't like having to rely on a 3rd-party plugin for features that other servers provide out of the box. It stops my plugin from working on newer versions on Spigot because I have to wait for the dependency to update, which may also bring breaking changes, making it possibly incompatible with former server versions. The plugin will now print a huge warning and disable itself should it not detect specific classes present in Paper, so make sure your server is paper-compatible. ## Other changes There also were some other changes. One is in fact a breaking one and related to the `${server ...}` placeholders. Previously, the `${server playersOnline}` would allow a space-separated list of server or world names to count the players in and display. Issue is that I messed it up and didn't really split the string up at the spaces (Or rather I limited it to two parts: `playersOnline` and whatever followed it afterwards). Also, using spaces feels weird... So I now changed it to split at commas. This means that instead of `${server playersOnline lobby1 lobby2}` the new syntax would be `${server playersOnline lobby1,lobby2}`

Long time no update ey? This update brings an important change to the project. Namely, the Spigot platform will no longer be supported by AdvancedServerList. There are many reasons, but the main one is, that I don't like having to rely on a 3rd-party plugin for features that other servers provide out of the box. It stops my plugin from working on newer versions on Spigot because I have to wait for the dependency to update, which may also bring breaking changes, making it possibly incompatible with former server versions. The plugin will now print a huge warning and disable itself should it not detect specific classes present in Paper, so make sure your server is paper-compatible. ## Other changes There also were some other changes. One is in fact a breaking one and related to the `${server ...}` placeholders. Previously, the `${server playersOnline}` would allow a space-separated list of server or world names to count the players in and display. Issue is that I messed it up and didn't really split the string up at the spaces (Or rather I limited it to two parts: `playersOnline` and whatever followed it afterwards). Also, using spaces feels weird... So I now changed it to split at commas. This means that instead of `${server playersOnline lobby1 lobby2}` the new syntax would be `${server playersOnline lobby1,lobby2}`

This update brings some signifcant changes to the placeholders provided by AdvancedServerList to use in PlaceholderAPI. If you use `%asl_extra_players_max%` read this changelog carefully as it has important news for you. ## New placeholders `%asl_playercount_maxplayers%` and `%asl_server_maxplayers%` 2 new placeholders have been added, each providing their own kind of functionality. - `%asl_playercount_maxplayers%` will return the value of `playerCount -> maxPlayers -> amount`. This value can return `null`, so keep this in mind. - `%asl_server_playersmax%` will return the effective output of `${server playersMax}`. This placeholder is meant as a replacement for `%asl_extra_players_max%`'s old behaviour (Read below for details) ## Changes, deprecation and future replacement of `%asl_extra_players_max%` This placeholder is planned to be removed in the next release, but for now still exists for you to use. There is however a new placeholder that will take its place, which is `%asl_playercount_extraplayers%`. The change was made to keep it consistent with the profile structure itself. Another important thing to note is, that this placeholder (And its deprecated counterpart) will no longer return `<online players> + <extraPlayers amount>` but instead just the value of `playerCount -> extraPlayers -> amount`. This value can return `null` so keep that in mind. To keep using the old behaviour, use `%asl_server_playersmax%` instead.

This update brings some signifcant changes to the placeholders provided by AdvancedServerList to use in PlaceholderAPI. If you use `%asl_extra_players_max%` read this changelog carefully as it has important news for you. ## New placeholders `%asl_playercount_maxplayers%` and `%asl_server_maxplayers%` 2 new placeholders have been added, each providing their own kind of functionality. - `%asl_playercount_maxplayers%` will return the value of `playerCount -> maxPlayers -> amount`. This value can return `null`, so keep this in mind. - `%asl_server_playersmax%` will return the effective output of `${server playersMax}`. This placeholder is meant as a replacement for `%asl_extra_players_max%`'s old behaviour (Read below for details) ## Changes, deprecation and future replacement of `%asl_extra_players_max%` This placeholder is planned to be removed in the next release, but for now still exists for you to use. There is however a new placeholder that will take its place, which is `%asl_playercount_extraplayers%`. The change was made to keep it consistent with the profile structure itself. Another important thing to note is, that this placeholder (And its deprecated counterpart) will no longer return `<online players> + <extraPlayers amount>` but instead just the value of `playerCount -> extraPlayers -> amount`. This value can return `null` so keep that in mind. To keep using the old behaviour, use `%asl_server_playersmax%` instead.

This update brings some signifcant changes to the placeholders provided by AdvancedServerList to use in PlaceholderAPI. If you use `%asl_extra_players_max%` read this changelog carefully as it has important news for you. ## New placeholders `%asl_playercount_maxplayers%` and `%asl_server_maxplayers%` 2 new placeholders have been added, each providing their own kind of functionality. - `%asl_playercount_maxplayers%` will return the value of `playerCount -> maxPlayers -> amount`. This value can return `null`, so keep this in mind. - `%asl_server_playersmax%` will return the effective output of `${server playersMax}`. This placeholder is meant as a replacement for `%asl_extra_players_max%`'s old behaviour (Read below for details) ## Changes, deprecation and future replacement of `%asl_extra_players_max%` This placeholder is planned to be removed in the next release, but for now still exists for you to use. There is however a new placeholder that will take its place, which is `%asl_playercount_extraplayers%`. The change was made to keep it consistent with the profile structure itself. Another important thing to note is, that this placeholder (And its deprecated counterpart) will no longer return `<online players> + <extraPlayers amount>` but instead just the value of `playerCount -> extraPlayers -> amount`. This value can return `null` so keep that in mind. To keep using the old behaviour, use `%asl_server_playersmax%` instead.

This update adds a new feature to the server list profile. This also includes changes to the API. ## Note about 1.20.2 I am aware that 1.20.2 is available now. And I'm confident that my plugin works on BungeeCord and Velocity, and also will work on Paper once they publish first updates. However, Spigot is not supported yet, which is due to the plugin's dependance on ProtocolLib which has yet not received any update for 1.20.2 from what I know. ## New `maxPlayers` option The server list profile now supports a new section called `maxPlayers`. It is part of the `playerCount` section and behaves similarly to the `extraPlayers` section. The difference here is, that the number you provide is used as the max player count to display while extraPlayers adds it to the online players and uses that for the max player count. Note that extraPlayers takes priority over this new option, so if you want to use maxPlayers, you have to disable or remove extraPlayers. Example configuration: ```yaml priority: 0 # We use just colour to hide the MOTD motd: - '<grey>' - '<grey>' playerCount: maxPlayers: enabled: true amount: -1 ``` Result:  ## API updated The API has been updated to `v3.1.0`. It includes support for the above mentioned maxPlayers feature but also a deprecation. Please read [the v3.1.0 changelog](https://asl.andre601.ch/api/changelog/#v310) for details.

This update adds a new feature to the server list profile. This also includes changes to the API. ## Note about 1.20.2 I am aware that 1.20.2 is available now. And I'm confident that my plugin works on BungeeCord and Velocity, and also will work on Paper once they publish first updates. However, Spigot is not supported yet, which is due to the plugin's dependance on ProtocolLib which has yet not received any update for 1.20.2 from what I know. ## New `maxPlayers` option The server list profile now supports a new section called `maxPlayers`. It is part of the `playerCount` section and behaves similarly to the `extraPlayers` section. The difference here is, that the number you provide is used as the max player count to display while extraPlayers adds it to the online players and uses that for the max player count. Note that extraPlayers takes priority over this new option, so if you want to use maxPlayers, you have to disable or remove extraPlayers. Example configuration: ```yaml priority: 0 # We use just colour to hide the MOTD motd: - '<grey>' - '<grey>' playerCount: maxPlayers: enabled: true amount: -1 ``` Result:  ## API updated The API has been updated to `v3.1.0`. It includes support for the above mentioned maxPlayers feature but also a deprecation. Please read [the v3.1.0 changelog](https://asl.andre601.ch/api/changelog/#v310) for details.

This update adds a new feature to the server list profile. This also includes changes to the API. ## Note about 1.20.2 I am aware that 1.20.2 is available now. And I'm confident that my plugin works on BungeeCord and Velocity, and also will work on Paper once they publish first updates. However, Spigot is not supported yet, which is due to the plugin's dependance on ProtocolLib which has yet not received any update for 1.20.2 from what I know. ## New `maxPlayers` option The server list profile now supports a new section called `maxPlayers`. It is part of the `playerCount` section and behaves similarly to the `extraPlayers` section. The difference here is, that the number you provide is used as the max player count to display while extraPlayers adds it to the online players and uses that for the max player count. Note that extraPlayers takes priority over this new option, so if you want to use maxPlayers, you have to disable or remove extraPlayers. Example configuration: ```yaml priority: 0 # We use just colour to hide the MOTD motd: - '<grey>' - '<grey>' playerCount: maxPlayers: enabled: true amount: -1 ``` Result:  ## API updated The API has been updated to `v3.1.0`. It includes support for the above mentioned maxPlayers feature but also a deprecation. Please read [the v3.1.0 changelog](https://asl.andre601.ch/api/changelog/#v310) for details.

This update, despite being only a Minor one, brings some significant changes to AdvancedServerList... Tho not necessarely as a plugin only. ## AdvancedServerList moved to Codeberg.org From this version onwards will AdvancedServerList be hosted on [Codeberg.org](https://codeberg.org/Andre601/AdvancedServerList) instead of GitHub. There are various reasons, but the main one is, that I just like Codeberg more, even if GitHub with their GitHub Actions is quite nice. What this means now is, that the GitHub Repository is semi-archived... It will still be open and I'll still manage issues there, but you won't receive active Updates there anymore and I hightly recommend to check Codeberg instead. Releases will (obviously) still be available on [Modrinth](https://modrinth.com/plugin/advancedserverlist) and [Hangar](https://hangar.papermc.io/Andre_601/AdvancedServerList), just don't expect any releases on GitHub anymore. ## Wiki has moved too For the third time (First time was github wiki to github pages wiki and second time changing from `andre601.ch/AdvancedServerList` to `docs.andre601.ch/AdvancedServerList`) has the Wiki of AdvancedServerList moved. You can now find it under <https://asl.andre601.ch>. Pages on the former Wiki location (`docs.andre601.ch/AdvancedServerList`) will have a banner at the top informing you about the move while also linking to the new place. Tho, keep in mind that the pages may not be up-to-date here... ## Changelog ### Maintenance Plugin support Added support for KennyTV's Maintenance plugin. If said plugin is loaded on the server will AdvancedServerList hook into its API to check if maintenance mode is enabled. If it is will it not manage the server list to avoid possible conflicts. As of right now is there no logic in place to check on the proxy, whether maintenance mode only affects a specific server or not, so keep that in mind.

This update, despite being only a Minor one, brings some significant changes to AdvancedServerList... Tho not necessarely as a plugin only. ## AdvancedServerList moved to Codeberg.org From this version onwards will AdvancedServerList be hosted on [Codeberg.org](https://codeberg.org/Andre601/AdvancedServerList) instead of GitHub. There are various reasons, but the main one is, that I just like Codeberg more, even if GitHub with their GitHub Actions is quite nice. What this means now is, that the GitHub Repository is semi-archived... It will still be open and I'll still manage issues there, but you won't receive active Updates there anymore and I hightly recommend to check Codeberg instead. Releases will (obviously) still be available on [Modrinth](https://modrinth.com/plugin/advancedserverlist) and [Hangar](https://hangar.papermc.io/Andre_601/AdvancedServerList), just don't expect any releases on GitHub anymore. ## Wiki has moved too For the third time (First time was github wiki to github pages wiki and second time changing from `andre601.ch/AdvancedServerList` to `docs.andre601.ch/AdvancedServerList`) has the Wiki of AdvancedServerList moved. You can now find it under <https://asl.andre601.ch>. Pages on the former Wiki location (`docs.andre601.ch/AdvancedServerList`) will have a banner at the top informing you about the move while also linking to the new place. Tho, keep in mind that the pages may not be up-to-date here... ## Changelog ### Maintenance Plugin support Added support for KennyTV's Maintenance plugin. If said plugin is loaded on the server will AdvancedServerList hook into its API to check if maintenance mode is enabled. If it is will it not manage the server list to avoid possible conflicts. As of right now is there no logic in place to check on the proxy, whether maintenance mode only affects a specific server or not, so keep that in mind.

This update, despite being only a Minor one, brings some significant changes to AdvancedServerList... Tho not necessarely as a plugin only. ## AdvancedServerList moved to Codeberg.org From this version onwards will AdvancedServerList be hosted on [Codeberg.org](https://codeberg.org/Andre601/AdvancedServerList) instead of GitHub. There are various reasons, but the main one is, that I just like Codeberg more, even if GitHub with their GitHub Actions is quite nice. What this means now is, that the GitHub Repository is semi-archived... It will still be open and I'll still manage issues there, but you won't receive active Updates there anymore and I hightly recommend to check Codeberg instead. Releases will (obviously) still be available on [Modrinth](https://modrinth.com/plugin/advancedserverlist) and [Hangar](https://hangar.papermc.io/Andre_601/AdvancedServerList), just don't expect any releases on GitHub anymore. ## Wiki has moved too For the third time (First time was github wiki to github pages wiki and second time changing from `andre601.ch/AdvancedServerList` to `docs.andre601.ch/AdvancedServerList`) has the Wiki of AdvancedServerList moved. You can now find it under <https://asl.andre601.ch>. Pages on the former Wiki location (`docs.andre601.ch/AdvancedServerList`) will have a banner at the top informing you about the move while also linking to the new place. Tho, keep in mind that the pages may not be up-to-date here... ## Changelog ### Maintenance Plugin support Added support for KennyTV's Maintenance plugin. If said plugin is loaded on the server will AdvancedServerList hook into its API to check if maintenance mode is enabled. If it is will it not manage the server list to avoid possible conflicts. As of right now is there no logic in place to check on the proxy, whether maintenance mode only affects a specific server or not, so keep that in mind.

This update includes the changes of the [Previous Beta Version](https://github.com/Andre601/AdvancedServerList/releases/tag/v3.3.0-b1), so make sure to read it. ## Changes to reload command The `/asl reload` command will no longer clear the Player and Favicon caches when used. If you still want to clear the caches, use `/asl clearcache` instead.

This update includes the changes of the [Previous Beta Version](https://github.com/Andre601/AdvancedServerList/releases/tag/v3.3.0-b1), so make sure to read it. ## Changes to reload command The `/asl reload` command will no longer clear the Player and Favicon caches when used. If you still want to clear the caches, use `/asl clearcache` instead.

This update includes the changes of the [Previous Beta Version](https://github.com/Andre601/AdvancedServerList/releases/tag/v3.3.0-b1), so make sure to read it. ## Changes to reload command The `/asl reload` command will no longer clear the Player and Favicon caches when used. If you still want to clear the caches, use `/asl clearcache` instead.

## ⚠️ WARNING: This is a BETA Due to a lack of a proper server network was I unable to test out this plugin version. I'm confident that it will work, but I do not give any guarantees. **Make sure to create backups of your server!** ### PAPIProxyBridge support This update implements support for the plugin PAPIProxyBridge which allows the usage of PlaceholderAPI placeholders on your BungeeCord or Velocity proxy. Do note that AdvancedServerList requires **at least** version 1.3 of PAPIProxyBridge to work due to new methods being implemented by that plugin. ### Favicon improvements The FaviconHandler - the class responsible for the favicon creation and management - has received some changes. The creation of the Favicon has been wrapped into a CompletableFuture, allowing asynchronous creation. Tho, this also means that if the CompletableFuture is not done yet when the plugin requests the favicon will `null` be returned, which is treated as no favicon being applied. This hopefully helps with Waterfall reporting the plugin being slow whenever a favicon is being used...

## ⚠️ WARNING: This is a BETA Due to a lack of a proper server network was I unable to test out this plugin version. I'm confident that it will work, but I do not give any guarantees. **Make sure to create backups of your server!** ### PAPIProxyBridge support This update implements support for the plugin PAPIProxyBridge which allows the usage of PlaceholderAPI placeholders on your BungeeCord or Velocity proxy. Do note that AdvancedServerList requires **at least** version 1.3 of PAPIProxyBridge to work due to new methods being implemented by that plugin. ### Favicon improvements The FaviconHandler - the class responsible for the favicon creation and management - has received some changes. The creation of the Favicon has been wrapped into a CompletableFuture, allowing asynchronous creation. Tho, this also means that if the CompletableFuture is not done yet when the plugin requests the favicon will `null` be returned, which is treated as no favicon being applied. This hopefully helps with Waterfall reporting the plugin being slow whenever a favicon is being used...

## ⚠️ WARNING: This is a BETA Due to a lack of a proper server network was I unable to test out this plugin version. I'm confident that it will work, but I do not give any guarantees. **Make sure to create backups of your server!** ### PAPIProxyBridge support This update implements support for the plugin PAPIProxyBridge which allows the usage of PlaceholderAPI placeholders on your BungeeCord or Velocity proxy. Do note that AdvancedServerList requires **at least** version 1.3 of PAPIProxyBridge to work due to new methods being implemented by that plugin. ### Favicon improvements The FaviconHandler - the class responsible for the favicon creation and management - has received some changes. The creation of the Favicon has been wrapped into a CompletableFuture, allowing asynchronous creation. Tho, this also means that if the CompletableFuture is not done yet when the plugin requests the favicon will `null` be returned, which is treated as no favicon being applied. This hopefully helps with Waterfall reporting the plugin being slow whenever a favicon is being used...

There is a rare chance that `gson.fromJson(Reader, Type)` will return `null` in the PlayerHandler loading process, which causes an NPE to happen. This should be fixed now and AdvancedServerList will print a warning about the JSON not being parsable, which seems to be the only explanation for this to occur.

There is a rare chance that `gson.fromJson(Reader, Type)` will return `null` in the PlayerHandler loading process, which causes an NPE to happen. This should be fixed now and AdvancedServerList will print a warning about the JSON not being parsable, which seems to be the only explanation for this to occur.

There is a rare chance that `gson.fromJson(Reader, Type)` will return `null` in the PlayerHandler loading process, which causes an NPE to happen. This should be fixed now and AdvancedServerList will print a warning about the JSON not being parsable, which seems to be the only explanation for this to occur.

This update brings a few minor improvements to the plugin. ## New `whitelistEnabled` placeholder The Spigot/Paper version now has a new `${server whitelistEnabled}` placeholder. When used will it return true or false based on if the whitelist is enabled. ## Multiple worlds/servers for `playersOnline` The `playersOnline` placeholder now allows to set multiple worlds/servers separated by spaces. When multiple are provided will the placeholder combine each player count and return the total. ## Config backups The plugin will now make a backup of your old config whenever it makes a config migration. This should help restore an old config in case something breaks. Should the backup fail will the entire config migration be cancelled. Backups are stored in a dedicated `backups` folder in the plugin's own directory and will have the format `config_<ISO date>.yml`

This update brings a few minor improvements to the plugin. ## New `whitelistEnabled` placeholder The Spigot/Paper version now has a new `${server whitelistEnabled}` placeholder. When used will it return true or false based on if the whitelist is enabled. ## Multiple worlds/servers for `playersOnline` The `playersOnline` placeholder now allows to set multiple worlds/servers separated by spaces. When multiple are provided will the placeholder combine each player count and return the total. ## Config backups The plugin will now make a backup of your old config whenever it makes a config migration. This should help restore an old config in case something breaks. Should the backup fail will the entire config migration be cancelled. Backups are stored in a dedicated `backups` folder in the plugin's own directory and will have the format `config_<ISO date>.yml`

This update brings a few minor improvements to the plugin. ## New `whitelistEnabled` placeholder The Spigot/Paper version now has a new `${server whitelistEnabled}` placeholder. When used will it return true or false based on if the whitelist is enabled. ## Multiple worlds/servers for `playersOnline` The `playersOnline` placeholder now allows to set multiple worlds/servers separated by spaces. When multiple are provided will the placeholder combine each player count and return the total. ## Config backups The plugin will now make a backup of your old config whenever it makes a config migration. This should help restore an old config in case something breaks. Should the backup fail will the entire config migration be cancelled. Backups are stored in a dedicated `backups` folder in the plugin's own directory and will have the format `config_<ISO date>.yml`

# For Paper users Paper introduced changes to the `paper-plugin.yml` file in regards to the Dependencies declaration in more recent 1.19.4+ patches. What this means is, that this version of AdvancedServerList is **only** compatible with the **latest** releases of Paper for 1.19.4 and newer! Trying to use it on any versions before these patches will result in an exception. I cannot guarantee that the plugin works on any forks such as Purpur or Pufferfish, so make sure to check if they include these patches before using this version of AdvancedServerList. ## Server placeholder changes The Server placeholder now allows you to add an additional argument in the form of a world or server name (Depending on the platform you use it on). This allows you to display the online players in a world or server, or the host used for a specific server. Please refer to [the wiki](https://www.andre601.ch/AdvancedServerList/profiles/placeholders/#server) for more details. ## Config Migrator The main config.yml has received changes, mainly in terms of its formatting. This means the old config isn't compatible anymore. Thankfully does the library used by AdvancedServerList offer a migration tool. This means that it will automatically migrate the config to the new format while preserving existing settings. However, a backup is still recommended. Also, the migration will remove any existing comments within the config.yml There is now a `configVersion` setting. **Do not edit this option!** It determines whether the config needs an update or not. ## New operators `~=` and `!~` have been added as operands for the conditions. - `~=` checks if the left value is equal to the right value, while being case-insensitive. - `!~` checks if the left value is not equal to the right value, while being case-insensitive. ## Updated ASL API The ASL API has been updated to v3.0.0 Full changelog can be found [here](https://www.andre601.ch/AdvancedServerList/api/changelog/#v300)

# For Paper users Paper introduced changes to the `paper-plugin.yml` file in regards to the Dependencies declaration in more recent 1.19.4+ patches. What this means is, that this version of AdvancedServerList is **only** compatible with the **latest** releases of Paper for 1.19.4 and newer! Trying to use it on any versions before these patches will result in an exception. I cannot guarantee that the plugin works on any forks such as Purpur or Pufferfish, so make sure to check if they include these patches before using this version of AdvancedServerList. ## Server placeholder changes The Server placeholder now allows you to add an additional argument in the form of a world or server name (Depending on the platform you use it on). This allows you to display the online players in a world or server, or the host used for a specific server. Please refer to [the wiki](https://www.andre601.ch/AdvancedServerList/profiles/placeholders/#server) for more details. ## Config Migrator The main config.yml has received changes, mainly in terms of its formatting. This means the old config isn't compatible anymore. Thankfully does the library used by AdvancedServerList offer a migration tool. This means that it will automatically migrate the config to the new format while preserving existing settings. However, a backup is still recommended. Also, the migration will remove any existing comments within the config.yml There is now a `configVersion` setting. **Do not edit this option!** It determines whether the config needs an update or not. ## New operators `~=` and `!~` have been added as operands for the conditions. - `~=` checks if the left value is equal to the right value, while being case-insensitive. - `!~` checks if the left value is not equal to the right value, while being case-insensitive. ## Updated ASL API The ASL API has been updated to v3.0.0 Full changelog can be found [here](https://www.andre601.ch/AdvancedServerList/api/changelog/#v300)

# For Paper users Paper introduced changes to the `paper-plugin.yml` file in regards to the Dependencies declaration in more recent 1.19.4+ patches. What this means is, that this version of AdvancedServerList is **only** compatible with the **latest** releases of Paper for 1.19.4 and newer! Trying to use it on any versions before these patches will result in an exception. I cannot guarantee that the plugin works on any forks such as Purpur or Pufferfish, so make sure to check if they include these patches before using this version of AdvancedServerList. ## Server placeholder changes The Server placeholder now allows you to add an additional argument in the form of a world or server name (Depending on the platform you use it on). This allows you to display the online players in a world or server, or the host used for a specific server. Please refer to [the wiki](https://www.andre601.ch/AdvancedServerList/profiles/placeholders/#server) for more details. ## Config Migrator The main config.yml has received changes, mainly in terms of its formatting. This means the old config isn't compatible anymore. Thankfully does the library used by AdvancedServerList offer a migration tool. This means that it will automatically migrate the config to the new format while preserving existing settings. However, a backup is still recommended. Also, the migration will remove any existing comments within the config.yml There is now a `configVersion` setting. **Do not edit this option!** It determines whether the config needs an update or not. ## New operators `~=` and `!~` have been added as operands for the conditions. - `~=` checks if the left value is equal to the right value, while being case-insensitive. - `!~` checks if the left value is not equal to the right value, while being case-insensitive. ## Updated ASL API The ASL API has been updated to v3.0.0 Full changelog can be found [here](https://www.andre601.ch/AdvancedServerList/api/changelog/#v300)

This update fixes a small issue on Spigot servers where a `NoClassDefFoundException` is thrown whenever the MOTD gets parsed. This was because I used a convenience method from ProtocolLib that converts a Adventure component to a WrappedChatComponent. This method only works on servers natively implementing adventure (i.e. Paper). The reason why it worked on older versions is unknown to me. My biggest guess is, that I accidentally included the adventure library in my plugin, which ProtocolLib would hook into. Either way, this should be fixed now. Thanks to SlimeDog for reporting.

This update fixes a small issue on Spigot servers where a `NoClassDefFoundException` is thrown whenever the MOTD gets parsed. This was because I used a convenience method from ProtocolLib that converts a Adventure component to a WrappedChatComponent. This method only works on servers natively implementing adventure (i.e. Paper). The reason why it worked on older versions is unknown to me. My biggest guess is, that I accidentally included the adventure library in my plugin, which ProtocolLib would hook into. Either way, this should be fixed now. Thanks to SlimeDog for reporting.

This update fixes a small issue on Spigot servers where a `NoClassDefFoundException` is thrown whenever the MOTD gets parsed. This was because I used a convenience method from ProtocolLib that converts a Adventure component to a WrappedChatComponent. This method only works on servers natively implementing adventure (i.e. Paper). The reason why it worked on older versions is unknown to me. My biggest guess is, that I accidentally included the adventure library in my plugin, which ProtocolLib would hook into. Either way, this should be fixed now. Thanks to SlimeDog for reporting.

This is a small update making some improvements to the code, while also fixing a few minor things. ## Improvements - Created a `BukkitCore<F>` class to extend the `JavaPlugin` class and implement the `PluginCore<F>` interface respectively. This allowed me to simply provide the class instance for cases where either a JavaPlugin or a PluginCore instance was needed. - Made `AdvancedServerList` have a Type parameter (So it became `AdvancedServerList<F>` This was made to get rid of `PluginCore<?>` usage, which I wasn't a big fan of. - Unregister PlaceholderAPI expansion when plugin is disabling itself. This should allow support for using `/reload` (Although I do not recommend using that). ## Fixes - PlaceholderAPI expansion not being set as Persistent. It should now no longer be unregistered when using `/papi reload` - JoinEvent class not being registered as a Event listener

This is a small update making some improvements to the code, while also fixing a few minor things. ## Improvements - Created a `BukkitCore<F>` class to extend the `JavaPlugin` class and implement the `PluginCore<F>` interface respectively. This allowed me to simply provide the class instance for cases where either a JavaPlugin or a PluginCore instance was needed. - Made `AdvancedServerList` have a Type parameter (So it became `AdvancedServerList<F>` This was made to get rid of `PluginCore<?>` usage, which I wasn't a big fan of. - Unregister PlaceholderAPI expansion when plugin is disabling itself. This should allow support for using `/reload` (Although I do not recommend using that). ## Fixes - PlaceholderAPI expansion not being set as Persistent. It should now no longer be unregistered when using `/papi reload` - JoinEvent class not being registered as a Event listener

This is a small update making some improvements to the code, while also fixing a few minor things. ## Improvements - Created a `BukkitCore<F>` class to extend the `JavaPlugin` class and implement the `PluginCore<F>` interface respectively. This allowed me to simply provide the class instance for cases where either a JavaPlugin or a PluginCore instance was needed. - Made `AdvancedServerList` have a Type parameter (So it became `AdvancedServerList<F>` This was made to get rid of `PluginCore<?>` usage, which I wasn't a big fan of. - Unregister PlaceholderAPI expansion when plugin is disabling itself. This should allow support for using `/reload` (Although I do not recommend using that). ## Fixes - PlaceholderAPI expansion not being set as Persistent. It should now no longer be unregistered when using `/papi reload` - JoinEvent class not being registered as a Event listener

This release is the first proper 3.0.0 release of AdvancedServerList. If you didn't follow the previous releases is here a short summary: - Support for PaperMC's new `Paper-plugin` system has been implemented. The two jars (Spigot and Paper) have been merged into one now. As of writing this has the Paper module - after being kept for a while - been removed. - Fixes have been made towards Spigot compatability (More precisely with protocollib). Other changes have recently been made too. In detail, a "HangarUploader" module was made, which houses the code of a Jar file made to upload the jar files to the Hangar Website automatically. Big thanks to all the @hangarmc team members that helped me in getting this to work. If you're reading this on Hangar, does it mean the application worked! Additionally have dependencies been improved. The Bukkit jar is no longer almost 8MB but instead around 1.15MB. The other jars - to my knowledge - received little to no size reduction. ### Funfact (Actually sad fact) This is the 7th time I make the release

This release is the first proper 3.0.0 release of AdvancedServerList. If you didn't follow the previous releases is here a short summary: - Support for PaperMC's new `Paper-plugin` system has been implemented. The two jars (Spigot and Paper) have been merged into one now. As of writing this has the Paper module - after being kept for a while - been removed. - Fixes have been made towards Spigot compatability (More precisely with protocollib). Other changes have recently been made too. In detail, a "HangarUploader" module was made, which houses the code of a Jar file made to upload the jar files to the Hangar Website automatically. Big thanks to all the @hangarmc team members that helped me in getting this to work. If you're reading this on Hangar, does it mean the application worked! Additionally have dependencies been improved. The Bukkit jar is no longer almost 8MB but instead around 1.15MB. The other jars - to my knowledge - received little to no size reduction. ### Funfact (Actually sad fact) This is the 7th time I make the release

This release is the first proper 3.0.0 release of AdvancedServerList. If you didn't follow the previous releases is here a short summary: - Support for PaperMC's new `Paper-plugin` system has been implemented. The two jars (Spigot and Paper) have been merged into one now. As of writing this has the Paper module - after being kept for a while - been removed. - Fixes have been made towards Spigot compatability (More precisely with protocollib). Other changes have recently been made too. In detail, a "HangarUploader" module was made, which houses the code of a Jar file made to upload the jar files to the Hangar Website automatically. Big thanks to all the @hangarmc team members that helped me in getting this to work. If you're reading this on Hangar, does it mean the application worked! Additionally have dependencies been improved. The Bukkit jar is no longer almost 8MB but instead around 1.15MB. The other jars - to my knowledge - received little to no size reduction. ### Funfact (Actually sad fact) This is the 7th time I make the release

This update fixes #67 on Spigot 1.19.4 The issue was, that The Server List Ping stuff of MC is now a record, which is unmodifiable, meaning that I simply can't get the ping, alter it and then ignore. So this change writes the changed ping back into ProtocolLib to properly update the Server List entry. It also updates some dependencies including the ASL API, which is now 2.1.0. Please read the API Changelog [here](https://github.com/Andre601/asl-api/releases/tag/v2.1.0). Note that I still publish this as beta as I still want to be sure to have all bugs removed before making a full update later on.

This update fixes #67 on Spigot 1.19.4 The issue was, that The Server List Ping stuff of MC is now a record, which is unmodifiable, meaning that I simply can't get the ping, alter it and then ignore. So this change writes the changed ping back into ProtocolLib to properly update the Server List entry. It also updates some dependencies including the ASL API, which is now 2.1.0. Please read the API Changelog [here](https://github.com/Andre601/asl-api/releases/tag/v2.1.0). Note that I still publish this as beta as I still want to be sure to have all bugs removed before making a full update later on.

This update fixes #67 on Spigot 1.19.4 The issue was, that The Server List Ping stuff of MC is now a record, which is unmodifiable, meaning that I simply can't get the ping, alter it and then ignore. So this change writes the changed ping back into ProtocolLib to properly update the Server List entry. It also updates some dependencies including the ASL API, which is now 2.1.0. Please read the API Changelog [here](https://github.com/Andre601/asl-api/releases/tag/v2.1.0). Note that I still publish this as beta as I still want to be sure to have all bugs removed before making a full update later on.

## FOR SPIGOT AND PAPER USERS This update is a **BETA**, so expect possible bugs and issues and **Make backups of your server and plugin configurations!** While I did test the plugin on 1.19.4 and it working will I not guarantee that it won't break, so be careful with it and always [report issues to me on GitHub!](https://github.com/Andre601/AdvancedServerList/issues) ---- ## What changed? This update adds support for PaperMC's all new Paper plugin system. This system allows a plugin to define a separate YAML file for different configurations to be loaded and used, making a merged jar a lot easier. Because of this is AdvancedServerList no longer shipping a separate Paper and Spigot jar but instead a Bukkit jar that works on both platforms. Please note that the Paper plugin feature only exists since the latest 1.19.3 and 1.19.4 releases and is still considered experimental. On older versions will AdvancedServerList load like a Spigot plugin (including the Paper notice banner). This won't be removed nor fixed. As a final note will I keep the `paper` module until the next non-patch release, so if you want to build the old paper plugin can you clone this repository and execute `mvn --projects :core,:paper clean install` in the root-directory to build the core and paper module. Please let me know about any issues you encountered!

## FOR SPIGOT AND PAPER USERS This update is a **BETA**, so expect possible bugs and issues and **Make backups of your server and plugin configurations!** While I did test the plugin on 1.19.4 and it working will I not guarantee that it won't break, so be careful with it and always [report issues to me on GitHub!](https://github.com/Andre601/AdvancedServerList/issues) ---- ## What changed? This update adds support for PaperMC's all new Paper plugin system. This system allows a plugin to define a separate YAML file for different configurations to be loaded and used, making a merged jar a lot easier. Because of this is AdvancedServerList no longer shipping a separate Paper and Spigot jar but instead a Bukkit jar that works on both platforms. Please note that the Paper plugin feature only exists since the latest 1.19.3 and 1.19.4 releases and is still considered experimental. On older versions will AdvancedServerList load like a Spigot plugin (including the Paper notice banner). This won't be removed nor fixed. As a final note will I keep the `paper` module until the next non-patch release, so if you want to build the old paper plugin can you clone this repository and execute `mvn --projects :core,:paper clean install` in the root-directory to build the core and paper module. Please let me know about any issues you encountered!

## FOR SPIGOT AND PAPER USERS This update is a **BETA**, so expect possible bugs and issues and **Make backups of your server and plugin configurations!** While I did test the plugin on 1.19.4 and it working will I not guarantee that it won't break, so be careful with it and always [report issues to me on GitHub!](https://github.com/Andre601/AdvancedServerList/issues) ---- ## What changed? This update adds support for PaperMC's all new Paper plugin system. This system allows a plugin to define a separate YAML file for different configurations to be loaded and used, making a merged jar a lot easier. Because of this is AdvancedServerList no longer shipping a separate Paper and Spigot jar but instead a Bukkit jar that works on both platforms. Please note that the Paper plugin feature only exists since the latest 1.19.3 and 1.19.4 releases and is still considered experimental. On older versions will AdvancedServerList load like a Spigot plugin (including the Paper notice banner). This won't be removed nor fixed. As a final note will I keep the `paper` module until the next non-patch release, so if you want to build the old paper plugin can you clone this repository and execute `mvn --projects :core,:paper clean install` in the root-directory to build the core and paper module. Please let me know about any issues you encountered!

This update adds a new set of Placeholders you can use in PlaceholderAPI. Obviously can they only be used on the Spigot and Paper version, so keep that in mind. A full list can be found here: https://www.andre601.ch/AdvancedServerList/placeholderapi/

This update adds a new set of Placeholders you can use in PlaceholderAPI. Obviously can they only be used on the Spigot and Paper version, so keep that in mind. A full list can be found here: https://www.andre601.ch/AdvancedServerList/placeholderapi/

This update adds a new set of Placeholders you can use in PlaceholderAPI. Obviously can they only be used on the Spigot and Paper version, so keep that in mind. A full list can be found here: https://www.andre601.ch/AdvancedServerList/placeholderapi/

This update adds a new set of Placeholders you can use in PlaceholderAPI. Obviously can they only be used on the Spigot and Paper version, so keep that in mind. A full list can be found here: https://www.andre601.ch/AdvancedServerList/placeholderapi/

# Please note Despite this being a minor version bump does it contain breaking changes due to the API being updated from v1 to v2 which has its own set of breaking changes (See [this Release](https://github.com/Andre601/asl-api/releases/tag/v2.0.0) for details) Also, while the plugin has been tested using the [`asl-mockup` plugin](https://github.com/Andre601/asl-mockup) could there be bugs and compatability issues. Please report them when you encounter any. ## Removed API module The `api` module has been removed. Instead is the separate [`asl-api`](https://github.com/Andre601/asl-api) repository used for the actual API stuff, meaning that the plugin will now use the same API as you would when hooking into it. ## Added PreServerListSetEvent This event is fired whenever AdvancedServerList is about to alter the server list for a player. It allows you to modify the used ProfileEntry or even cancel the event to not have the server list changed. ## Fixed `=` condition not working when surrounded by spaces If you had a `=` (equals) condition and the `=` was surrounded by spaces would this break the check, as an expression like `value1 = value1` would check `"value1 "` with `" value1"` which obviously aren't equal. The plugin now removes any leading and trailing spaces from the left and right side of the expression before evaluating the condition.

# Please note Despite this being a minor version bump does it contain breaking changes due to the API being updated from v1 to v2 which has its own set of breaking changes (See [this Release](https://github.com/Andre601/asl-api/releases/tag/v2.0.0) for details) Also, while the plugin has been tested using the [`asl-mockup` plugin](https://github.com/Andre601/asl-mockup) could there be bugs and compatability issues. Please report them when you encounter any. ## Removed API module The `api` module has been removed. Instead is the separate [`asl-api`](https://github.com/Andre601/asl-api) repository used for the actual API stuff, meaning that the plugin will now use the same API as you would when hooking into it. ## Added PreServerListSetEvent This event is fired whenever AdvancedServerList is about to alter the server list for a player. It allows you to modify the used ProfileEntry or even cancel the event to not have the server list changed. ## Fixed `=` condition not working when surrounded by spaces If you had a `=` (equals) condition and the `=` was surrounded by spaces would this break the check, as an expression like `value1 = value1` would check `"value1 "` with `" value1"` which obviously aren't equal. The plugin now removes any leading and trailing spaces from the left and right side of the expression before evaluating the condition.

# Please note Despite this being a minor version bump does it contain breaking changes due to the API being updated from v1 to v2 which has its own set of breaking changes (See [this Release](https://github.com/Andre601/asl-api/releases/tag/v2.0.0) for details) Also, while the plugin has been tested using the [`asl-mockup` plugin](https://github.com/Andre601/asl-mockup) could there be bugs and compatability issues. Please report them when you encounter any. ## Removed API module The `api` module has been removed. Instead is the separate [`asl-api`](https://github.com/Andre601/asl-api) repository used for the actual API stuff, meaning that the plugin will now use the same API as you would when hooking into it. ## Added PreServerListSetEvent This event is fired whenever AdvancedServerList is about to alter the server list for a player. It allows you to modify the used ProfileEntry or even cancel the event to not have the server list changed. ## Fixed `=` condition not working when surrounded by spaces If you had a `=` (equals) condition and the `=` was surrounded by spaces would this break the check, as an expression like `value1 = value1` would check `"value1 "` with `" value1"` which obviously aren't equal. The plugin now removes any leading and trailing spaces from the left and right side of the expression before evaluating the condition.

# Please note Despite this being a minor version bump does it contain breaking changes due to the API being updated from v1 to v2 which has its own set of breaking changes (See [this Release](https://github.com/Andre601/asl-api/releases/tag/v2.0.0) for details) Also, while the plugin has been tested using the [`asl-mockup` plugin](https://github.com/Andre601/asl-mockup) could there be bugs and compatability issues. Please report them when you encounter any. ## Removed API module The `api` module has been removed. Instead is the separate [`asl-api`](https://github.com/Andre601/asl-api) repository used for the actual API stuff, meaning that the plugin will now use the same API as you would when hooking into it. ## Added PreServerListSetEvent This event is fired whenever AdvancedServerList is about to alter the server list for a player. It allows you to modify the used ProfileEntry or even cancel the event to not have the server list changed. ## Fixed `=` condition not working when surrounded by spaces If you had a `=` (equals) condition and the `=` was surrounded by spaces would this break the check, as an expression like `value1 = value1` would check `"value1 "` with `" value1"` which obviously aren't equal. The plugin now removes any leading and trailing spaces from the left and right side of the expression before evaluating the condition.

This is a HUGE update as it brings a lot of changes to AdvancedServerList, including a brand new API to hook into! ## New API A completely new API has been created to allow plugins to provide their own placeholders to parse in AdvancedServerList. How you can hook and use this API is explained on the new Wiki here: https://www.andre601.ch/AdvancedServerList/api/ AdvancedServerList is using this API internally for the player and server placeholders you can already use. A [mockup paper plugin](https://github.com/Andre601/asl-mockup) is also available for you to see how it could look like. I've tested it and it works:    ## New Wiki As mentioned is there also a new wiki you can visit. The old one - while working fine - simply wasn't nice in terms of look or available features. With the new wiki I can customize it more. The link is - again - https://www.andre601.ch/AdvancedServerList/ The source of this wiki is also in this repository, located under the `docs/` directory. PRs always welcome if they improve things. --- I really hope this update brings new functionality to AdvancedServerList. I've put a lot of effort into it. I started this over a month ago and am really happy now to publish it. My next goals are to expand the API further... If you have any ideas, let me know. I'm always open for feedback!

This is a HUGE update as it brings a lot of changes to AdvancedServerList, including a brand new API to hook into! ## New API A completely new API has been created to allow plugins to provide their own placeholders to parse in AdvancedServerList. How you can hook and use this API is explained on the new Wiki here: https://www.andre601.ch/AdvancedServerList/api/ AdvancedServerList is using this API internally for the player and server placeholders you can already use. A [mockup paper plugin](https://github.com/Andre601/asl-mockup) is also available for you to see how it could look like. I've tested it and it works:    ## New Wiki As mentioned is there also a new wiki you can visit. The old one - while working fine - simply wasn't nice in terms of look or available features. With the new wiki I can customize it more. The link is - again - https://www.andre601.ch/AdvancedServerList/ The source of this wiki is also in this repository, located under the `docs/` directory. PRs always welcome if they improve things. --- I really hope this update brings new functionality to AdvancedServerList. I've put a lot of effort into it. I started this over a month ago and am really happy now to publish it. My next goals are to expand the API further... If you have any ideas, let me know. I'm always open for feedback!

This is a HUGE update as it brings a lot of changes to AdvancedServerList, including a brand new API to hook into! ## New API A completely new API has been created to allow plugins to provide their own placeholders to parse in AdvancedServerList. How you can hook and use this API is explained on the new Wiki here: https://www.andre601.ch/AdvancedServerList/api/ AdvancedServerList is using this API internally for the player and server placeholders you can already use. A [mockup paper plugin](https://github.com/Andre601/asl-mockup) is also available for you to see how it could look like. I've tested it and it works:    ## New Wiki As mentioned is there also a new wiki you can visit. The old one - while working fine - simply wasn't nice in terms of look or available features. With the new wiki I can customize it more. The link is - again - https://www.andre601.ch/AdvancedServerList/ The source of this wiki is also in this repository, located under the `docs/` directory. PRs always welcome if they improve things. --- I really hope this update brings new functionality to AdvancedServerList. I've put a lot of effort into it. I started this over a month ago and am really happy now to publish it. My next goals are to expand the API further... If you have any ideas, let me know. I'm always open for feedback!

This is a HUGE update as it brings a lot of changes to AdvancedServerList, including a brand new API to hook into! ## New API A completely new API has been created to allow plugins to provide their own placeholders to parse in AdvancedServerList. How you can hook and use this API is explained on the new Wiki here: https://www.andre601.ch/AdvancedServerList/api/ AdvancedServerList is using this API internally for the player and server placeholders you can already use. A [mockup paper plugin](https://github.com/Andre601/asl-mockup) is also available for you to see how it could look like. I've tested it and it works:    ## New Wiki As mentioned is there also a new wiki you can visit. The old one - while working fine - simply wasn't nice in terms of look or available features. With the new wiki I can customize it more. The link is - again - https://www.andre601.ch/AdvancedServerList/ The source of this wiki is also in this repository, located under the `docs/` directory. PRs always welcome if they improve things. --- I really hope this update brings new functionality to AdvancedServerList. I've put a lot of effort into it. I started this over a month ago and am really happy now to publish it. My next goals are to expand the API further... If you have any ideas, let me know. I'm always open for feedback!

This update improves the way players are cached. It brings somewhat breaking changes. ### New Player caching AdvancedServerList now stores cached players as a JSON Array of JSON objects in a `playercache.json` file. When a player joins your server/network will it now collect and save the following information when disabling: - IP for identification - Player name - Player UUID A quick example using myself (actual file would be minified by Gson): ```json [ { "ip": "127.0.0.1", "name": "Andre_601", "uuid": "286f8d0c-b571-4720-b7ab-f2929cb38120" } ] ``` ### Placeholder changes With the above changes are there also changes to the available placeholders. Namely, `${player uuid}` can now be used across all platforms and not just Spigot/Paper like in the previous versions. In addition was a new option called `unknown_player_uuid` added to the config.yml. This String option would have the UUID used for `${player uuid}` should the pinging player be unknown (not cached) by AdvancedServerList yet. It defaults to `606e2ff0-ed77-4842-9d6c-e1d3321c7838` which is the UUID of MHF_Question. ### OfflinePlayer handling in Spigot and Paper With the Cache changes were also changes made to how AdvancedServerList obtains OfflinePlayer instances. It now uses UUID instead of player names to obtain an OfflinePlayer instance. Please let me know if this has any unwanted side-effects for you. ### What comes next? The next major plan is to release v2 of AdvancedServerList, which brings an API for providing your own Placeholder values! You can check out #38 for further info and progress (Spoiler: It's pretty much done by now).

This update improves the way players are cached. It brings somewhat breaking changes. ### New Player caching AdvancedServerList now stores cached players as a JSON Array of JSON objects in a `playercache.json` file. When a player joins your server/network will it now collect and save the following information when disabling: - IP for identification - Player name - Player UUID A quick example using myself (actual file would be minified by Gson): ```json [ { "ip": "127.0.0.1", "name": "Andre_601", "uuid": "286f8d0c-b571-4720-b7ab-f2929cb38120" } ] ``` ### Placeholder changes With the above changes are there also changes to the available placeholders. Namely, `${player uuid}` can now be used across all platforms and not just Spigot/Paper like in the previous versions. In addition was a new option called `unknown_player_uuid` added to the config.yml. This String option would have the UUID used for `${player uuid}` should the pinging player be unknown (not cached) by AdvancedServerList yet. It defaults to `606e2ff0-ed77-4842-9d6c-e1d3321c7838` which is the UUID of MHF_Question. ### OfflinePlayer handling in Spigot and Paper With the Cache changes were also changes made to how AdvancedServerList obtains OfflinePlayer instances. It now uses UUID instead of player names to obtain an OfflinePlayer instance. Please let me know if this has any unwanted side-effects for you. ### What comes next? The next major plan is to release v2 of AdvancedServerList, which brings an API for providing your own Placeholder values! You can check out #38 for further info and progress (Spoiler: It's pretty much done by now).

This update improves the way players are cached. It brings somewhat breaking changes. ### New Player caching AdvancedServerList now stores cached players as a JSON Array of JSON objects in a `playercache.json` file. When a player joins your server/network will it now collect and save the following information when disabling: - IP for identification - Player name - Player UUID A quick example using myself (actual file would be minified by Gson): ```json [ { "ip": "127.0.0.1", "name": "Andre_601", "uuid": "286f8d0c-b571-4720-b7ab-f2929cb38120" } ] ``` ### Placeholder changes With the above changes are there also changes to the available placeholders. Namely, `${player uuid}` can now be used across all platforms and not just Spigot/Paper like in the previous versions. In addition was a new option called `unknown_player_uuid` added to the config.yml. This String option would have the UUID used for `${player uuid}` should the pinging player be unknown (not cached) by AdvancedServerList yet. It defaults to `606e2ff0-ed77-4842-9d6c-e1d3321c7838` which is the UUID of MHF_Question. ### OfflinePlayer handling in Spigot and Paper With the Cache changes were also changes made to how AdvancedServerList obtains OfflinePlayer instances. It now uses UUID instead of player names to obtain an OfflinePlayer instance. Please let me know if this has any unwanted side-effects for you. ### What comes next? The next major plan is to release v2 of AdvancedServerList, which brings an API for providing your own Placeholder values! You can check out #38 for further info and progress (Spoiler: It's pretty much done by now).

This update improves the way players are cached. It brings somewhat breaking changes. ### New Player caching AdvancedServerList now stores cached players as a JSON Array of JSON objects in a `playercache.json` file. When a player joins your server/network will it now collect and save the following information when disabling: - IP for identification - Player name - Player UUID A quick example using myself (actual file would be minified by Gson): ```json [ { "ip": "127.0.0.1", "name": "Andre_601", "uuid": "286f8d0c-b571-4720-b7ab-f2929cb38120" } ] ``` ### Placeholder changes With the above changes are there also changes to the available placeholders. Namely, `${player uuid}` can now be used across all platforms and not just Spigot/Paper like in the previous versions. In addition was a new option called `unknown_player_uuid` added to the config.yml. This String option would have the UUID used for `${player uuid}` should the pinging player be unknown (not cached) by AdvancedServerList yet. It defaults to `606e2ff0-ed77-4842-9d6c-e1d3321c7838` which is the UUID of MHF_Question. ### OfflinePlayer handling in Spigot and Paper With the Cache changes were also changes made to how AdvancedServerList obtains OfflinePlayer instances. It now uses UUID instead of player names to obtain an OfflinePlayer instance. Please let me know if this has any unwanted side-effects for you. ### What comes next? The next major plan is to release v2 of AdvancedServerList, which brings an API for providing your own Placeholder values! You can check out #38 for further info and progress (Spoiler: It's pretty much done by now).

This update should fix some NullPointerExceptions caused by `Boolean` being nullable. It now uses a own class to guarantee a not-null value being returned.

This update should fix some NullPointerExceptions caused by `Boolean` being nullable. It now uses a own class to guarantee a not-null value being returned.

This update should fix some NullPointerExceptions caused by `Boolean` being nullable. It now uses a own class to guarantee a not-null value being returned.

This update should fix some NullPointerExceptions caused by `Boolean` being nullable. It now uses a own class to guarantee a not-null value being returned.

This update adds a better Version check system to replace the other one. The main issue with the old one was/is, that it only expects `n.n.n` patterns, so a version like the previous one (`1.10.0-b1`) would break it. Additionally have I removed some debug lines I left in by accident. Sorry for the console spam. I also consider this a proper release now!

This update adds a better Version check system to replace the other one. The main issue with the old one was/is, that it only expects `n.n.n` patterns, so a version like the previous one (`1.10.0-b1`) would break it. Additionally have I removed some debug lines I left in by accident. Sorry for the console spam. I also consider this a proper release now!