Tags
Creators
Details
All versions
v0.3.0-mc1.21.1-neoforge
Beta
Vouch v0.3.0-mc1.21.1 (NeoForge)3 months ago 590
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Dedicated servers only
Required content
Any compatible version
Changes
Vouch v0.3.0-mc1.21.1 (pre-release)
Highlights:
- feat(auth): mixed-mode premium login with cryptographic verification (closes #2 part 1)
Replaces the broken v0.2.0 premium auto-login. The mod now intercepts the login handshake and selectively forces an encryption challenge for usernames that exist in the Mojang API, so premium accounts go through the same session-server verification as on online-mode servers. Non-premium players keep the normal offline flow.
Default is opt-in:
premium_offline_by_default=truemakes all players offline by default, players run/vouch markAsOnlineto enable premium verification on their next join. Admins can use/vouch admin force-offline <player>andforce-online <player>to override per-player. - fix(build): exclude SLF4J from shadow bundle (closes #2 part 2)
HikariCP pulled in
org.slf4jtransitively and shadow was bundling it. The platform already provides SLF4J at runtime, and the duplicate caused a split-package crash on clean NeoForge installs.
Migration notes:
- The
auth.premium_auto_loginconfig option is unchanged but the underlying flow is different. If you were running it on v0.2.0, expect newauth.premium_offline_by_defaultandauth.premium_auto_login_require_2fakeys in your TOML on first start (defaults are safe). - New permissions:
vouch.admin.premium-override,vouch.command.mark-as-online. - New DB table
vouch_premium_overridesis created automatically on startup.
Full Changelog: https://github.com/valentin-marquez/vouch/compare/v0.2.1-mc1.21.1...v0.3.0-mc1.21.1
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:E4nhP7pz:9CBBjLMf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E4nhP7pz:9CBBjLMf"
}

