Tags
Creators
Details
2.7
Compatibility
Changes
ProtocolLib is not required in this version of the plugin. The experimental premium login feature has been deprecated for security reasons.
Summary: This update focuses on hardening server security and administrative control. We have removed the experimental Premium Auto-Login features to ensure maximum stability and zero data loss, while introducing powerful brute-force protection and external integrations.
🔒 Brute-Force Protection (Account Locking)
Automatic Locking: If a player is kicked 3 times (default) for entering the wrong password, their account is permanently LOCKED. Behavior: Locked players can join but cannot move, chat, or execute commands. They will see a "Blocked" screen. Resolution: Admins must use /pureauth unlock <player> to restore access.
🤖 Captcha System
New players must enter a random 5-character alphanumeric code during registration to prevent bot attacks. Configurable in config.yml.
🔔 Discord Webhook Integration (BETA)
The plugin can now send alerts to a Discord channel for: Failed login attempts (Kicks). Account Lockouts. Administrative actions (Unregister, Force Login, Password Changes).
🛡️ Safe Mode
Added a safe_mode switch in the config. When enabled, sensitive admin commands (like changing passwords or unregistering players) are blocked in-game and can only be executed from the Server Console.
🌍 Localization
Full support for English (EN) and Polish (PL). Switch languages instantly in the config.
🛠️ Admin Tools
New: /pureauth unlock <player> - Unblocks a locked account. New: /pureauth register <player> <password> - Manually register a player. Improved: /pureauth stats - Displays detailed configuration status.
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:a0H5ojum:IeFz1bQ6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a0H5ojum:IeFz1bQ6"
}

