Back to mods
Create: Recipe Hooks project artwork

CurseForge · Minecraft mod

Create: Recipe Hooks

Create library for recipe-based mods/addons/scripts etc...

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which Create: Recipe Hooks release should I use?

Updated 2 months ago
Latest stable file crh-neoforge-1.2.0.jar
Game version 1.21.1
Loader NeoForge

Create: Recipe Hooks crh-neoforge-1.2.0.jar targets 1.21.1 with NeoForge. The project page does not say whether this file belongs on the client, dedicated server, or both. All 1 required mods have matching files.

Where it goes

Is Create: Recipe Hooks required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release NeoForge
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does Create: Recipe Hooks crh-neoforge-1.2.0.jar need?

crh-neoforge-1.2.0.jar. Change the file and its required mods may change too.

All 1 required mods have matching files

Install Create first. We found matching files for this game-version and loader setup. 2 come through another mod in the chain.

2 listed on this file 2 pulled in by those mods
Create Needed by Create: Recipe Hooks crh-neoforge-1.2.0.jar
required
Matching file found Matched file: Create 6.0.10 for mc1.21.1
KubeJS Optional for Create: Recipe Hooks crh-neoforge-1.2.0.jar
optional
Matching file found Matched file: KubeJS NeoForge 2101.7.2-build.377
Better Advanced Tooltips Needed by KubeJS
pulled in
Matching file found Matched file: better-advanced-tooltips-2101.1.0-build.5.jar
Rhino Needed by KubeJS
pulled in
Matching file found Matched file: Rhino 2101.2.7-build.85

2 extra mods were pulled in by other dependencies. Indented rows show who needs each one. We only count dependency files that match this setup. A file for another loader does not fill the gap.

Before you install it

Add Create: Recipe Hooks without breaking your instance.

Built for Create: Recipe Hooks crh-neoforge-1.2.0.jar. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use crh-neoforge-1.2.0.jar. It targets 1.21.1 with NeoForge; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    Install Create first. We found matching files for this game-version and loader setup. 2 come through another mod in the chain.

  3. 03

    Put it on the correct side

    The project page does not say whether this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside crh-neoforge-1.2.0.jar. It opens that exact file at the source.

About this project

What does Create: Recipe Hooks add?

Create Recipe Hooks

Create Recipe Hooks is a server-side library for Minecraft 1.20.1 (Forge and Fabric) that fires events whenever a Create machine finishes processing a recipe, and whenever a Create machine processes a world block: Drill mining, Harvester reaping, Saw felling trees. It provides a unified API so that integration mods - such as quest books, automation scripts, and analytics tools - can react to Create production without writing their own mixins.

What it does

The mod hooks into Create's machines at the bytecode level and fires three events:

  • recipeFinished - a Create machine completed a recipe (Basin, Fan, Press, Millstone, Crushing Wheels, Saw, Crafter, Deployer, Spout, Item Drain, Sand Paper, Sequenced Assembly, CEI Printer)
  • blockProcessed - a machine processed a world block: one event per block broken by a Mechanical Drill, per plant cut by a Mechanical Harvester, per lone block cut by a horizontal Mechanical Saw
  • treeCut - a Mechanical Saw felled a whole tree, with the exact log and leaf counts

Every event carries:

  • Source - which machine did the work
  • Player attribution - the UUID of the player who placed the machine (for Crushing Wheels: who threw the item, with a fallback to whoever placed the wheels for belt and hopper input). Persisted across server restarts and carried along inside moving contraptions
  • Recipe ID, item inputs and outputs, fluid outputs - for recipe events
  • Block id, block state, contraption flag, log count - for block events
  • Block position - where it happened in the world

Supported machines

Machine Source constant Event
Basin (Mixing / Compacting) BASIN recipeFinished
Crushing Wheels CRUSHING_WHEEL recipeFinished
Mechanical Saw (recipes) MECHANICAL_SAW recipeFinished
Spout (recipe and bucket filling) SPOUT_FILLING recipeFinished
Millstone MILLSTONE recipeFinished
Mechanical Press (belt and world) MECHANICAL_PRESS recipeFinished
Mechanical Crafter MECHANICAL_CRAFTER recipeFinished
Deployer DEPLOYER_BELT recipeFinished
Encased Fan (belt and world) FAN_BLASTING / FAN_HAUNTING / FAN_SPLASHING / FAN_SMOKING recipeFinished
Item Drain (recipes, buckets, potions) ITEM_DRAIN_EMPTYING recipeFinished
Sand Paper SAND_PAPER recipeFinished
Sequenced Assembly (final step) SEQUENCED_ASSEMBLY recipeFinished
CEI Printer (optional, Forge only) CEI_PRINTER recipeFinished
Mechanical Drill (stationary and contraption) MECHANICAL_DRILL blockProcessed
Mechanical Harvester (contraption) MECHANICAL_HARVESTER blockProcessed
Mechanical Saw, horizontal (stationary and contraption) MECHANICAL_SAW treeCut / blockProcessed

KubeJS scripting, no addons needed

CRH registers its own KubeJS event group. The same scripts run unchanged on Forge and Fabric, with an optional source filter and built-in owner resolution:


CRHEvents.recipeFinished('MILLSTONE', event => {
    const player = event.getOwner();
    if (!player) return;
    player.server.runCommandSilent('give ' + player.name.string + ' minecraft:emerald 1');
});

CRHEvents.treeCut('MECHANICAL_SAW', event => {
    // event.getLogCount(), event.getBlockId(), event.getOwner()
});
  

Ready-to-use script examples (FTB Quests integration, output filtering, per-player counters, drill mining quests, log counting) are available in the README.

Why you might want this

If you are building a quest integration (FTB Quests etc.), you can trigger quest progress the moment a Create machine finishes, attributed to the right player - not just when items land in an inventory. Quests like "smelt 64 iron with a Fan", "mine 500 stone with a Drill" or "fell 50 trees with a Saw" become one short script each.

If you are writing analytics or logging tools for a server, you get a single reliable event stream for all Create production.

This mod does nothing visible on its own. It is a library - you will not see any in-game UI, items, or blocks. Install it when another mod or script requires it. It is server-side: clients without the mod can join a server that has it. For singleplayer, install it in your instance.

Requirements

  • Minecraft 1.20.1
  • Forge file: Forge 47 or newer, Create 6.0.8 or newer. Also runs on NeoForge 1.20.1, verified on clients and dedicated servers
  • Fabric file: Fabric Loader 0.15+, Fabric API, Create Fabric 6.0.8.1 or newer. Works on Quilt
  • KubeJS - optional, only for JS scripting (no EventJS or other addons required)
  • Create Enchantment Industry - optional soft dependency on Forge; CEI Printer events are only fired when CEI is installed

For developers

Register listeners during mod initialization, identical on both loaders:


CreateRecipeHooks.register(ctx -> {
    if (ctx.getSource() == RecipeSource.BASIN) {
        // ctx.getRecipeId(), ctx.getItemOutputs(), ctx.getBlockPos(), ...
    }
});

CreateRecipeHooks.registerBlockProcessed(ctx -> {
    // ctx.getBlockId(), ctx.isContraption(), ctx.getMetadata()
});

CreateRecipeHooks.registerTreeCut(ctx -> {
    // ctx.getLogCount(), ctx.getLeafCount()
});
  

On Forge the events are also posted on the event bus (CreateRecipeFinishedEvent, CreateBlockProcessedEvent, CreateTreeCutEvent); on Fabric they are standard callbacks (CreateRecipeFinishedCallback, CreateBlockProcessedCallback, CreateTreeCutCallback).

A debug mode is available for testing on Forge. Launch with the JVM argument -Dcrh.debug=true to write every recipe completion to logs/crh-events.log.

Full API documentation is available in the per-loader READMEs on the GitHub repository.

License

LGPL-3.0-or-later - free to use in public and private modpacks and as a dependency in other mods. Forks and derivative mods must remain open source under the same license with attribution.

Project description from CurseForge.

Pick your setup

Create: Recipe Hooks by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

5 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

Create: Recipe Hooks versions and loaders

3 of 3 releases match

Looking for an older file? The official CurseForge project page is in Resources.