GAME MECHANICS HOARD

RECIPE EXPERIMENTATION

Discovering recipes by trying combinations — throwing ingredients in the pot to see what emerges, mixing unknown reagents, deducing formulas from ingredient properties rather than reading them from a list.

Breath of the Wild's cooking is the celebrated case (ingredient effects combine legibly: hearty things heal, spicy things warm, and the pot rewards both logic and whimsy), Noita's alchemy hides material combinations in a simulation deep enough to sustain wiki archaeology, Minecraft's original crafting grid made shape-guessing a communal puzzle (solved, ultimately, by the wiki), and Potion Craft turns mixing itself into spatial navigation. Designers build experimentation systems because discovery is a reward recipes-as-unlocks can't deliver: when the player deduces that any fish plus any mushroom yields a stamina meal, the knowledge is theirs — earned, generalizable, and satisfying in a way a menu entry never is — and ingredient logic that generalizes converts the whole item catalog into a hypothesis space. The design's real substrate is the property system underneath: experimentation only works when ingredients have legible attributes that combine by learnable rules, so players form theories rather than brute-forcing. Key decisions: failure cost (BOTW's dubious food is a gentle joke, not a punishment — expensive failures kill experimentation dead), how much the system hints (ingredient tooltips carrying property tags versus pure mystery), and the wiki question — designers must decide whether the system survives its community solving it, because it will be solved within a week. Pitfall: combinatorics without logic — when results are arbitrary lookups rather than emergent from properties, experimentation is a slot machine, players feel it immediately, and the entire discovery loop collapses into consulting the wiki the designer pretended not to expect.

SEEN IN

VIEW “RECIPE EXPERIMENTATION” IN THE MAP ▶