Tags
Creators
Details
All versions
5.0.0
Release
DynamicHUD 5.0.03 days ago 8
Compatibility
Minecraft: Java Edition
26.1.1–26.1.2
Platform
Fabric
Supported environments
Client-side
Changes
Updated to version 26.1.x
Major Highlights for Users:
- Removed YACL: YACL dependency has been removed and replaced.
- Better Minecraft Skin: MinecraftSkin has been enhanced with UI sound effects, better search and cursor change.
- Tooltips: More tooltips have been added for widgets as well as options.
- Customisated: Widgets will now look more customised and smooth.
Major Changes for Developers:
- [Feat.] TextWidget (String -> Component): The text widget now also accepts a component as well as a String through the registry supplier. Components can be styled using MutableComponent when passing to the supplier.
- [Update] DynamicValueReigstry rewritten: The registry has become fully shared and now requires Identifier as key.
- [Fix.] Styled characters in drawChromaText:
drawChromaTextnow accepts and renders components with their original styles. - [Refactor]:
drawScalableTextanddrawTruncatedScaledTexthave been moved toDrawHelper. - [Feat.]
Util.getSearchResults(): The function will either flatten and sort the resultant options, or return sorted option groups + options as per the booleanflattenset in function parameter. - [Refactor.] Change in option
name,descriptionandvalueaccess specifiers: Use the getters for their fields respectively. - [Feat.]
renderTooltipIfHovered(): Function was overloaded and now waits for a specified delay before displaying the tooltip. - [Feat.]
valudIdin WidgetBuilder: For widgets usingDynamicValueWidget, the fieldsregistryKeyandregistryIdhave been replaced withIdentifier valueId - Full Changelog: https://github.com/V-Fast/DynamicHUD/compare/v4.1.0...v5.0.0
The Wiki has also been updated.
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:hQbzUScT:cnila8js"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hQbzUScT:cnila8js"
}

