Tags
Creators
Details
0.2.5-beta.5
Compatibility
Required content
Changes
Major refactor: MarieLib required
This is the refactor release. Nourished now hard-depends on MarieLib 0.1.0-beta.1+. Install MarieLib before or alongside this version .
Shared infrastructure (scanner, tracking, datapacks, compat framework, registries, client widgets, most public API) lives in MarieLib. Nourished keeps nutrition gameplay, config, and datapacks.
What changed
- Architecture: duplicate API/registry/scanner code removed;
NourishedAPIdelegates to MarieLib. - Config: four module toggles renamed in
nourished-common.toml(legacy JSON keys still accepted). - Scanner/datapacks: bundled
scanner_spec.jsonuses MarieLib schema keys; delete old generated config to regenerate. - Compat: Nourished-owned compat catalog; LSO, Peak Stamina, and Spice of Life Onion hooks moved here.
- KubeJS: new server events and
NourishedAPIbindings (optional; Nourished still loads without KubeJS).
Fixed
- Preset registry init crash on load.
- Client code updated for MarieLib API renames.
- KubeJS events expose
event.playeron key nutrition events.
Upgrading from any earlier Nourished
- Install MarieLib: required from this version onward.
- Delete
config/nourished/scanner_spec.jsonbefore first launch. - Review
nourished-common.tomlif you customized module toggles (four keys renamed). - Run
/nourished reloador rejoin to refresh cached state.
Dev-Notes
So the reasoning behind this refactor is Nourished was becoming more of a framework than it was a nutrition mod I decided to split it, which will make it easier for me to work on features for nourished.
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:zLludvu9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gXy6YNys:zLludvu9"
}




