1.0.1
Compatibility
Changes
Changlog 1.0.1
Added
- IP verification for unrecognized login addresses.
- Trusted IP management.
- Discord DM login verification.
- Approve and Reject verification actions.
- Configurable IP verification timeout.
- Configurable Minecraft IP verification kick message.
- Configurable Discord verification messages.
- Configurable PIN system.
- Configurable PIN length.
- Configurable PIN messages.
- AuthMe login integration.
- Discord Guild validation.
- Discord Channel validation.
Security Improvements
Version 1.0.1 significantly expands the security functionality of DiscordAuthMeBridge.
Unrecognized login IP addresses can now require explicit Discord verification before access is granted. Trusted IP addresses are maintained per Minecraft account, while verification requests are temporary and automatically expire.
The existing one-to-one Minecraft ↔ Discord account relationship remains enforced to prevent account duplication or unauthorized reassociation.
Design Goals
DiscordAuthMeBridge focuses on three principles:
Security — Authentication and verification are separated into controlled stages, with temporary credentials and Discord-based confirmation.
Simplicity — The plugin requires only AuthMe, a Discord bot, and a local SQLite database. No external database infrastructure is necessary.
Maintainability — Configuration, verification messages, expiration periods, and security behavior are designed to remain configurable without unnecessary complexity.
Summary
DiscordAuthMeBridge provides a complete Minecraft–Discord identity bridge with an additional layer of login security.
It combines AuthMe authentication, temporary account-linking codes, Discord verification, trusted IP management, PIN verification, and SQLite persistence into a single lightweight plugin.
The result is a controlled authentication workflow where Minecraft accounts can be associated with verified Discord identities and suspicious login attempts can be challenged through Discord before access is granted.
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:j4GLK383:TAqy57DW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j4GLK383:TAqy57DW"
}
