Links
Tags
Creators
Details
All versions
1.1.0
Release
Sp0k's Hud+ v1.1.05 months ago 54
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Sp0k's HUD+ v1.1.0: Settings Update
This release adds a full in-game configuration update for Sp0k's HUD+, making the HUD easier to customize without editing the config file manually.
What's New
- Added a new configurable options screen through Mod Menu.
- Added separate submenu sections for:
- Location information
- Direction display
- Equipment HUD
- Added UI size options:
- Small
- Medium
- Large
- Medium remains the default and keeps the original HUD size.
- Added HUD position sliders for
hudXandhudY. - Added individual toggles for location information:
- Full location info display
- Position
- Biome
- Added individual toggles for direction information:
- Direction display
- Direction guide lines
- Added individual toggles for equipment information:
- Full equipment display
- Armor
- Tools
- Added support for showing tool durability alongside armor durability.
- Added durability display modes:
- Percentage
- Remaining hits
- Updated HUD scaling so text, direction indicators, armor icons, and tool icons scale together.
- Improved right-side equipment layout so scaled icons stay aligned to the screen edge.
Notes
- Mod Menu is optional, but recommended. Without Mod Menu, the HUD still works, but the in-game configuration screen will not be available from the Mods menu.
- Existing config files should continue to work. New options will use their default values if they are missing.
Requirements
- Minecraft
26.1.2 - Fabric Loader
- Fabric API
- Java
25 - Optional: Mod Menu, for the in-game config screen
Optional dependencies
Unavailable 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:V1LiiWq6:umAWX3zY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:V1LiiWq6:umAWX3zY"
}

