All versions
1.0.0
Release
Chef's Workbench 1.0.02 weeks ago 38
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Chef's Workbench 1.0.0
Release date: 2026-06-14
Added
- Forge and Fabric builds for Minecraft 1.20.1.
- Forge and Fabric builds for Minecraft 1.21.1.
- NeoForge build for Minecraft 1.21.1.
- Fabric and NeoForge builds for Minecraft 1.21.11.
- Fabric and NeoForge builds for Minecraft 26.1.2.
- Stove cooking with fuel, primary products, and optional fuel byproducts.
- Pan frying with independent-slot and combined recipes.
- Oven baking with eight single-item cooking slots.
- Bamboo steamer cooking with four single-item cooking slots.
- Pot boiling with six combined ingredient slots and one output.
- Counter block and crafting recipes for mod blocks and items.
- JEI, EMI, and REI recipe viewer integrations as optional dependencies.
- Shared generated content, model conversion, validation, and build scripts.
- Manual GitLab compatibility build matrix for testing exact Minecraft and loader version combinations.
Changed
- Mod ID and Java package use
chefworkbench. - GUI layouts and recipe viewer layouts now follow their machine screens.
- GUI textures are sourced from
.source/final/gui. - Machine fuel and cooking progress indicators use shared UI assets.
Fixed
- Shift-click insertion now respects one-item slot limits in the oven and bamboo steamer.
- Frying audio is positional and becomes quieter with distance.
- Particle textures are tightly cropped without transparent border pixels.
- Pan handle UV conversion and machine GUI alignment issues.
Compatibility testing
The GitLab matrix performs compile and package tests only. A passing target is CI-buildable, not automatically an officially supported gameplay version.
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:eehhTHZj:Q47NdVa8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eehhTHZj:Q47NdVa8"
}

