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 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.
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:
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:altandminecraft: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.