
IG: Durability Multiplier
Complete control over item durability in Minecraft 26.1+. Multiply durability by any factor or make items completely unbreakable — all through GameRules. Works automatically with modded items via vanilla tags. Part of the Instant Gratification Collection.
Tags
Creators
Details
1.0.0+1.21.1
Compatibility
Required content
Changes
[1.0.0+1.21.1]
Added
- Initial Minecraft 1.21.1 Release Anchor: Native port of Durability Multiplier to Fabric 1.21.1 and Java 21 toolchains.
- Granular Percentage Scaling & Multipliers: Configure durability scaling via GameRules (
ig:dm_percent_*) and sparse JSON config, supporting fractional durability reductions (< 100%) and massive durability boosts (> 100%). - Unbreakable God Mode: Complete damage negation and unbreakable durability toggle per category and per item (
ig:dm_infinity_*). - Single-Use (Glass Mode) Engine: High-risk 1-hit break mode inflicting full item durability on damage events, with
-1sentinel percentage support and red warning tooltips. - Dynamic Modded Item Discovery: Automatic registry scanning detects damageable items added by other mods, automatically generating GameRules and config options without manual setup.
- Hierarchical Priority Cascade: Smart resolution cascade ensuring specific overrides cleanly take precedence (
Per-Item > Sub-category > Category > Global). - Live Tooltip Networking: Seamless Fabric networking synchronization broadcasting active durability scaling to client tooltips in real time.
- YACL v3 Configuration Screen: In-game configuration interface powered by YetAnotherConfigLib (YACL v3) and ModMenu integration, featuring categorized tabs and a Ko-fi creator support button.
- DasikLibrary 1.21.1 Engine: Built on DasikLibrary for robust dynamic GameRule management and cross-mod synchronization.
Links & Resources:
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:vLdIEU16:ylbaWPWf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vLdIEU16:ylbaWPWf"
}
