Skip to content

Configuring Recipe Logic ​

MBD2 21.1.1

Recipe logic connects one machine definition to one MBDRecipeType. It searches only when the machine has compatible handler proxies for recipe content.

MBD2 Recipes view showing a recipe type, example recipe, and Fuel Recipe Config in Inspector
Recipe logic points at a registered recipe type; its fuel configuration and viewer visibility belong to that type.

Settings ​

SettingRuntime value keyEffect
Enablerecipe_logic.enableWhether recipe logic runs at all
Recipe type—The registry ID this machine searches
Recipe damping valuerecipe_logic.dampingProgress lost per waiting tick, floored at zero. 0 freezes progress while waiting
Consume inputs after workingrecipe_logic.consume_inputs_after_workingDefer normal input consumption to completion. Every working tick re-simulates the inputs, and losing them interrupts the recipe
Always search reciperecipe_logic.always_searchForce a fresh recipe-type search after each completed recipe instead of reusing the cached one
Always modify reciperecipe_logic.always_modifyRe-apply modifiers every cycle. Needed when tier, upgrades or machine data can change the effective recipe between runs
Recipe modifiers—Amount, duration and parallel transformations applied to the matched recipe

Every keyed setting is also a runtime value, so a blueprint, a script or a UI can change it for one placed machine without touching the definition.

Wiring checklist ​

  1. Register or export the recipe type before the machine definition is resolved.
  2. Select its exact namespaced ID.
  3. Add at least one handler trait for every capability used by candidate recipes.
  4. Set handler IO for each recipe direction.
  5. Test normal and per-tick content separately.
  6. Add waiting and working states if the visuals should reflect status.
  7. Test recipe-viewer lookup from the generated UI.

Conditions are evaluated again while working. A recipe may wait when weather, redstone, rotation, heat, pressure or another condition changes; waiting is not the same as resetting, and how much progress waiting costs is the damping value.

See Recipe lifecycle for the execution model, and Blueprints for rewriting a matched recipe rather than only scaling it.

Released under the MIT License.