Tags
Creators
Details
Licensed MIT
Published last month
Updated 2 days ago
All versions
1.3.0
Release
truhearts 1.3.0last month 21
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platform
Fabric
Supported environments
Client-side
Required content
Changes
A new overlay: the last few hits you took.
- Recent-damage log stacked above the HP readout. Each hit shows the damage amount (real un-rounded value, matching the HP readout's precision) and a short label for the source — mob or player name for attacks, or the environmental cause (
Fall,Fire,Lava,Drowning,Explosion,Void, …). Newest hit at the bottom, older entries stack upward, each fades out over its trailing ~2 s of a 10 s lifetime. Up to 5 entries on screen at once. - Death marker. When the hit that killed you lands, a distinct
☠ Died to <source>line drops into the stream right after the killing entry. Rendered in a dim warm gray so it reads as visually different from a hit — you'll always know which one finished you. - Heal entries too. The log isn't just damage: recovering HP shows up as a green
+ <amount> <label>(mirror of the damage red). Sources labeled where inferable — currentlyRegenerationfor the mob effect,Healedotherwise. Consecutive same-source heals within 2 s coalesce into one growing entry so tick-by-tick regen doesn't spam. Respawn HP snap-to-full is suppressed (it's a respawn, not a heal). - Damage is measured as health + absorption delta, so hits eaten by absorption are counted at the amount the player actually felt — not the residual HP loss after absorption ate its share.
- Two-level toggle model. The existing keybind (Controls → TruHearts → Toggle everything (master)) is now the master switch that turns off every TruHearts overlay in one shot. A new keybind, Toggle recent-damage log, flips just the damage log on/off while leaving the HP readout alone. Both are unbound by default; bind whatever you like in Controls. Both preferences persist in
config/truhearts.json. - Coupled to vanilla-hearts visibility the same way the HP readout is: no vanilla hearts (creative, spectator) → no damage log.
Requires Fabric Loader 0.19.3+ and Fabric API matching your MC version. Still one jar for MC 26.1 through 26.2.
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:DyZnpICK:VzcMuBJL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DyZnpICK:VzcMuBJL"
}

