Links
Tags
Creators
Details
0.2.0+1.21(.1)
Compatibility
Changes
Changelog
-
Biome-based tinting for wild crops: Implemented biome-based color tinting for wild crop blocks (lettuce, strawberry, tomato, and red onion) by splitting textures into base and tintable layers.
-
Item handling and interaction: Refactored
IronCupIteminteraction logic to resolve item management issues in Creative mode and improve general item usage. -
Block color registration: Added client-side block color handlers and updated data generation (
datagen) to support tintable crops. -
Gradle and NeoForge configuration: Streamlined metadata generation in Gradle and updated the
neoforge.mods.tomltemplate using variables to define mod loading sides. -
Build system migration to Kotlin DSL and Stonecutter:
- Migrated
build.gradleandsettings.gradlefiles to Kotlin scripts (build.gradle.ktsandsettings.gradle.kts). - Added multi-version support scripts via Stonecutter (
stonecutter.gradle.kts,buildSrc/, and configurations for versions 1.21.1 and 1.21.3). - Moved
neoforge.mods.tomldirectly to the resources directory (src/main/resources/META-INF/).
- Migrated
-
Blocks and Recipes:
- Updated
GrillTableBlockandGrillTableBlockEntity, including JEI integration (JeiNerdSoftKitchenPlugin,GrillCookingCategory). - Adjusted
TomatoCropBlockandTomatoCropPoleBlockbehavior. - Improved serialization and definition of recipes (
CookRecipe,CupContentIngredient,ShapelessCupCraftingRecipe,CurdleRecipe,MixRecipe).
- Updated
-
Data Generation (Datagen) and Registry:
- Added
DatagenUtilsand refactored the data generator provider. - Adjusted generators for block states, item models, advancements, block tags, and sound definitions.
- Updated the internal logger (
NerdSoftKitchenLogger).
- Added
Optional dependencies
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:1ePZxh6a:bF8caBeg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1ePZxh6a:bF8caBeg"
}

