All versions
1.2.1+1.20.1
Release
Create: Recipe Extensions 1.2.1+1.20.12 months ago 15
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
1.2.1+1.20.1
Added
Recipes
- Added Veridium Mixing recipe: combines 3 Clay Balls, 1 Flint, and 250 mB of Lava in a Mixing basin (no heat required) to produce 1 Veridium.
- Added Asurine Mixing recipe: combines 3 Clay Balls, 1 Flint, and 500 mB of Water in a Mixing basin (no heat required) to produce 1 Asurine.
Integrations
- Added Create: Vibrant Vaults integration. When this mod is installed, a Deployer holding a Wrench can convert Item Vaults into their vertical variants. Supports all 16 dye-colored vaults from Create: Vibrant Vaults as well as the base Create Item Vault, which converts to the uncolored vertical variant. This adds 17 deployer recipes in total.
Configuration
- Added
enableVerdiumMixingRecipeconfig toggle (default:true). - Added
enableAsurineMixingRecipeconfig toggle (default:true). - Added
enableVibrantVaultDeployingRecipeconfig toggle (default:true). Has no effect when Create: Vibrant Vaults is not installed. - Added corresponding lang entries for all three new config options.
Removed
- Removed Charcoal Milling recipe and its
enableCharcoalMillingRecipeconfig toggle.
Notes
- The Vibrant Vaults deployer recipes are conditional - they only load when Create: Vibrant Vaults is present. No config change is needed when the mod is absent.
- This release brings the total recipe count from 6 to 8, plus 17 conditional integration recipes.
Optional dependencies
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:713oqOhn:QqGpwRfV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:713oqOhn:QqGpwRfV"
}




