Easy Custom Craft A Minecraft Forge 1.20.1 mod that lets admins create their own recipes in-game — no files, no JSON. Recipes are stored per world/server and applied instantly.
Features
Crafting table – shaped & shapeless (commands + 3×3 GUI)
Cooking – furnace, blast furnace, smoker, campfire (xp + time)
Smithing table & stonecutter
Tags – use tag:… ingredients anywhere + create your own tags
Any modded machine (Create, Mekanism, Thermal…) – scans every recipe type, detects its options, with command auto-complete, multiple inputs and fluids — all without JSON
NBT results and modded items supported
Commands (/ecc)
Public: list, preview
Syntax Meaning minecraft:stick / stick item (namespace defaults to minecraft) tag:ns:path item tag → {"tag":"…"} empty / air blank crafting cell (shaped only) Result positions take a concrete item (via the vanilla item argument, so NBT like minecraft:diamond_sword{…} works). In modded_craft only, key=value values additionally accept: fluid:ns:path[:amount] (default amount 1000), true/false, numbers, plain strings, and comma lists a,b,c (→ JSON array).
Recipe names are sanitized to [a-z0-9/._-] (other chars → _).
Crafting table
shaped
Stations & default cook time: furnace 200, blastfurnace 100, smoker 100, campfire 600 ticks.
experience default 0.0. Result supports count + NBT (Forge object result).
Smithing & stonecutting
smithing
Modded recipes (modded_craft) Discovery
types with no filter → one line per mod with a type count.
types
Picks a template recipe of the type, preferring one in the type's own namespace and without conditions. Strips conditions (so your recipe never inherits a forge:mod_loaded dependency on another mod). Replaces item inputs with your list (fluid inputs from the template are kept); replaces the first item output with yours (secondary/fluid outputs kept). Applies each key=value override onto the JSON (any top-level field; lists via commas). Validates with the mod's own RecipeSerializer — invalid recipes are rejected with the mod's error, never written. Writes + reloads, then reports the options kept from the example (e.g. heatRequirement=heated) so you can override them. Scope & limits
Best for 1→N item machines plus scalar/enum options; Create mixing-style recipes typically need ≥2 inputs or heat.
Schemas are learned from loaded recipes only (Forge 1.20.1 serializers are not introspectable), so a field never used by any installed recipe won't be suggested — but you can still type any key=value manually.
The full type schema is built in one pass over all recipes and cached (first types/tab may take a moment); string fields with >16 distinct values are treated as free-form.
Storage & runtime
Each recipe is a data-pack file in
No gallery available for this project.