Preferred outputs
How a recipe that outputs a tag picks one item, and how to change which mod wins.
Many Enthalpy recipes output a tag instead of one item: grinding tin ore gives "a tin dust", not a particular mod's tin dust. When a machine finishes, it must hand over one real item. The server config decides which, and a pack can change the order.
A worked example#
A pack has Mekanism and All The Ores. Both add a tin dust, so the tag c:dusts/tin holds two
items, alltheores:tin_dust and mekanism:dust_tin. The Triturator's tin recipe
outputs the tag. With the default order, All The Ores comes before Mekanism, so every ground tin ore gives
the All The Ores dust.
To get Mekanism's dust instead, move mekanism ahead of alltheores:
[outputs]
preferredMods = ["minecraft", "mekanism", "alltheores", "immersiveengineering"]Nothing else changes: the same recipe now gives mekanism:dust_tin. It applies to the next
item a machine makes, and to every other tag output in the mod.
The rule#
For a tag output, Enthalpy takes the items in the tag, sorted by their full IDs, and picks the first that fits one of these, in order:
- The first mod in
preferredModsthat has an item in the tag. Within one mod, the item whose ID sorts first. - If no listed mod has one, the first item from any mod that is not Enthalpy.
- If the only items are Enthalpy's own, the first of those.
- If the tag is empty, there is no output, and the recipe is skipped.
The mod names are namespaces: the part of an ID before the colon. So mekanism matches
mekanism:dust_tin, and minecraft matches vanilla items. A name in the list for a
mod that is not installed does nothing.
The setting is outputs.preferredMods, a list of mod names. Its default order, and its
exact wording, are on the config reference.
Where it applies#
- Only tag outputs. A recipe that names one item with
idalways gives that item, whatever the config says. - Every kind of output. Results, secondaries and byproducts of Enthalpy's recipes, the resource a fish yields, and the Salt Pan's salt block all resolve this way. See the recipe formats for the output shape.
- Not ingredients. A tag in an input accepts every item in the tag. The order only matters for what comes out.
- On the server. It is a server setting like the rest; see how the config works.
Tips for pack makers#
- List
enthalpyto prefer Enthalpy's own items. They are used last by default, but they count as a mod like any other if you name them. Putenthalpyfirst and Enthalpy's own iron, gold and copper dust win wherever they exist. - Keep
minecraftnear the front if you want vanilla items to win where they exist; it matters for tags such asc:ingots/iron. - Choose one metal family per pack. Players expect one tin dust, not three. Put the mod you are standardising on first.