Creators
Details
2.4.0
Compatibility
Changes
π LifeHeartsPro v2.4.0
π₯ Major Update β Ban System & Message Rework
This update introduces a complete elimination system, improved messaging, and a much cleaner plugin structure.
π NEW: Elimination & Ban System
Players are now automatically banned when reaching 0 lives Works with: Death system π /lifeheartspro lives set 0 /lifeheartspro lives remove Custom ban message (fully configurable π) Clean colored message with formatting π¨
π Revive & Unban System
/lifeheartspro revive <player> /lifeheartspro unban <player>
π Automatically:
Removes the ban Restores default lives Sends proper messages π¬ NEW: Global Prefix System Every chat message now automatically includes a prefix No more missing or inconsistent messages Clean and professional look
β Works for:
Commands Team system Life system Errors
β Excluded:
ActionBar (clean by design) π Language System Improved Fully optimized German & English files Added: elimination messages ban messages Better placeholder handling Missing keys now handled safely π§ Internal Improvements Reworked message handling system Cleaner code structure Improved command logic Better error handling π Bug Fixes Fixed missing message errors Fixed inconsistent team messages Fixed reload issues Fixed plugin loading problems Fixed incorrect project structure π Important
β οΈ After updating:
plugins/LifeHeartsPro/lang/
Delete this folder β it will regenerate automatically.
π― Summary π Real ban system π Revive + unban π¬ Global prefix system π Better language handling π§ Cleaner code β€οΈ Support
If you enjoy the plugin: β Leave a review π¬ Give feedback π Help the project grow
π₯ Short Version (fΓΌr Titel)
v2.4.0 - Ban System, Revive/Unban, Global Prefix, Bugfixes
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:vCpl4G6Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NA8cl1Vd:vCpl4G6Y"
}

