How a craft stores its inputs and outputs

The game ships a single GameBalance object inside resources.assets. It holds a craftDefs array of 827 entries. Each entry carries needItems for what it consumes and outputItems for what it produces. Nothing on this page is estimated: the counts are read straight out of that object.

needItems is a flat list of entries, each pairing an item id with a count. 584 of the 827 crafts have at least one entry. A recipe that takes two different materials therefore appears as two entries rather than one entry with two counts.

outputItems is not a list. It is an object whose chanceOutputItems field holds the produced items. Because the field is named for chance, a craft can carry several possible outputs, and a planner that reads outputItems as a flat array will report zero outputs for all 827 crafts. Reading chanceOutputItems instead finds 468 crafts that produce something.

Expand a target item by repeatedly replacing each entry with the inputs of a craft that produces it, accumulating counts. Stop when an item has no producing craft: that item is a base material. The recursion has to remember the items already on the current path, because a production chain can loop back on itself. Without that guard the expansion does not terminate.

The counts above are read from the shipped data, but which workstation a craft is offered at, and whether an output is guaranteed or probabilistic, still need review before they are published as facts. Those fields are recorded and deliberately left out of the claims here.

Read directly from the GameBalance object in the shipped build through scripts/gb_reader.py, cross-checked against the handover snapshot.

• Graveyard Keeper 2 game balance data (GameBalance)→Lazy Bear Games · in_game · Checked 2026-09-25