Links
Tags
Creators
Details
7.3.0+fabric-26.1.2
Compatibility
Required content
Changes
A visual overhaul of all three blocks. The Kitchen Station and Kitchen Access Point get new models and textures, and the Kitchen Station now shows a distinct screen for "linked, but the network is offline".
Added
- The Kitchen Station screen reads its status in three states. Green means linked and powered, so the Cooking Table can cook from your Refined Storage network. Red means it is linked but the network has no power. A dark screen means it is not linked yet. Before, the linked-but-offline case looked identical to unlinked; now it is distinct, and Jade reports the same three states in words.
- A glowing screen. On NeoForge the display is emissive, so it stays readable in the dark: brightest when online, dimmer for the linked-but-offline warning, and off when unlinked.
- The Kitchen Access Point shows its own status the same way. Its relay fins light green when powered, red when a card is inserted but the network is not running, and stay dark when off, with the inserted card visible in the slot.
Changed
- New models and textures for all three. A retro desktop-computer Kitchen Station with a tilted screen, a finned relay-node Kitchen Access Point, and a redesigned Kitchen Network Card whose green tip matches the card chunk shown in the Access Point.
- The Kitchen Station and Kitchen Access Point items show their powered look in your inventory, hotbar, and tooltips.
- Rebuilt the Kitchen Station's hitbox to fit the new model.
- Updated the guide's "Reading the Screen" page and the in-book block previews for the new looks.
- Restyled the guide book with a new book texture and item icon.
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:AOuwe9He:GcqfCBr0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AOuwe9He:GcqfCBr0"
}







