Tags
Creators
Details
Licensed MIT
Published 2 months ago
All versions
0.2.3-beta
Beta
Nourished v0.2.3-betalast month 6
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
[0.2.3-beta] - 2026-05-31
Added
- Multi-nutrient recipe inheritance — complex dishes now contribute to multiple food groups based on their ingredients. Eating a steak sandwich gives Proteins, Grains, and Vegetables credit automatically.
- HUD hide-above threshold — bars above a configurable percentage are hidden from the HUD. Set to 0.4 to only see bars that need attention. as requested. in #3
- HUD show-below threshold — bars below a configurable percentage are always shown regardless of other visibility settings.
- Show zero nutrients on HUD — toggle to show bars at 0% so you always know what you're missing.
- HUD background opacity — configurable from fully transparent to fully opaque.
- Vertical HUD layout — bars render as side-by-side columns filling upward instead of horizontal rows.
- HUD flash on nutrient increase — bars briefly highlight for 2 seconds when a nutrient increases from eating.
- Multi-nutrient full registry analysis — /nourished scan_analysis command analyzes all 4700+ classified foods and writes multi-nutrient recommendations, overlap matrix, ambiguity report, and scanner metrics to config/nourished/scanner_analysis/.
- Run Analysis button in the Scanner config tab triggers full registry analysis in game.
- Data Scan button renamed from Scan for clarity.
Changed
- HUD settings now apply live without requiring Save & Quit.
- Pre-scan hint text removed from Scanner config tab.
Fixed
- HUD vertical layout and zero-bar visibility were reading stale config values due to Cloth Config write-on-save behavior — fixed with live config application.
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:gXy6YNys:hgu0qTYQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gXy6YNys:hgu0qTYQ"
}



