Creators
Details
2.3.0
Compatibility
Changes
๐ LifeHeartsPro v2.3.0 Update
๐ ๏ธ Bugfix & System Update
This update focuses on improving stability, fixing critical issues, and introducing a cleaner and more reliable messaging system.
๐ฅ New Features
๐ Improved Language System
Fully reworked LocaleManager
Automatic language file creation
Safe fallback to English (en_EN)
Added missing message detection in console
Cleaner and more consistent translations
๐ฌ Global Prefix System
All chat messages now automatically include a prefix
No more missing prefixes or inconsistent messages
Smart system prevents duplicate prefixes
Actionbar messages remain clean (no prefix)
๐ง New Message API (Developer Improvement)
Introduced locale.send(...) system
Simplifies sending messages with placeholders
Reduces errors and improves maintainability
๐ Bug Fixes
Fixed "Missing message" errors caused by invalid or missing keys
Fixed issues with outdated language files not updating properly
Fixed potential crash in placeholder replacement system
Fixed inconsistent team command messages
Improved error handling for missing language entries
โ๏ธ Improvements
Cleaner and more structured codebase
Improved command feedback system
Better debug logging in console
Safer reload behavior
Improved tab completion logic
๐งฉ Team System Improvements
Fully integrated with new language system
All team messages now support placeholders
Improved feedback for invalid actions
More consistent user experience
๐ Important Note
โ ๏ธ After updating to v2.3.0:
Please delete your old language files:
plugins/LifeHeartsPro/lang/
They will be automatically regenerated.
๐ฏ Summary
This update brings:
Better stability
Cleaner messages
Easier development
Improved user experience
๐ Thank you for using LifeHeartsPro!
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:NA8cl1Vd:xlOuKXes"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NA8cl1Vd:xlOuKXes"
}

