Tags
Creators
Details
All versions
1.6
Release
CraftersLogin 1.66 months ago 18
Uploaded by
Compatibility
Minecraft: Java Edition
1.21โ1.21.5
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platforms
BungeeCord
Paper
Spigot
Velocity
Waterfall
Changes
CraftersLogin v1.6 โ Critical Premium Auto-Login System - Fully Functional
๐ง Fixed
- Premium auto-login was not working correctly when switching servers or reconnecting because the premium status was not being validated early enough in the connection process
- Already registered premium players were incorrectly rejected because the system was not recognizing their existing registration during the UUID validation process
- The auto-login system was generating false positives because it was not properly distinguishing between new and existing registered players during UUID mismatch checks
- Database error when updating accounts because SQL queries were still referencing columns that had been removed when the ban system was deleted
- The premium player cache was throwing internal errors because the implementation was using a view of the key set that became invalid when the underlying map was modified
- Premium players were not being correctly forced into online mode because the authentication listener was not running at the right priority level in the event chain
- Internal message communication between the proxy and backend servers was failing because the listener was expecting messages from the wrong source type
- A player's premium status was not being saved to the correct database table because the enable and disable methods were using different tables inconsistently
- The console was generating excessive spam because informational messages were being logged at the wrong level
- Expired premium accounts or players who used
/premiumbefore their subscription ended were not being handled because there was no way to disable premium mode once enabled
โ Added
- Early premium validation system at the moment the player attempts to connect, before entering the server
- In-memory cache manager for premium players, improving verification performance
- Database support on the proxy side for storing premium player data (H2 and MySQL)
- Configurable message for when a premium player fails automatic authentication
- Using
/premiumnow kicks the player so they can reconnect and apply auto-login correctly - Changing another player's password as an admin now automatically kicks that player for security
๐ Changed
- H2 is now the default database, MySQL is now optional
- All system messages were moved to configuration files, none are hardcoded anymore
/cl banand/cl unbansubcommands were completely removed- The spawn command was restructured with new subcommands:
setspawnregister,setspawnloginandsetspawn - The ban system was fully removed from the database for better compatibility and a lighter JAR size
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:1ttKrKwS:hGpPHzQS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1ttKrKwS:hGpPHzQS"
}

