Tags
Creators
Details
0.2.5-beta
Compatibility
Changes
0.2.5-beta
Important Upgrade Notes
If updating from an earlier 0.2.x beta:
-
Delete
config/nourished/scanner_spec.jsonbefore launching the game. -
Load your world and run:
/nourished invalidate_cache -
Rejoin the world to rebuild cached nutrition data.
Existing worlds may continue using outdated scanner data until these steps are completed.
These steps ensure recipe inheritance, nutrient tags, and scanner data are regenerated using the latest compatibility improvements.
Added
- Recipe inheritance now works client-side, allowing composite foods to display accurate multi-nutrient tooltips without requiring server-side lookups.
- Single-ingredient transformation recipes now inherit nutritional categories correctly (e.g. bread → bread slice, raw meat → cooked meat, apple → apple mash).
Fixed
- Pam's HarvestCraft mixing bowl recipes and other custom recipe types are now discovered by the inheritance pipeline. Previously, only crafting and smelting recipes were supported.
- Pam's cooking containers (bakeware, cutting board, pot, saucepan, mixing bowl, skillet, juicer, grinder) and Croptopia cooking tools (frying pan, cooking pot, food press, knife) are no longer treated as nutritional ingredients during recipe inheritance.
- Non-food items such as salt, oils, spices, flavorings, yeast, water bottles, and alchemical ingredients are now ignored during inheritance instead of lowering confidence counts.
- Fruits such as berries and raspberries no longer incorrectly classify as raw foods.
Compatibility
- Greatly expanded nutrient tag coverage across Pam's HarvestCraft 2 (Crops, Trees, Food Core, Food Extended), Croptopia, Create: Food, Farmer's Delight, Wilder Nature, Undergarden Delight, and additional food mods.
- Hundreds of composite foods now inherit and display more accurate multi-nutrient profiles.
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:Bxa7kzRP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gXy6YNys:Bxa7kzRP"
}

