Tags
Creators
Details
1.0.0
Compatibility
Changes
SecureLogin v1.0.0! This plugin has been created to add an important layer of security when players access their accounts. We want to ensure that server accounts are protected from unauthorized access and attacks.
With this version 1.0.0, our project has reached a level of technical maturity. We offer a secure, optimized login system that is ready for production servers.
Here are some key features and highlights:
Robust Authentication System: We have implemented a secure registration and login flow. This means players will not be able to move, chat, or access their inventory until their identity is successfully verified.
Brute Force Protection: We have added security measures to prevent massive and automated attempts to guess passwords. This protects the integrity of both the server and its users.
Storage Optimization: We have improved the data saving system to log credentials efficiently. This prevents server lag during the login process.
Customizable Configuration and Messages: The configuration files are organized so you can adapt all alerts, timeouts, and texts to match your community's aesthetics.
Security is essential from the very first moment. The login phase is one of the most vulnerable points on any server. SecureLogin takes care of closing that security gap with a lightweight yet effective behavior against compromised sessions.
We invite you to try this version and integrate it into your infrastructure. If you encounter any issues or want to suggest a new feature for the authentication flow, feel free to open an Issue in this repository. Your collaboration is very important to keep improving our tools.
Thank you for choosing Revers Studio development solutions. Keep your server secure!
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:G133KHgy:EboCKgkf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G133KHgy:EboCKgkf"
}

