All versions
0.8.0+fabric-26.3
Release
DuraPing 0.8.0 (Fabric 26.3)2 hours ago 3
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Added
- Minecraft 26.2 and 26.3 support on both Fabric and NeoForge.
- Minecraft 26.1 and 26.1.1 support on Fabric. On NeoForge, the 26.1 line needs 26.1.2.
- On Fabric, 26.3 needs Fabric Loader 0.19.3 or newer.
Changed
- FastStats updated to 0.31.0. It now appears as its own entry in the mod list and adds a FastStats button to the Telemetry Data screen for opting out. Pseudonymous usage metrics remain on the 26.x builds only, and DuraPing's copy of FastStats does not load on Fabric 26.1 or 26.1.1.
- Cloth Config is listed as optional on Modrinth and CurseForge for every file. Without it, the config screen is unavailable and the mod runs through the JSON config.
Fixed
- Mod Menu no longer logs an error on launch when Cloth Config is not installed.
- The config screen's keybind help now points to Options, Controls, Key Binds, Miscellaneous.
- A worn item now alerts each time it drops into a more severe tier. A warn alert used to silence the danger alert that followed it.
- The emergency alert at 2 uses left now fires during a snooze, and on high-durability items, where 3 and 2 uses left both read as 0%. A tier alert for the same item no longer replaces its toast and flash.
- With hysteresis on, an item bouncing around the warn threshold no longer alerts each time, and an item re-arms by the same rule whether it recovers gradually or all at once.
- In singleplayer, block click handlers no longer run on the integrated server thread.
Optional dependencies
Any compatible version
Any compatible version
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:JsUDKArh:EHlNwcMI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JsUDKArh:EHlNwcMI"
}

