Links
Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 weeks ago
All versions
5.0.0
Release
5.0.03 weeks ago 6
Compatibility
Minecraft: Java Edition
1.20.4
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Changelog
All notable changes to Applied Cooking are listed here.
5.0.0
First NeoForge 1.20.4 release, ported from Forge 1.20.1.
Added
- Fluids from your ME network. The Kitchen Station can now satisfy recipes that need water and milk by draining them straight from network storage (matched by tag, like a Sink or Milk Jar), with a network-driven fallback for other fluids such as lava.
- Network power draw. While connected, the Station uses a small amount of power from the linked network. If the network can't spare it, the Station goes offline until power returns. The draw is shown in Jade and The One Probe.
- JEI info page for the ME Kitchen Station, explaining how to link and use it.
- 10 translations: German, Spanish, French, Italian, Korean, Brazilian Portuguese, Russian, Swedish, and Simplified & Traditional Chinese.
Changed
- Rewrote the in-game guide for current AE2: you now link the Station at a Wireless Access Point's GUI (the old ME Security Terminal is gone). Added a rotatable 3D multiblock preview and a dedicated "Reading the Screen" page, and localized the whole guide.
- Made the connected/disconnected screen and the Jade/TOP tooltips reliable, and lightened the Station's per-tick network work.
- Applied Cooking now depends on Balm directly. Jade, The One Probe, JEI, and Patchouli are all optional — the mod runs fine without any of them.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible 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:BmMjyidG:2RJFvY0R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BmMjyidG:2RJFvY0R"
}

