All versions
1.4.0
Release
1.20.1-1.4.0last week 1,842
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Added:
- Added the Wither Pepper and Wild Wither Pepper.
- Added the Copper Latiao and Enchanted Copper Latiao.
- Added the Block of Wheat Flour and all Blocks of Pepper Powder.
- Added some decorative blocks of Hotaurum.
- Added the Hotaurum Door and Hotaurum Trapdoor.
- Added a new craft recipe for the Block of Unprocessed Latiao.
- Added some festival surprise content.
Fixed:
- Fixed the issue where Unprocessed Latiao Club were missing the
ltc2:latiaotag. - Fixed the issue where the Fouroseven Latiao Club could not be enhanced properly under certain circumstances.
- Fixed the issue where weapon config files could not be worked correctly.
- Fixed the issue where the
ltc2:uncleanablestatus effect tag did not work as intended. - Fixed the issue where the requirements for the "Forged by A Hundred Eating" advancement were incorrect.
Changed
- Hotaurum blocks are no longer destroyed by lava or fire.
- The Extra Spice Event now supports more flexible custom configuration.
- Optimized the item movement logic in the Latiao Oven GUI.
Support:
- Immortalers Delight
- Added the Hotaurum Kwat Toast and Hotaurum Kwat Toast Slice
- Added the Gelpitaya Lime Pudding.
- Added the DRAKE SPRING.
- Added the A'B'Pepper MoC'ha.
- Added the Underground Oil Fizz.
- HUAJI Age: Astral Regenesis
- Fixed the issue where SHINY STAR Huaji Latiao were missing the
ltc2:flavourable_latiaotag. - Added the
ltc2:cannot_flavour_with_saltandltc2:cannot_flavour_with_sugaritem tags to all Huaji Latiao.
- Fixed the issue where SHINY STAR Huaji Latiao were missing the
- Crock Pot
- Added the Food Type for the Bittterheart Root.
- Jade
- Latiao Oven now displays additional information with Jade.
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:70eF0Jga:AehRsLkq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:70eF0Jga:AehRsLkq"
}

