Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 months ago
Updated last month
All versions
v0.1.2-mc26.1.x
Release
HerobrineHUD 0.1.2last month 54
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Server-side
Client and server
Changes
Added
- Added official support for Minecraft
1.21.11 - Added split Fabric build pipelines:
:fabricfor26.1+:fabric-remapfor1.21.x
- Added layered Mojang official mappings + Parchment support for the active
1.21.11remap build - Added version-aware main/client source layout under
fabric/src/mc<version>/mainandfabric/src/mc<version>/client - Added version bridges for networking, HUD render registration, and keybinding registration
- Added a HUD provider registry and public provider API for registering alternate HUD implementations
- Added a built-in classic HUD provider and provider selection support in the management screen
- Added a read-only HerobrineHUD client data API for teams, players, placements, hotkeys, spectating state, and HUD settings
- Added serializable HUD data snapshots and JSON snapshot export for external HUD/UI consumers
Changed
- Reorganized Fabric multi-version source loading to support separate versioned
mainandclientcode - Split GUI and HUD implementation where Minecraft/Fabric APIs differ between
26.1and1.21.x - Split chat mixin implementations by Minecraft version
- Updated Gradle version routing, debug tasks, and wrapper/toolchain expectations for the new Loom split
- Moved classic HUD rendering behind the provider system
- Updated the classic HUD renderer to consume the public data API instead of internal client state directly
- Relaxed the Fabric metadata Minecraft dependency for
26.1builds to allow patch-compatible26.1.xversions - Disabled build and release targets for unfinished
1.21.4and1.21.1ports
Fixed
- Fixed shared player avatar rendering state extraction regression that caused the 3D player model to render too high in player cards
- Fixed
26.1.2being rejected by Fabric Loader even though the26.1build is patch-compatible
Notes
- Release date: 2026-06-23
1.21.4and1.21.1source directories remain as incomplete porting placeholders and are not release targets- NeoForge remains stubbed and is not part of this completed migration
- PowerShell users should quote version overrides such as
"-PdebugVersion=1.21.11"
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:E53CyfJb:pnFd3OQt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E53CyfJb:pnFd3OQt"
}

