Tags
Creators
Details
2.2.0
Compatibility
Required content
Changes
Bug Fix: We have resolved a security vulnerability where players could exploit the system if the plugin detected 127.0.0.1 or a local IP address.
Previously, a local IP detection could allow the automatic login bypass to trigger incorrectly. This has been fixed: the bypass mechanism is now strictly disabled for 127.0.0.1 and all local loopback addresses to ensure player authentication cannot be spoofed.
Security Warning: If running behind a proxy (Velocity/BungeeCord), you must configure IP forwarding properly. If the plugin detects 127.0.0.1 as the player's IP, automatic login will now fail completely for that player rather than risking a security bypass for all local connections.
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:amuh0XZx:TNnoXQVG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:amuh0XZx:TNnoXQVG"
}

