Tags
Creators
Details
2.0.0
Compatibility
Changes
๐ก๏ธ AstraLogin BIG UPDATE - v2.0.0 -
--------------------------------------------------------------------------
โ ๏ธ UNSTABLE VERSION โ ๏ธ
DO NOT DOWNLOAD THIS VERSION. This version (2.0.0) is Unstable, contains serious security bugs and is unstable.
Please download the latest release for the best experience, new features
--------------------------------------------------------------------------
New Features & Improvements:
โ Support - Added support for Java 17, from now on the plugin will work from version 1.18+
โ Session System โ From now on, you don't have to log in every time you have a power outage. You can just come back and keep playing! You can configure it your way in the config!
โ Orderly file structure โ From now on, the file with players' passwords and IP is not loosely located in the plugin folder but in the "playerdata" folder!
โ New blocks for those not logged in โ First of all, the lock for opening the inventory, eating, moving items, and not detecting the player as a target for mobs was added
โ Protecting players console passwords โ Now passwords are not loaded in the console when the player logs in. Logs are blocked using the "Log4j" logger. Currently, this cannot be disabled for password security reasons, but in the next versions of the plugin it will be possible to mask the password or completely remove the log.
โ New extended config โ Now the config has been extended with many more options such as disabling login time, limiting incorrect password attempts, multi-accounts, etc. Check it out for yourself!
โ Protection against multi-accounts โ Added protection against multi-accounts by checking the player's IP. If a player tries to join from the same IP that is already registered in the database but with a different nickname, he will be rejected.
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:sO4dBl28:iIMKJqks"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sO4dBl28:iIMKJqks"
}

