Tags
Creators
Details
Licensed ARR
Published last year
Updated last week
All versions
1.1.0-NeoForge-mc26.1
Release
1.1.0 (NeoForge 26.1-26.3)last week 120
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
New
- New gamerule minHearts (default 0): players can't go below this amount of hearts
- 0: players become spectators when they lose their last heart (same as before)
- greater than 0: players never drop below this amount of hearts and are never made spectators
- New gamerule goldenAppleRestoresHearts (default false): normal golden apples also restore lost hearts, but only up to 10 hearts. Enchanted golden apples still go up to maxHearts.
- New command: /playerhearts get [<targets>] shows the current hearts of a player (with a single target the hearts are returned, so the value can be used with /execute store)
- New command: /playerhearts set <numberHearts> [<targets>] sets the hearts of a player (the short form /playerhearts <numberHearts> [<targets>] still works)
- Chat messages when you lose or gain a heart, and a message to everyone when a player loses their last heart
- Added German translation for the gamerule descriptions
Fixes
- Only deaths in survival and adventure mode cost a heart (no more lost hearts in creative or spectator mode, e.g. through /kill or the void)
- /playerhearts:
- feedback now goes to whoever ran the command (also works from the server console and command blocks)
- returns the number of changed players, so it works with /execute store
- only accepts players as targets
- shows an error when run from the server console without a target
- Hearts are no longer lost when another mod cancels the death (e.g. revive mods)
- The heart capability is now registered correctly
- Removed duplicate registration of Forge's /config command
Changes
- canRestoreHearts is the main switch: when it is false, no golden apple gives hearts
- /playerhearts only accepts values between minHearts (at least 1) and maxHearts
- /playerhearts: the target player is notified when someone else changes their hearts
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:UopFqYzZ:BRPPOpJY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UopFqYzZ:BRPPOpJY"
}

