1.0.0
Compatibility
Changes
🛡️ RisersSecurity v1.0.0 - Initial Release
Welcome to the first public release of RisersSecurity!
A lightweight, dependency-free authentication plugin designed to keep your Minecraft server and player accounts secure.
✨ Added
- 🔐 Secure player registration and login system
- 🔒 BCrypt password hashing for secure password storage
- 📁 YAML-based player data storage (
playerdata.yml) - ⚡ Zero external dependencies (No MySQL, SQLite, or JDBC)
- 🌍 Spawn protection for unauthenticated players
- 👁️ Blindness effect before authentication
- 📍 Automatic player location restoration after successful login
- ⏱️ Configurable login and registration timeouts
- 🔢 Configurable maximum failed login attempts
- 🔑 Password change command for players
- 👮 Admin password reset command
- 🔄 Plugin reload command
- 🎨 Fully customizable messages, prefixes, and colors
- ⚙️ Configurable security settings via
config.yml - 🛡️ Session timeout support
⚙️ Configuration
- Customizable login and register messages
- Editable plugin prefix
- Configurable password length requirements
- Configurable login attempt limits
- Spawn protection settings
- Session timeout options
- Message color customization
👮 Admin Features
- Reset player passwords
- Reload configuration without restarting the server
- Permission-based administration (
riserssecurity.admin)
🚀 Performance
- Lightweight implementation
- Dependency-free architecture
- Optimized for Paper & Spigot servers
- Fast YAML-based data management
📦 Requirements
- Paper / Spigot 1.21+
- Java 21
🎉 First Release
This is the initial public release of RisersSecurity.
Future updates will include additional security improvements, quality-of-life features, and expanded configuration options.
Thank you for choosing RisersSecurity to protect your server! 🔐
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:VKoauAUb:FPGl5x6t"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VKoauAUb:FPGl5x6t"
}

