Tags
Creators
Details
0.2.1-beta
Compatibility
Changes
[0.2.1-beta] - 2026-05-17
Upgrade Notes
If upgrading from 0.2.0-beta or earlier, delete:
config/nourished/scanner_spec.jsonconfig/nourished/nutrients.json
Both files will regenerate on launch.
If your world contains an older nourished-generated datapack, run:
/nourished repair_generated_datapack
then:
/reload
Added
-
Raw Food Penalties
- Raw foods can now apply effects and nutrient penalties.
- Four severity levels: Fine, Mild, Medium, Severe.
- Settings are configurable in
config/nourished/raw_food.json.
-
Gut Flora
- Repeated raw food consumption increases sensitivity to future penalties.
- Recovery occurs through cooked and varied diets.
- Stored separately from the nutrition system.
-
Non-Beneficial Nutrients
- Nutrients can now be marked as harmful when accumulated in excess.
- HUD indicators, toasts, and threshold checks account for this behavior.
-
Raw Food configuration options added to the Cloth Config screen.
-
Compat integrations now appear in dedicated config categories.
- Large Stamina Overhaul
- Peak Stamina
- Spice of Life: Onion
-
New Food Safety chapter in the Patchouli guide.
-
Nutrient schema validation.
- Outdated
nutrients.jsonfiles are automatically regenerated when required fields are missing.
- Outdated
-
/nourished repair_generated_datapack- Repairs generated nutrient tags after nutrient definition changes.
-
Expanded nutrient tag coverage for vanilla and supported food mods.
-
Added:
PHILOSOPHY.mdARCHITECTURE.md
Changed
-
Returned to five nutrient groups:
- Fruits
- Vegetables
- Proteins
- Grains
- Dairy
-
Removed the Sugars category.
- Existing sugar-tagged foods have been reassigned.
-
Legacy player data containing removed nutrient keys is now migrated automatically.
-
Documentation updated for the five-group system.
Fixed
-
Raw vanilla meats now correctly trigger raw food penalties when appropriate.
-
Non-beneficial nutrients no longer trigger low or critical nutrient warnings while decaying.
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:2AvbjIhN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gXy6YNys:2AvbjIhN"
}

