Tags
Creators
Details
1.2.0
Compatibility
Changes
Changelog
v1.2.0 – Major Feature Overhaul
This update is a full upgrade of MaxHearts, adding advanced systems while improving stability, configurability, and compatibility.
New Systems
-
Added full lifesteal system with:
- PvP lifesteal
- Projectile & tamed-mob lifesteal
- Trap lifesteal (TNT, lava, falling dripstone)
- Daily caps, cooldowns, bypass permissions, and opt-out mode
-
Added revive system, including:
- Craftable Revive Tokens (custom recipe, name, lore, model data)
- Token requirement toggle
- Offline-safe unbanning & restoration
-
Added death penalty system:
- Configurable heart loss
- Floor actions: block / clamp / kick / ban
- Offline-safe pending application
-
Added heart shard and consumable heart item crafting recipes
- Customizable names, lore, and model data
-
Added optional Vault integration for heart purchases
- Supports flat or progressive price models
- Daily caps & cooldowns
-
Added combat tag system
- Enter/leave combat notifications
- Optional logout protection
Improvements
- Fully rewritten killer-resolution engine
- Detects TNT, dripstone, and lava owners reliably
- Compatible with “Last Stand” plugins
- Offline-player handling improved
- Tab completion rewritten and permission-aware
- Auto-prunes old daily counters
- Added safe merge logic for config upgrades
Fixes
- Prevented Revive Token spoofing
- Fixed item-dupe edge cases during death/ban
- Correct absorption restoration after early bed exit
- Corrected tamed-mob and projectile lifesteal behavior
- Fixed various cooldown, floor-action, and pending-heart issues
If you are upgrading from older versions, your existing config will automatically merge with new keys.
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:2CbID0MU:UDhks6bT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2CbID0MU:UDhks6bT"
}

