Tags
Creators
Details
3.1.0
Compatibility
Required content
Changes
EmakiCooking v3.1.0
Workstation text displays, wok stir-fry animation, configurable effects, and Web console support.
✨ New Features
Workstation Text Display
Cooking stations now support floating text displays above them, providing clear visual feedback on the current processing status. Choose between Bukkit and PacketEvents display backends depending on your server setup.
Wok Stir-fry Animation
The wok station now features a stir-fry animation effect, adding visual flair to the cooking process.
Station Effect System
A new configurable particle and sound effect system lets you add custom visual and audio feedback during station operation.
Cooking Animation Improvements
Cooking animations have been optimized to support arbitrary rotation angles, removing the previous fixed-direction limitation.
Recipe Completion Conditions
Cooking recipes now support the core library's recipe completion condition system, enabling post-completion logic and actions.
Web Console Integration
EmakiCooking is now accessible through the built-in Web management console, allowing you to edit recipes and configurations directly in your browser.
🐛 Bug Fixes
- Fixed ingredient source resolution during recipe matching, which could cause incorrect ingredient consumption.
- Fixed wok failure output using incorrect item source format.
♻️ Improvements
- All station GUI interfaces have been optimized and updated.
- Example recipe files have been improved for better clarity and ease of use.
- Language files have been significantly expanded with translations for all new features.
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:NlpcnczH:ET09c0oE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NlpcnczH:ET09c0oE"
}

