All versions
1.0.0
Release
Compassionate-Hardcore-1.0.0last month 288
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Changes
Added
- Updated to Minecraft 26.2, Fabric Loader 0.19.3, and Java 25.
- Added separate enable/disable settings for each world.
- Added /chm enable, /chm disable, and /chm status commands.
- Added clickable [ENABLE] and [KEEP DISABLED] options for new worlds.
- Added three configurable exile difficulty profiles:
- Merciful: 50,000–100,000 blocks
- Standard: 100,000–500,000 blocks
- Brutal: 500,000–1,000,000 blocks
- Added clickable difficulty selection after enabling the mod.
- Added /chm profile <merciful|standard|brutal> for changing the profile later.
- Added the selected difficulty profile to /chm status.
- Added persistent storage for world settings, difficulty profiles, penalty locations, and remaining penalty time.
- Added a protected one-second preparation period before teleportation.
- Added clearer orange and red warning messages.
- Added destination coordinates to penalty messages.
- Added release notes to the description displayed in Mod Menu.
- Added world-border validation when selecting exile destinations.
Changed
- Compassionate Hardcore is now disabled by default in new worlds.
- The initial setup prompt is only shown to the singleplayer world owner or authorized operators.
- /chm enable, /chm disable, and /chm profile can only be used by the world owner, authorized operators, or server console.
- Exile distance is now measured from the player’s actual death location instead of the world origin.
- Exile destinations now use true radial distance in a random direction.
- Dying during an active penalty returns the player to the same exile location.
- After the 30-minute penalty expires, the next death selects a new exile location.
- Joining a CHM-enabled world now displays a clearer warning.
- Teleport preparation time was reduced from three seconds to one second.
Fixed
- Fixed singleplayer world owners being unable to use setup controls when cheats were disabled.
- Fixed exile distances being calculated from the respawn point instead of the actual death location.
- Fixed the game becoming stuck after dying with a bed respawn point.
- Fixed problems when returning to distant or previously loaded penalty locations.
- Fixed penalty progress being lost after closing the world or server.
- Fixed players being able to move, interact, or take damage before the penalty teleport completed.
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:n6L9g0h8:uMcfLRA1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:n6L9g0h8:uMcfLRA1"
}

