Tags
Creators
Details
5.6.0
Compatibility
Changes
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.
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| AdvancedServerList-BanPlugins-Addon-5.6.0.jar | Unknown | 22.46 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:xss83sOY:POe7BxHC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xss83sOY:POe7BxHC"
}
