Tags
Creators
Details
All versions
1.0.3-velocity
Release
mAuth Velocity 1.0.32 weeks ago 16
Compatibility
Minecraft: Java Edition
26.3
Platform
Velocity
Changes
Changelog
1.0.3 - 2026-10-10
- Added Minecraft 26.3 compatibility across the Paper, Velocity, Discord, and Telegram modules and verified the complete build and tests.
This project follows Semantic Versioning.
1.0.2 - 2026-09-20
- Removed unauthenticated connection handling from the Velocity addon
- Added a startup guard that requires Mojang authentication on standalone servers or the proxy addon
- Replaced the legacy account-mode command with
/passwordlogin - Removed obsolete account-mode settings from the Velocity configuration
1.0.1 - 2026-08-27
- Fixed an async teleport race that could leave session-authenticated players in limbo
- Fixed incomplete Brigadier commands returning generic syntax errors instead of localized usage
- Added separate login and registration deadlines with an optional localized bossbar countdown
- Added configurable duplicate-session and shared-IP session protection
- Kept English as the clean-install default and preserved explicit language choices during config migration
- Updated security-sensitive runtime dependencies
1.0.0 - 2026-08-13
- Added asynchronous Argon2id authentication with legacy hash migration
- Added H2, SQLite, MySQL, MariaDB, and PostgreSQL storage
- Added TOTP, recovery codes, email recovery, sessions, account locks, and audit history
- Added premium, Floodgate, and Velocity authentication flows
- Added Discord and Telegram addons, local GeoIP, VPN providers, and a local web panel
- Added Paper Brigadier commands, Folia schedulers, and the standalone mAuth API artifact
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:xk0cx4UM:hdZWfLRf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xk0cx4UM:hdZWfLRf"
}

