Tags
Creators
Details
All versions
1.5.1-26.2-(NeoForge)
Release
1.5.1-26.2-(NeoForge)6 days ago 7
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
1.5.1-26.2-(NeoForge)
Custom Recipe — Minecraft 26.2 (NeoForge)
This update makes configurations easier to share, improves the recipe editor, and lets servers keep custom recipes active for players who do not install the mod.
Added
- Two export formats — export a complete Custom Recipe share file for lossless backup and transfer, or create a standard Minecraft datapack for supported recipes.
- Customizable datapack export — choose the datapack name, description, and target Minecraft version before saving. The export includes its credit and licence information.
- The datapack preview reports how many recipes can be exported and clearly identifies recipes that must be skipped because vanilla datapacks cannot represent them.
Improved
- Shaped and shapeless recipe quantity controls use the free space beside the crafting preview, leaving more room for the item list.
- Shapeless recipes show up to four ingredient rows at once and keep the remaining entries accessible by scrolling.
- Alternative groups display their number of choices in recipe slots, saved groups, and while the complete group is carried by the cursor.
- Exported share files use clearer default filenames based on the selected world or library.
Fixed
- Confirmation and import/export windows fully block hover effects and visual elements from the menu behind them.
- Shaped/Shapeless and Known by default controls now show their highlighted and selected states consistently.
- Carried items, carried alternative counts, delete markers, and quantity labels keep the correct drawing order above placed recipe items.
- Opening editor and configuration screens no longer triggers duplicate background blur on affected Minecraft versions.
Compatibility / servers
- Supports Minecraft 26.2 with NeoForge.
- No additional library mod is required. Roughly Enough Items (REI) remains optional.
- A dedicated server can keep previously configured custom recipes active for vanilla clients that do not install Custom Recipe. Install the mod on a client only when that player needs the graphical editor.
- Recipes using features that vanilla datapacks cannot represent remain available through the Custom Recipe share format and are skipped with an explanation during datapack export.
Before updating
- Existing recipes and configurations remain compatible.
- No migration or additional setup is required after updating.
Optional dependencies
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:nGLLzNcJ:BJ0mTDV9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nGLLzNcJ:BJ0mTDV9"
}

