Tags
Creators
Details
1.1.3
Compatibility
Changes
0745b2f feat: Add conflict mode, timestamp, and original nickname columns to player database operations. (rafalohaki)
09916dd feat: introduce ListenerFactory for listener instantiation and integrate IPRateLimiter cleanup into AuthCache (rafalohaki)
e4e5573 refactor: Encapsulate internal database components by reducing visibility and simplify virtual thread executor management. (rafalohaki)
f2fed46 feat: make premium resolver more resilient by accepting both 204 and 404 for not-found responses and prioritizing explicit offline results over unknown resolver states. (rafalohaki)
4f14efa feat: Enhance brute force protection by tracking failed login attempts per username (rafalohaki)
d2d4ece Add unit and integration tests for database and authentication components (rafalohaki)
964bc85 feat: add command in progress message and improve premium detection logic (rafalohaki)
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:awl91tjn:rVxpvJd6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:awl91tjn:rVxpvJd6"
}

