Custom ingredient kinds
Implement Hooks::ingredient(context, event) to resolve recipe ingredient types outside the minecraft: namespace. Fill event.items with the item IDs your ingredient accepts. The loader removes duplicates in first-seen order.
This list supplies recipe-book placement candidates. Use the match-time hook to check a concrete stack. A nonempty candidate list filters matching by item on every matching path, including shaped, shapeless and non-simple shapeless matching, before the stack test runs. The list must therefore contain every item the test should accept; the test can only narrow it. An empty custom list retains the predicate without this filter, so the stack test can accept items outside the list. Everything that reads the list (recipe book, placement, recipe property sets, vanilla clients) sees only the list.
Load contract
- The hook receives the owning load's
DataLoadContext. - Each occurrence is dispatched once per load, including nested ingredients and ingredients in any recipe slot.
- Dispatch occurs before the load's tables parse recipes. Server tables, stations and copies sent to guests share that load.
- The client's recipe preload reports
ClientPreloadthroughorigin(); the server's recipe load reportsServerDataLoad, including on a dedicated server. /reloaddispatches the occurrences again. A client joining a remote server does not receiveServerDataLoad.- Return a consistent answer for the same input. If no mod listens to the
ingredienthook, a recipe file naming a custom kind fails whole at load with an error naming the file and the kind, and the recipe is absent everywhere. If a mod listens but leaves the list empty, the recipe and its match-time predicate are retained, with a warning naming the file and the kind that the recipe cannot be placed. It is excluded from recipe-book learning/displays, recipe property sets and stonecutter selections; the server also refuses recipe-book placement. The effective recipe map and manual matcher still retain it. - An existing empty item tag likewise retains an unplaceable recipe, but never matches a stack. An undefined tag fails the recipe with an error. A direct empty list (
[]) remains invalid and fails the recipe with an error.
Ingredient data
Read event.data as an API Compound, using typed Tag variants such as Int, Long, List and Compound, not JSON accessors.
The loader converts recipe metadata once using vanilla JsonOps-to-NbtOps rules. JSON true and false become Byte 1 and 0, so the hook cannot tell a bool from the number 1 or 0. A number that is an exact signed 64-bit integer, including a decimal such as 1.0 or 1e3 and -0.0, becomes the smallest of Byte, Short, Int and Long that holds it (1 is a Byte, 300 a Short, 100000 an Int). Any other number becomes a Float if it survives a round trip through f32 (0.5), otherwise a Double (0.1). Because the width depends on the value, read numeric tags by value, accepting any numeric variant, rather than matching one tag type. Numeric JSON arrays remain lists. Nested null values refuse the ingredient and fail the recipe. The match-time hook receives the same retained compound without reconversion.