1.0.0
Compatibility
Changes
✨ Features
Password-based authentication system for player access Unique trust system using player UUID + IP address Automatic login bypass for trusted players on the same IP Re-authentication required when joining from a new or unknown IP Secure chat handling to prevent password exposure
⚙️ Configuration
Simple config setup with customizable password and hint Trusted player data is automatically stored and managed Option to manually remove trusted IP/UUID pairs from the config Useful for forcing re-authentication if needed Requires a server restart after manual edits
🔒 Security
Prevents unauthorized access even if a player’s account is compromised Ensures only verified users can bypass login on recognized connections
🛠️ Notes
Plugin generates required files on first startup Most config values are auto-managed—avoid modifying unknown fields Designed for both convenience (trusted users) and protection (unknown logins)
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:sMHO66dr:LShioqEK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sMHO66dr:LShioqEK"
}

