Tags
Creators
Details
3.4.0
Compatibility
Changes
This update, despite being only a Minor one, brings some significant changes to AdvancedServerList... Tho not necessarely as a plugin only.
AdvancedServerList moved to Codeberg.org
From this version onwards will AdvancedServerList be hosted on Codeberg.org instead of GitHub. There are various reasons, but the main one is, that I just like Codeberg more, even if GitHub with their GitHub Actions is quite nice.
What this means now is, that the GitHub Repository is semi-archived... It will still be open and I'll still manage issues there, but you won't receive active Updates there anymore and I hightly recommend to check Codeberg instead. Releases will (obviously) still be available on Modrinth and Hangar, just don't expect any releases on GitHub anymore.
Wiki has moved too
For the third time (First time was github wiki to github pages wiki and second time changing from andre601.ch/AdvancedServerList to docs.andre601.ch/AdvancedServerList) has the Wiki of AdvancedServerList moved.
You can now find it under https://asl.andre601.ch.
Pages on the former Wiki location (docs.andre601.ch/AdvancedServerList) will have a banner at the top informing you about the move while also linking to the new place.
Tho, keep in mind that the pages may not be up-to-date here...
Changelog
Maintenance Plugin support
Added support for KennyTV's Maintenance plugin. If said plugin is loaded on the server will AdvancedServerList hook into its API to check if maintenance mode is enabled. If it is will it not manage the server list to avoid possible conflicts.
As of right now is there no logic in place to check on the proxy, whether maintenance mode only affects a specific server or not, so keep that in mind.
Optional dependencies
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:awzugoEp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xss83sOY:awzugoEp"
}
