1.0-Alpha
Compatibility
Changes
๐ Blueprint HUD v1.0.0 โ The "Master Settings" Update
This update completely overhauls how you interact with your blueprints. No more clunky chat commands; everything is now handled through a unified, sleek interface.
๐ New Features
Master Settings GUI: A new unified menu (Default: C) that combines color settings and block management into one screen.
Searchable Block Selector: No more guessing item IDs. Type the name of a block in the search bar, see the icon, and click to add it to your HUD instantly.
Custom RGB/Hex Support: You can now type in specific Hex codes (e.g., FF55AA) to get the exact color you want for your progress bars.
HUD Drag & Drop: Press B to enter Edit Mode. You can now freely click and drag the HUD to any position on your screen.
Delete on the Fly: While in Edit Mode, a red [X] appears next to items. Click it to remove them from your list instantly.
โก Improvements & Changes
Persistent Config: Your HUD position and custom colors are now saved to blueprinthud_config.json. They will stay the same even after restarting the game.
Death Reset Notification: If you die and your progress marks reset, a temporary on-screen warning will now notify you.
GLFW Input Polling: Rewrote the dragging logic to use GLFW, fixing the "mouse cursor locking" bug when trying to move the HUD.
Search Optimization: Added icon rendering in the search dropdown for faster identification of items.
๐ Bug Fixes Fixed a crash when trying to open the color preset menu in Minecraft 1.21+.
Fixed an issue where the progress bar would sometimes "jitter" when reaching 100%.
Corrected package visibility issues that caused compilation errors in Fabric environments.
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:dL82ofzi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zKeOYZjQ:dL82ofzi"
}

