Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated 2 months ago
All versions
3.0.0
Release
Emaki Cooking 3.0.06 months ago 75
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Spigot
Required content
Unavailable version
Changes
EmakiCooking 3.0.0 Release
This release adds three new cooking stations (Oven, Juicer, Fermentation Barrel), a virtual display entity system, and heat source ignition, significantly expanding cooking gameplay.
New Features
- Oven: Temperature-sensitive cooking station. Players control heat by adding fuel; supports perfect bake, normal bake, and burnt results based on temperature management.
- Juicer: Press-based cooking station. Players press multiple times to extract fluid (measured in ml), then collect with a container. Supports fluid mode and direct output mode.
- Fermentation Barrel: Long-duration fermentation station. Supports early collection (partial product), normal completion, and over-fermentation (spoiled product). Progress persists across server restarts.
- Display Entity System: Cooking stations show floating item display entities above them. Three backends:
auto,packet_events(virtual entities, no entity ID usage, better performance),bukkit(real ItemDisplay). Configurable view distance and refresh interval. - Heat Source Ignition: Wok and steamer support
ignite_heat_sourceto automatically light/extinguish heat source blocks when ingredients are added/removed. Works with CraftEngine, ItemsAdder, and Nexo custom blocks. - PAPI Placeholders:
%emakicooking_recipe_count%(total recipes) and%emakicooking_recipe_count_<station>%(per-station count).
Improvements
- Config and language files auto-merge new keys on upgrade.
- Fermentation barrel state uses dirty-flag batch persistence to reduce disk IO.
- All stations auto-drop contents when the block is broken.
Breaking Changes
- Station block sources changed from single
block_sourceto listblock_item_sources. - Tool/spatula/heat source fields unified to
*_item_sourceslist format. - Steamer moisture rules renamed from
moisture_sourcestomoisture_ruleswith updated sub-fields. - All recipe
input.source→input.item_sources(list),result.output.source→result.output.item_sources(list). - Old built-in recipes removed; each station directory now has
example_recipe.yml.
Upgrade Notes
- New station GUI templates and recipe directories are auto-created.
- PacketEvents display backend requires Minecraft 1.19.4+; auto-falls back to Bukkit on older versions.
- Config version updated to
4.0.0with new station anddisplay_entitiesconfiguration sections. - Existing recipes must migrate
sourcefields toitem_sourceslist format — refer to each station'sexample_recipe.yml.
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:zOenBPfQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NlpcnczH:zOenBPfQ"
}

