1.1-beta
Compatibility
Changes
๐ Blueprint HUD v1.1-beta โ The "Core HUD" Update
This update establishes the foundation of Blueprint HUD. It focuses on the core gameplay loop: tracking required items, visualizing progress, and clearly showing completion status โ all directly on the HUD.
๐ New Features
Blueprint HUD Overlay: A persistent on-screen HUD that displays all tracked blueprint items with their required counts.
Live Progress Bars: Each item now shows a dynamic progress bar that fills as you collect blocks.
Completion Indicator: When an item is fully collected:
The progress bar fills to 100%
A โ checkmark appears
The item is visually marked as completed
Automatic Progress Tracking: Item counts update automatically as blocks are collected โ no manual refresh required.
๐จ Visual Feedback
Green Completion State: Completed items visually switch to a green-tinted state for instant recognition.
Strike-through Text: Finished items display a strike-through effect to clearly separate them from incomplete ones.
Clean HUD Layout: Consistent spacing, readable text, and compact bars designed to stay out of the way during gameplay.
โก Improvements & Changes
Optimized HUD Rendering: Reduced unnecessary redraws to keep performance smooth even with many items tracked.
Stable Item Ordering: Blueprint items maintain a consistent order instead of shifting during updates.
Config-backed Blueprint Storage: Blueprint data is stored persistently, preventing accidental loss between sessions.
๐ Bug Fixes
Fixed progress bars not updating correctly when items were added mid-session.
Fixed completed items occasionally failing to display the checkmark.
Resolved HUD flickering issues when rapidly collecting items.
Fixed multiple Fabric/Yarn compatibility issues related to HUD rendering.
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:zKeOYZjQ:hKq8aMqD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zKeOYZjQ:hKq8aMqD"
}

