Tags
Creators
Details
3.3.0
Compatibility
Changes
๐ AstraLogin v3.3.0 - Account Management & Adventure API Update
This update introduces a brand new account and IP tracking system for server administrators, along with a complete migration to the modern Adventure API for ultimate message customization.
๐ฅ Advanced Account Management & Anti-Alt Tools
- New
/account <player>Command: Added a comprehensive account statistics system. Administrators can now instantly check a player's IP address, registration date, last login date, and unique UUID. This system will be further expanded in upcoming updates! ๐ - New /resetaccount <player> Command: Command: Added a dedicated command for full account data removal. This wipes all stored player data related to AstraLogin, including the hashed password, recorded IP addresses, temporary inventory caches, and saved locations. ๐งนโ
- New
/iplistCommand: A powerful new monitoring tool that scans the database and lists all registered IP addresses along with every player account associated with them. Perfect for quickly detecting, tracking, and monitoring multi-account (alt) creation attempts! ๐๐
๐จ Modern Text Formatting & Adventure API
- Full Adventure API Integration: The plugin has completely transitioned to Paper's modern Adventure API. You can now use advanced text formatting in your language files, including modern MiniMessage tags (e.g.,
<red>,<gradient>,<rainbow>) and full HEX color codes! ๐โจ
๐งน Code Cleanup & Performance
- Code Optimization: Removed old legacy methods, completely cleared internal developer warnings, and optimized database/file queries for even better server performance and lower resource usage. ๐๏ธ๐งผ
Thank you for using AstraLogin! If you encounter any issues or have suggestions, please report them on our Discord or GitHub. ๐ฆพ๐ฅ
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:YSNEdiB9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sO4dBl28:YSNEdiB9"
}

