Tags
Creators
Details
4.16.8.2
Compatibility
Required content
Changes
Changes since 4.16.8.0
Armor Trim Merge Adapter
The new Armor Trim merge adapter makes it possible to copy armor trim patterns and materials from ingredients to the result stack. It provides some further options to customize its behaviour.
Examples
Copies the pattern and changes the material to amethyst.
{
key = "customcrafting:armor_trim"
copyPattern = true
copyMaterial = false
defaultMaterial = "minecraft:amethyst"
}
Copies the pattern from the ingredient in slot 1 and the material from slot 2.
{
key = "customcrafting:armor_trim"
copyPattern = [ 1 ]
copyMaterial = [ 2 ]
}
Copies both the pattern and material.
{
key = "customcrafting:armor_trim"
copyPattern = true
copyMaterial = true
}
Changelog
- #300 - Add Exlude Option to Lore, Book & Banner Merge Adapter
- #303 - Add Armor Trim Merge Adapter
- #306 - Add Preserve Trim Option to Smithing Recipe
- #309 - Add Config Option to toggle vanilla cooking recipe fallback check
- #295 - Fix Error on interactions in Recipe Lookup Menu
- #297 - Fix Recipe Book Editor Error in 'Add Category/Filter' Menu
- #299 - Fix Invalid Cooking Recipe Result
- #301 - Fix Inability to save Smithing Recipes on pre-1.19.4 servers
- #302 - Fix Invalid Match Result of the Elite Crafting Table Condition
- #304 - Fix Empty Base/Addition Ingredient causing Anvil Recipe to not load
- #298 - Fix Campfire Interaction with Buckets, Flint and Steel, and more
- #305 - Fix duplicate recipe list entry for disabled recipes
- #307 - Fix NullPointerException in Recipe Condition
- #308 - Update & Fix Elite Crafting Table Condition Settings
- #310 - Fix Anvil Recipes ignoring hidden recipes & not checking conditions
- #311 - Fix recipe priority for various recipe types
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:qmTmOySQ:pG3wT2eN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qmTmOySQ:pG3wT2eN"
}

