Links
Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated yesterday
All versions
1.3.0
Beta
Create: Extra Recipes 1.3.0last week 16
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Create: Extra Recipes — v1.3.0
New
- Automatic recipe patching system for armor trim templates: any duplication recipe for a trim template (
*_armor_trim_smithing_template) is now dynamically detected and has its cost inverted (1 precious material + 7 base material, instead of 7+1), regardless of which mod adds it. Works natively with already-installed third-party mods (More Armor Trims, Supplementaries, Alex's Caves) and with any future trim mod, no configuration needed. - New recipe: Compacted Obsidian (9x Powdered Obsidian → 1 Obsidian).
- New recipe: Witness armor trim template (compatible with More Armor Trims + Vanilla Backport).
- Change Create recipes: Gearbox and Vertical Gearbox now give 2 instead of 1.
Fixes
- Major fix: vanilla armor trim templates were no longer being nerfed due to a recent NeoForge patch (recipes were silently replaced with tag-based versions, bypassing our overrides).
- Fix: double-nerf on Supplementaries — the Blast template was incorrectly reverting to the vanilla cost due to a leftover legacy override file conflicting with the new dynamic system.
- Netherite Ingot nerf: reduced netherite scrap drop chance on Nether Bricks crushing (0.05 → 0.01).
Technical
pack_formatupdated: 47 → 48 (1.21.1 compliance).- Loosened Create dependency range for better modpack compatibility:
[6.0.9,6.1.0)→[6.0.0,). - Cleanup: removed all legacy static JSON override files (vanilla + third-party templates), replaced by dynamic detection.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:uUsD8Drs:gRQ20i8y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uUsD8Drs:gRQ20i8y"
}

