Links
Tags
Creators
Details
2.2.2-Stable
Compatibility
Changes
Updated to the latest version of Minecraft, fixing some known issues.
v2.2.2-Stable (2025-02-11)
🎨 New Features
✨ Added ItemsAdder compatibility support Supports using custom items in configuration files (format: namespace:item_id) Automatically detects the ItemsAdder plugin and enables custom item functionality Fully backward compatible with vanilla item configurations
✨ Added automatic login support for legitimate players Listens to FastLogin/AuthMe automatic login events Delay check mechanism (2 seconds) to avoid timing issues Event priority optimization (MONITOR) to ensure other plugins process first
🔧 Optimizations and Improvements
⚡ Optimized configuration file reloading logic Automatically clears the old configuration cache during reloading Fixed the issue of item types not updating Added detailed configuration loading logs
⚡ Improved item loading system Changed storage from Material to ItemStack, supporting custom items Added default value rollback mechanism Enhanced error handling and log output
🛡️ Enhanced MMOProfiles Compatibility
Prevent unverified players from opening the GUI of other plugins
Automatically reopen the login screen
Prevent the GUI from being overwritten by other plugins
🐛 Bug Fixes
🐛 Fixed a password generation logic error in PasswordGen
🐛 Fixed incorrect naming in Handler singleton pattern
🐛 Fixed a Mojang API resource leak issue
🐛 Fixed an issue where item types did not update after configuration reload
🐛 Fixed an issue where a password window still popped up after automatic login for legitimate players
📝 Code Quality
🧹 Cleaned up all commented-out code
🔄 Optimized object caching (SecureRandom, Gson)
📊 Improved ConfigUtil message caching mechanism
🎯 Optimized string checking using the Stream API
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:uhk4EMXY:UIOSBTkR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uhk4EMXY:UIOSBTkR"
}

