> For the complete documentation index, see [llms.txt](https://developers.wiki.resourcefulbees.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.wiki.resourcefulbees.com/recipes/centrifuge.md). # Centrifuge Schema reconstructed from `CentrifugeRecipe`, its item/fluid output codecs, ResourcefulLib `WeightedCollection`, Minecraft `Ingredient` and `ItemStackTemplate`, and NeoForge `FluidStackTemplate`. ## Example ```json { "type": "resourcefulbees:centrifuge", "ingredient": "resourcefulbees:iron_honeycomb", "inputAmount": 1, "itemOutputs": [ { "chance": 0.8, "pool": [ { "item": { "id": "minecraft:raw_iron", "count": 3 }, "weight": 25 }, { "item": "minecraft:raw_iron", "weight": 50 } ] } ], "fluidOutputs": [ { "chance": 1.0, "pool": [ { "fluid": { "id": "resourcefulbees:honey_fluid_source", "amount": 100 }, "weight": 1 } ] } ], "time": 200, "energyPerTick": 10 } ``` ## Fields | Field | Type | Required | Default | Description | | --------------- | --------------------------- | -------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `type` | string | Yes | `resourcefulbees:centrifuge` | Recipe serializer identifier. | | `ingredient` | Minecraft Ingredient | Yes | — | Item ingredient tested against the centrifuge input stack. Simple Resourceful Bees recipes use a direct item ID; Minecraft/NeoForge ingredient objects remain codec-driven. | | `inputAmount` | positive integer | No | `1` | Required stack count for the recipe match and the number of input items consumed when the recipe completes. Must be at least `1`. | | `itemOutputs` | array of item output rolls | No | `[]` | Independent item-output rolls. Up to the first `3` entries are evaluated when producing recipe results; later entries are ignored. At least one of `itemOutputs` or `fluidOutputs` must be non-empty. | | `fluidOutputs` | array of fluid output rolls | No | `[]` | Independent fluid-output rolls. Up to the first `3` entries are evaluated when producing recipe results; later entries are ignored. At least one of `itemOutputs` or `fluidOutputs` must be non-empty. | | `time` | positive integer | No | configured default (`200` initially) | Recipe processing time. Must be at least `1`; the default comes from `CentrifugeConfig.defaultCentrifugeRecipeTime`. | | `energyPerTick` | positive integer | No | configured default (`10` initially) | Energy consumed per processing tick. Must be at least `1`; the default comes from `CentrifugeConfig.centrifugeRfPerTick`. | | `rotations` | positive integer | No | derived from `time` | Optional explicit rotation count. Must be at least `1` when supplied. If omitted, runtime computes `((time / 20) / 8) * 2` using integer division. | ## Output rolls Each entry in `itemOutputs` or `fluidOutputs` is an independent roll: | Field | Type | Required | Default | Description | | -------- | ------ | -------- | ------- | -------------------------------------------------------------------------------------------------------------------------------- | | `chance` | number | No | `1.0` | Probability that this output roll occurs. Range `0.0` through `1.0`, inclusive. | | `pool` | array | No | `[]` | Weighted collection from which one result is selected when the roll succeeds. In practical recipes, provide at least one result. | `itemOutputs` and `fluidOutputs` are individually optional and each defaults to an empty list, but a centrifuge recipe cannot have both lists empty. The recipe validation safeguard throws an exception when both output lists are empty, so every recipe must define at least one item-output roll or at least one fluid-output roll. The centrifuge evaluates **at most three item-output rolls and three fluid-output rolls** when producing a recipe result. Only the first three entries of each top-level output list are considered; entries after index `2` do not participate in result generation. This matches the three item and three fluid output slots represented by the JEI centrifuge category. Within those evaluated entries, multiple output rolls can succeed during the same recipe completion. `chance` controls whether a roll occurs; `weight` only controls which member of that roll's `pool` is selected. The three-entry limit applies to the top-level `itemOutputs` and `fluidOutputs` lists, not to the number of weighted choices inside an individual `pool`. ### Item pool entries | Field | Type | Required | Default | Description | | -------- | ----------------- | -------- | ------- | ---------------------------------------------------------------------------- | | `item` | ItemStackTemplate | Yes | — | Item result, using the compact item ID or expanded item-stack-template form. | | `weight` | number | No | `1.0` | Relative selection weight. Range `1.0` through `1000.0`, inclusive. | ### Fluid pool entries | Field | Type | Required | Default | Description | | -------- | ------------------ | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `fluid` | FluidStackTemplate | Yes | — | Fluid result. A compact non-empty fluid ID or expanded `{id, amount, components}` form is accepted by the underlying template codec. | | `weight` | number | No | `1.0` | Relative selection weight. Minimum `1.0`; the codec's upper bound is `Double.MAX_VALUE`. | ## Runtime notes The recipe matches only when `ingredient.test(input)` succeeds **and** the input stack's count is exactly equal to `inputAmount`. When the recipe completes, the centrifuge consumes `inputAmount` items from the input stack. Although the two output fields are optional at the field level, a recipe with no item outputs and no fluid outputs is invalid. If both lists resolve to empty, recipe validation throws an exception instead of accepting a recipe that can never produce an output. When generating outputs, the item-output and fluid-output streams are each limited to their first three entries. Defining more than three entries in either list does not create additional results; the extra entries are ignored by result generation. Each successful output roll calls into its weighted pool to choose one result. Although an omitted `pool` codec-decodes to an empty weighted collection, an empty pool cannot provide a random result at runtime. Treat a non-empty pool as practically required for every output roll that can succeed. The current manual centrifuge uses `rotations` when supplied. Otherwise, rotations are derived from `time` with integer division. With the stock `time` default of `200`, the derived value is `2` rotations. `inputAmount`, `time`, `energyPerTick`, and an explicitly supplied `rotations` value use `ExtraCodecs.POSITIVE_INT`, so values below `1` are rejected by the recipe codec. `rotations` remains optional; when omitted, its value is derived from `time` at runtime. ## Ingredient codec scope `ingredient` is delegated directly to Minecraft's `Ingredient.CODEC`. The schema intentionally models the common direct item/tag forms and leaves custom ingredient objects extensible rather than guessing every Minecraft/NeoForge ingredient subtype. If stricter completion for the exact Minecraft version is desired, the external `Ingredient.CODEC` definitions can be incorporated separately. ## Schema and template The source files used for this page are included in the `reference/` directory: * `resourcefulbees-centrifuge-recipe-template.json` * `resourcefulbees-centrifuge-recipe.schema.json` > The schema is the machine-readable reference. Runtime notes document codec or game behavior that JSON Schema cannot fully express.