Tags
Creators
Details
0.2.7-beta.1-Hotfix
Compatibility
Required content
Changes
Nourished 0.2.7-beta.1-hotfix
Bug Fixes
-
Fixed a dedicated-server startup crash Split client-only HUD panel color registration out of the common color registration logic.
-
Client-only color definitions for the Calorie HUD and Activity Log HUD are now registered only on the client.
-
Prevents Calorie HudScreen and ActivityLog HudPanel from being loaded during dedicated server initialization.
-
Fixes the RuntimeDistCleaner crash caused by attempting to load net.minecraft.client.player. LocalPlayer on a dedicated server.
-
Tested on a NeoForge dedicated server and confirmed successful startup
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:i4sxTnr9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gXy6YNys:i4sxTnr9"
}




