
Balanced Hardcore
Balanced Minecraft Hardcore (BMH) gives you flexibility in difficulty by replacing death by distant respawn based on your difficulty and Eternal Items possessed. BMH is the perfect middle ground between normal Minecraft and hardcore Minecraft.
Tags
Creators
Details
1.20.2-1.6.0
Compatibility
Required content
Changes
Added
- A distant respawn now plays a short journey scene. The death screen fades to black, and a night sky comes in. A star lights up for your home. Then a line goes from star to star, like a star reading of the Navigator's Amulet, and the view follows it far away. An amethyst chime rings at each star. The message "A new journey begins for you" shows. At the last star, the sky breaks into pixel blocks over your new place, and the bell rings.
Changed
- The respawn message now shows on a server too. Before, only the player of a singleplayer world or a LAN host saw it.
- After a distant respawn, you take no damage for 10 seconds while the scene plays. Vanilla gives 3 seconds.
- Only a distant respawn plays the bell and the message. In Adventure mode or when no safe place is found, the respawn is a normal one.
Fixed
- A distant respawn no longer shows your bed or the world spawn for a moment before it takes you to the new place.
- When you turn off the
removeCoordinatesInSurvivalgame rule, the full F3 screen with coordinates comes back at once. It also comes back when no player is in survival. Before, it stayed reduced until you setreducedDebugInfoto false. - If you reload a world while the rule is on and then turn the rule off, the F3 screen stays reduced. Run
/gamerule reducedDebugInfo falseone time to fix it.
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:dc7VO9FK:zciWEu8P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dc7VO9FK:zciWEu8P"
}
