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 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 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, so that I can try to fix it.
The documentation has been updated with the new condition option, including all available 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.