Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 2 days ago
All versions
2.6.1
Release
Create: Central Kitchen 2.6.1 for Create 1.21.1-6.0.102 days ago 4,591
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Create: Central Kitchen 2.6.1
Requires Create 6.0.10 and Create: Dragons Plus 1.11.9 or newer. Farmer's Delight integration requires Farmer's Delight 1.3.2 or newer.
Fixed
- Fixed severe server tick lag when Spouts repeatedly check items on Depots, including empty and filled buckets. Brewin' and Chewin' Filling and Emptying fallbacks now cache their complete recipe selection and refresh after recipe or tag reloads. Native Create recipes retain priority. (#203)
- Condensed food variants in the Mechanical Arm's Ponder target list using Create: Dragons Plus's grouped tag cards. The stacked cards cycle between whole foods with a fade transition. Hover to pause, scroll to select a variant, and left-click to open its Ponder scenes. Partially served foods stay out of the carousel and retain their individual Ponder access. (#202)
- Corrected Ponder demonstrations for Cultural Delights feasts, Rustic Delight pancake stacks, Festive Delight chicken, and Hearth and Harvest Casks, including serving states and packaging instructions. (#197)
Localization
- Added English and Simplified Chinese names for food groups. Shared controls and tooltips use Create: Dragons Plus's localization.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| create-central-kitchen-2.6.1-sources.jar | Unknown | 332.44 KiB |
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:btq68HMO:FaEwZ1Pr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:btq68HMO:FaEwZ1Pr"
}

