Links
Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated 2 months ago
All versions
1.3.0
Release
ConvenientCrafting 1.3.04 months ago 18
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
1.3.0
Added
- Added brewing stand recipe support in the convenient crafting panel.
- Added vanilla brewing batch behavior: one brewing ingredient can process up to three matching input potions into up to three result potions.
- Added
enabledBuiltinRecipeTypesconfig so modpack users can choose which vanilla workstation recipe types are available in convenient crafting. - Added Shift-click batch crafting for the convenient crafting
>button. - Added the standard button click sound when pressing the convenient crafting
>button. - Added Alt-click nested crafting for the convenient crafting
>button, including a preflight raw-material check and a scrollable tree-style missing-material popup. - Added item name tooltips when hovering required ingredients in the convenient crafting recipe list.
- Added item tooltips when hovering recipe result icons in the convenient crafting recipe list.
Changed
- Vanilla crafting, smithing, and brewing recipe types are enabled by default through config.
- Server-to-client recipe unlock syncing now includes enabled built-in recipe types so multiplayer clients follow the server config.
- Convenient crafting panel now keeps its original default size on normal windows and shrinks only when needed to fit smaller game windows.
- Convenient crafting panel layout is now more compact, with tighter recipe rows and page-aligned adaptive ingredient columns.
Fixed
- Fixed the Convenient Crafting creative mode tab icon showing as a missing-texture block by using a vanilla crafting table icon until custom mod items are added.
- Removed unused template example items from creative tab display to avoid missing-model entries in creative search.
- Added localized names and tooltips for the in-game NeoForge configuration screen, and removed unused template demo config entries.
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:dDkmGsRk:RWPx76Et"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dDkmGsRk:RWPx76Et"
}

