Tags
Creators
Details
All versions
2.0.0
Release
DynamicHUD 2.0.0 - 1.20.42 years ago 138
Compatibility
Minecraft: Java Edition
1.20.4
Platform
Fabric
Supported environments
Client-side
Changes
Complete rewritten of previous versions.
Major changes
- Adding widgets is now more simpler
- Integrate DynamicHUD with a simple interface
- Multi-Mod support
- WidgetRenderer for rendering groups of widgets of a specific ID.
- Different groups of widgets are saved to different files as per the developer.
- Widgets are now compiled with Unique IDs to identify them across mods.
- Better dragging, snapping and border control.
- Scalability of widgets is much more improved in the hands of the player.
- Using DynamicValueRegistry to supply the library with changing values.
- Widgets can be rendered on any screen as per the developers requirement instead of the previous TitleScreen and in game.
- Supports more compatibility with other mods.
- AbstractMoveableScreen is simplified heavily.
- ContextMenu now works directly with widgets instead of previosly indirectly from the Abstract screen.
- ContextMenu is improved with better visuals and now accepts Options.
- Default ContextMenu options are: Boolean, Color, Double, Runnable,List/Enum and a SubMenu option. The Option<T> class enables the developer to add more options as per their desire.
Minor changes:
- ModMenuIntegration has been fixed.
- DynamicHUD now uses YACL to manage global settings.
- Removed complex and unnecessary code.
- Overall performace and stability has been improved.
- All previous bugs are fixed.
The wiki has also been updated and explains in much more depth.
A small showcase video was also made on youtube.
Optional dependencies
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:8wiRMAXs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hQbzUScT:8wiRMAXs"
}


