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 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 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 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, 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 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 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:
centerdoes not resize the image, but instead centers it as good as possible in the Favicon.nonedoes 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 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.