Tags
Creators
Details
0.2.6-beta.5
Compatibility
Required content
Changes
Nourished: 0.2.6-beta.5
Changes
- Improved compatibility handling for modded food items with incomplete recipe definitions
- Refined fallback classification when recipe inheritance is unavailable
- Better logging and trace output for resolver cache misses
- Improved stability of nutrient inference pipeline for composite foods
Improvements
- More consistent behavior when recipe graphs are missing or incomplete
- Clearer distinction between:
- recipe-based classification
- inference-based classification
- cached external classification
- Milk Bottles Now Register Dairy vaules.
Fix / Known Issue Note: Source Inspector Debug Trace
Some Create cutting board recipes are not exposed as standard recipe entries.
-
The /source_inspector debug output may show incorrect values in Weighted Totals and Why X Won when an item’s classification is changed by a recipe-level override.
-
This is caused by the trace displaying intermediate keyword-scoring results even after a later override is applied. The override is correct and fully reflected in-game, this issue only affects the debug visualization.
-
If you see mismatched breakdowns (correct final category but inconsistent intermediate values), that’s the cause.
No gameplay impact. Debug trace fix coming in the next update.
Example:
createfood:hamburger_onion→ missing protein classificationcreatefood:hamburger_onion_lettuce→ works when ingredient chain is explicit
Cause
- Create cutting board recipes do not register as standard recipe sources, breaking inheritance resolution.
Impact
- Some composite foods may be misclassified or partially unclassified
Status
- Not fixable in this release
- Requires Synthetic Recipe Resolver (future system)
- Confirmed via trace dumps and reproduction
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:O2LfqMkW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gXy6YNys:O2LfqMkW"
}




