4.2.0
Compatibility
Changes
HUD_BW 4.2.0 - Changelog
Forge 1.20.1 and Fabric 1.20.1
New widgets (hidden by default, enable them in the editor)
Air: remaining air in seconds. Text, number, icon + number or bar mode. Visibility: always, or only while the value is changing. XP: experience level. The bar mode also shows progress to the next level. Armor Toughness: now a separate widget. Armor Points shows armor only, and both have an icon + number mode. If your old layout had Armor Points visible, Toughness turns on right below it. Temperature: ambient temperature, calculated only from vanilla data (biome temperature, cooling with altitude). White in the comfortable range, blue when cold, orange to red when hot. °C or °F.
Food and Saturation
Eating preview: holding food shows a blinking "+N" for hunger and saturation gain. In bar mode it also draws a blinking ghost segment. It works without AppleSkin. Saturation now has 4 modes: text, number, icon + number and bar, using a gold-tinted vanilla drumstick.
Widget styling
New Frame option on every widget: none, four L-shaped corners, or a full border. Color and size are adjustable. Visibility "only when changing" for all stat widgets. Durability at 100% is now shown as a green ✓ (armor widgets, Armor Hotbar, Held Item).
Vanilla HUD hiding
Each widget's settings have "Hide vanilla: …" checkboxes for what it replaces (hearts, hunger, armor, air, XP, effects, item name). New Style → Vanilla HUD window with 13 toggles: hearts, armor, hunger, air, mount health, XP, jump bar, hotbar, item name, effect icons, crosshair, scoreboard, boss bars.
Editor
Hovering a widget zooms it smoothly and draws it above all others. While dragging, it stays at its final size. New Style → Preview autofill: an empty widget being dragged shows sample content (armor, potion effects, held item, eating preview). Removed the bottom hint bar.
Fixes
Widget name labels no longer show through the settings menus. Frames no longer hide under the widget background. Old configs still load; new options use defaults.
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:NmycxeQE:FTqhsy2o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NmycxeQE:FTqhsy2o"
}

