Tags
Creators
Details
1.1.0
Compatibility
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
This update adds a complete template system overhaul for the vanilla Crafter, with slot-based template logic, x1/x64 slot limits, smarter automation handling, expected recipe result protection, and multiple UI and interaction improvements.
Fixed
- Fixed template insertion stacking identical items into the first compatible slot
- Fixed repeated ingredient handling inside crafting patterns
- Fixed disabled template slots being accidentally re-enabled by interactions
- Fixed multiple insertion edge cases with manual insertion, shift-click, and automation
- Fixed template synchronization and persistence issues
- Fixed recipe ambiguity problems with intermediate recipes such as Iron Bars, Iron Nuggets, and Glass Panes
- Fixed incorrect crafts being triggered before the full template was completed
Added
- Added slot-based template handling
- Added
x1andx64slot limit modes - Added expected recipe result saving
- Added an expected output protection system
- Added ghost result preview support
- Added smarter automation compatibility for storage systems and hoppers
- Added transparent UI buttons integrated directly into the Crafter screen
- Added translatable tooltips for template controls
Improved
- Improved template reliability for automation workflows
- Improved compatibility with recipes using repeated ingredients
- Improved Crafter interaction behavior
- Improved template persistence and synchronization
- Improved overall UX and visual integration with the vanilla Crafter
Notes
- Templates now validate both the crafting pattern and the expected crafting result
- Each Crafter stores its own independent template and slot limit mode
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:d3eqiji1:4BYzxJDe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d3eqiji1:4BYzxJDe"
}

