AdvancedServerList

You can now add multiple MOTDs to a Server list profile. To not break compatability with the motd option is this new feature available as a separate option called motds that takes priority over motd if both are present.

Note that the syntax is a little bit different for this option. Instead of each entry being a line is each entry the MOTD, meaning you have to use the |- option of YAML like this:

motds:
  - |-
    MOTD 1
    One of the MOTDs
  - MOTD 2
    Another MOTD

This is a smaller release that updates the following dependencies:

• adventure-api from 4.11.0 to 4.12.0
• adventure-text-minimessage from 4.11.0 to 4.12.0
• adventure-text-serializer-legacy from 4.11.0 to 4.12.0
• adventure-platform-bukkit from 4.1.2 to 4.2.0

Note that the plugin does Support 1.19.3 without any changes needed. At most will you need to update ProtocolLib if you're using the Spigot version (Also, the adventure-platform-bukkit update may be required here for chat).

This update changes the event handling for the ping events used on the servers and proxies. Previously did each platform version have its own handling of the event, resulting in a lot of repeated code. This has now been moved to a central class to be handled by, allowing the amount of duplicate code to be reduced significantly.

You shouldn't notice any real difference. If you do, report it on the issue tracker or in my Discord Server.

This versions add an update checker. To use it, you have to add check_updates: true to your config,yml.

When enabled will AdvancedServerList check for a new update at Modrinth every 12 hours. If it finds a new update will it inform you about it. The updates are checked against the plugin's respective platform, meaning that the Spigot version only checks versions for the Spigot platform.

Please report any issues on the issue tracker or in my Discord Server.

This update adds a new option called disable_cache to the config.yml

When set to true (Defaults to false) will the caching of players be disabled. This means the following:

• No player names will be loaded from the cache.data file, if present
• No cache.data file will be created if none is present
• No player data will be saved to the cache.data file when the plugin gets disabled

Placeholders

It's important to note, that any placeholder requiring a cached player will NOT work when this option is used.

In particular, the following placeholders won't work:

• ${player name} (Will display the text set in unknown_player)
• ${player hasPlayedBefore}
• ${player isBanned}
• ${player isWhitelisted}
• ${player uuid}
• Any PlaceholderAPI placeholders