1.0.2-1.21.6
Compatibility
Changes
Hunger Bound v1.0.2-1.21.6 Release Date: June 20, 2025 Game Version: Minecraft 1.21.6 Loader: Fabric
🚨 Major Features ⚰️ Death-Ban System Players are now automatically banned after reaching a configurable death limit. This introduces permanent consequences for repeated failure:
Fully configurable in config.json
Upon being banned:
A player head is placed in a chest at the death location
A sign is attached showing:
Player's name
Heart count at death
Total unique foods eaten
Days survived (based on playtime)
Adds tension and permanence to long survival runs
🔁 Auto-Unban System Banned players are automatically unbanned after a delay (configurable in milliseconds). This allows players to return after a “cooldown” period:
Works offline and survives server restarts
Profiles are stored persistently to ensure reliability
Unban delay is fully customizable
💀 Orb of Revival A renamed Eye of Ender crafted with a player head can revive a banned player:
Clears all their death, health, and food progress
Resets them as if they were a fresh player
Sends a global revival announcement
Plays a totem-like sound effect upon use
Awards the Second Chances advancement
⚙️ Config Additions Located in config/foodhearts/config.json:
json Copy Edit { "banAfterDeathsEnabled": true, "banAfterDeathsLimit": 3, "autoUnbanDelayMillis": 86400000 } banAfterDeathsEnabled: Toggle death-ban system
banAfterDeathsLimit: Max deaths before ban
autoUnbanDelayMillis: Milliseconds until auto-unban (default 1 day)
✅ Fixes & Improvements Fixed: Revival now properly resets persistent death count
Improved: All revival logic now uses PlayerDataManager and PersistentState
Improved: Advancement syncing and heart reapplication is clean across deaths and revivals
Fixed: Totem sound now reliably plays on orb use
Streamlined: Ban logic now reuses proper reset logic from respawn system
🔧 Technical Notes Fully updated for Minecraft 1.21.6
Works on vanilla clients (no mods required)
Designed for hardcore, anarchy, or challenge SMPs
Lightweight and multiplayer-safe
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:rje4kJCt:mDgv7hKY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rje4kJCt:mDgv7hKY"
}

