Tags
Creators
Details
1.6.0
Compatibility
Changes
VeloAuth 1.6.0
π Security fix. Premium players connecting during the startup window β after Velocity opens
its port but before VeloAuth finishes initializing β were let through with no premium check, and
got an offline UUID on proxies with online-mode = false. The window reopened on every restart
and could be timed deliberately: treat it as a name-sniping vector. Queued logins now go through
the full PreLogin pipeline, and are denied if it isn't ready.
β±οΈ Rate limits for premium lookups. A join wave could multiply into far more upstream requests
than lookups, cross Mojang's limit, and turn its 429s into a proxy-wide login outage. New ceilings
under premium.resolver: mojang-requests-per-minute (120), ashcon- / wpme-requests-per-minute
(60), rate-limit-max-wait-ms (1000). Set to 0 to disable.
Upgrading. Full proxy restart required.
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:PC8Clbt2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:awl91tjn:PC8Clbt2"
}

