1.0.1
Compatibility
Changes
š¦ Persistent Block Damage 1.0.1 ā What's New
š Material-Based Impact Sounds
- Each block material has a distinct mining sound: stone, metal, wood, sand, dirt, glass, plus an extra tool-specific sound (axe on wood, shovel on sand).
- Customizable mineral sounds with overrides (
block|#tag = sound). - Configurable sound timing (
soundIntervalTicks, 4 = vanilla cadence).
š¦ Water Effects
- Splash effect + sound when mining underwater or when water is between your eyes and the block.
⨠Impact Particles
- A burst of block particles occurs each time the crack stage advances.
šļø HUD Damage Bar (New)
-
Displays the % remaining damage of the targeted block, using colors (green/yellow/red), with amber when damage is being lost.
-
Dual control:
- Global (admin):
/pdb hud global on|offor via the mod config. Disabled by default. - Personal (player):
/pdb hud(toggle), persistent per player even after server restarts.
- Global (admin):
š„ļø Configuration GUI
- Native config screen available from the Mods menu (no longer commands only), with EN/ES translations.
š ļø New Commands
| Command | Who | Function |
|---|---|---|
/pdb hud |
Anyone | Toggle your damage bar |
/pdb hud on|off |
Anyone | Enable/disable your damage bar |
/pdb hud global [on|off] |
Admin | Damage bar for the entire server |
āļø New Config (persistentblockdamage-server.toml)
[feedback]
soundEnabled = true
soundIntervalTicks = 4
impactSoundOverrides = []
impactParticles = true
waterSplashEffects = true
[hud]
hudIndicator = false # GLOBAL bar, disabled by default
(renderDistance now also limits sound/HUD synchronization.)
š Fixes
- Fixed a crash on loading ("Cannot get config value before config is loaded") caused by reading the config from a static initializer.
- Fixed command messages with correct color encoding.
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:erOUfqdI:Gib2xvaK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:erOUfqdI:Gib2xvaK"
}

