
Tango's Dynamic Hud Lib
A small client-side Fabric library for movable HUD widgets. Provides an API that other mods can use to register HUD elements. For players, that means TangosHudLib renders and stores the widgets that another mod registers through this l
Links
Tags
Creators
Details
1.2.0+26.2
Compatibility
Required content
Changes
Tango's HudLib 1.2.0
Added
- Named HUD layouts can be listed, saved, loaded, deleted, exported, and imported per registering mod.
- Validated layout share codes make it possible to move layouts between installations.
- A mod-specific HUD editor can be opened from another configuration screen.
- Minecraft
26.1.xand26.2.xsupport. - Dedicated editor hotkeys for each mod that registers widgets through Tango's HudLib.
- Owner-aware widget registration so multiple mods can use the same widget ID without conflicts.
- A client-side Fabric library for defining movable HUD widgets with
@HudWidgetmethods. - Built-in drag-and-drop HUD editor with persistent widget state.
- Public registration API, development widget examples, and validation tests.
Fixed
- The HUD editor hotkey now opens and closes directly from open container screens.
Changed
- Hover a HUD in the editor and use the mouse wheel to adjust its font size from 50% to 300%.
- Font-size scaling applies to the complete widget, including its background, layout, hitbox, and drag bounds.
- The editor remains an overlay when opened from an existing screen, keeping container screens and their context HUDs active.
- HUD positions are stored per mod and widget, while existing unqualified saved widget positions remain readable.
- Ported Fabric, HUD rendering, screen, and key-mapping integration to the current Minecraft client APIs and Java 25.
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:zErAqm0g:THd8o628"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zErAqm0g:THd8o628"
}
