Tags
Creators
Details
1.12.4-r.3+mc26.2
Compatibility
Required content
Changes
KNOWN ISSUE
C2ME can cause item migration to be skipped when updating Matcha without changing your Minecraft version. This affects items stored in chests and other containers in the world, including shulker boxes inside them. The MC 26.3 release is also affected. (#24)
Please back up your world and temporarily remove C2ME before updating.
If you had C2ME installed during earlier updates, some previous migrations for items stored in world containers may also have been skipped. Removing C2ME will not restore items that have already disappeared 😔 recovering those requires a backup.
BREAKING CHANGE
- Item ID changes:
matcha:divine_fragment→matcha:pithminecraft:blaze_rod→matcha:stabilized_estusminecraft:blaze_powder→matcha:raw_estusmatcha:chocolate_chip_cookie→minecraft:cookie- Volatile Flasks now use
minecraft:splash_potion.
- Don’t worry — existing mod saves are migrated automatically.
New Features
- Farmer’s Delight compatibility:
- Cleavers can now be used on cutting boards.
- With FD installed, seed bundles sold by farmers can randomly contain beetroot seeds.
- Renamed FD’s Straw and Straw Bale to avoid duplicate names.
- Added a setting that allows blazes to drop additional blaze rods.
- Disabled by default, takes effect immediately, and requires operator permissions.
- Vanilla blaze rods and blaze powder are now separate from Estus items. This option supports crafting compatibility with third-party mods.
- Restored the blaze powder crafting recipe.
Bug Fixes
- Fixed Naan being unobtainable with FD installed.
- Fixed FD Stove recipes being identical to Matcha Oven recipes.
- Corrected leftover upstream carrier item references in loot tables and recipe unlock conditions.
Note
- The internal data migration schema version is now v8.
Optional dependencies
Known incompatibilities
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:9LKX5H57:fuxKeUFm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9LKX5H57:fuxKeUFm"
}

