Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 6 days ago
All versions
1.2.0
Release
Rustic Pancakes 1.2.0last week 26
Compatibility
Minecraft: Java Edition
1.21.6
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Additions
- Rustic Pancakes now runs on both Fabric and NeoForge. Fabric gets everything from 1.1.0 as well: Pancakes, Pumpkin Pancakes, Syrup and single pancakes
- Pancakes can be put back onto a placed stack by sneaking and right-clicking with a matching pancake, up to 12 high
- Added particles when taking a pancake from a placed stack
- Added advancements: Batter Up!, A Taste of Sweetness and Fresh Off the Griddle
- Added Spanish (Argentina), Spanish (Chile), Kazakh, Korean, Russian and Ukrainian translations, carried over from Rustic Delight (thank you ex0planet, vlaster666, ninsent, TAILS, MaxKuz67, JedaiGames and hikarosato!)
- Added translations for the mod's item and block tags, which recipe viewers such as JEI show
- Ported to Minecraft 1.21.6
Changes
- Now requires Architectury API
- You no longer need shears to get a single pancake: right-clicking a placed stack now puts a pancake straight into your inventory, instead of eating it
- Breaking a placed stack now drops the pancakes that are left on it, along with the bowl
- Improved the Cherry Blossom Pancakes textures
- Pancake stacks now show the italicized "Placeable" tooltip
Fixes
- Fixed the topping floating above a full stack of Chocolate or Vegetable Pancakes
- Fixed a malformed Japanese translation file, and the creative tab being called Rustic Delight in Japanese
- Eating Batter now gives its bowl back, as drinking Syrup gives back its bottle
- Comparators beside a placed stack now read how many pancakes are left on it; a full plate used to read 0
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:coJ1i4xo:5UBrlq8X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:coJ1i4xo:5UBrlq8X"
}

