Tags
Creators
Details
v1.0.3
Compatibility
Changes
📦 v1.0.3 - The "Clean & Secure" Update
The biggest update yet! We have rebuilt the plugin's core to be lighter, removing unnecessary dependencies and improving global compatibility from 1.8.8 to 1.20.1+.
🚀 New Features
- 💎 Smart Premium System: Added the
/premiumcommand with a confirmation system. Users can toggle their original Mojang status for automatic login (Auto-login). - 🔐 Secure Password Change: New
/changepasswordcommand using BCrypt encryption to update passwords securely. - 🌈 Dynamic Hex Color Support: Smart system that detects your server version. Use Hex colors (
&#RRGGBB) on 1.16+ while maintaining classic compatibility on 1.8.8. - 📂 100% Editable Messaging: All messages are now organized by categories in
messages_en.ymlfor full customization.
🛠️ Improvements & Optimization
- 📦 Migration to Local H2: Heavy MySQL and Email dependencies have been removed. The plugin is now "Plug & Play", storing everything in an ultra-fast local
data.dbdatabase. - ⚡ Asynchronous Performance: All save and load operations are now asynchronous to ensure your server's TPS stays at 20.0.
- 🛡️ Hardened Security:
- Improved Blindness and movement lock upon joining.
- Password change protection for premium users.
- Status validation to prevent duplicate messages in commands.
🐛 Bug Fixes
- ✅ 1.8.8 Compatibility: Fixed material errors (
SKULL_ITEMvsPLAYER_HEAD) and sound issues that prevented the plugin from loading on older versions. - ✅ Database Fix: Optimized the connection to prevent H2 file corruption during server shutdowns.
- ✅ GUI Fix: The admin panel now correctly displays player heads across all versions.
Made with ❤️ by xPlugins .
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:FEQ1r4Lb:cL7HdKol"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FEQ1r4Lb:cL7HdKol"
}

