The verified loop
Stackmon can gather materials, those materials feed item crafting, and repeated tasks can be automated around Harmony. New base development is also described as unlocking recipes and upgrades.
- Assign a Stackmon to a visible material task.
- Read the resulting cards before combining further.
- Check whether a camp upgrade unlocks the next recipe in your build.
Why this is not a complete recipe list
Demo patch 7.0.33 explicitly removed a few recipes. A list captured from an earlier Demo can therefore be plausible and still be wrong for the launch build. This page does not republish crowdsourced combinations as current facts.
What will unlock a Recipe Finder
The tool can ship after inputs, outputs and build version are reproduced in the current game. Reverse lookup also needs to confirm that multiple paths or substitutions are represented correctly.
A launch achievement confirms the scale—not the list
The official Eureka! achievement asks players to discover 30 recipes. That proves a meaningful recipe-discovery target exists in the released game, but it does not publish the ingredients or prove that 30 is the complete total.
Build a recipe notebook that survives patches
For every working combination, record the exact input card names, quantities, order of interaction, output, station or building, and the game build. Add a screenshot of the input state and result when possible. A recipe name without version and context is fragile because the Demo already demonstrated that recipes can be removed. Keeping failed attempts alongside successes also helps distinguish an incorrect input from a locked recipe, missing building or changed progression requirement.
- Exact input cards and quantities
- Required building or board state
- Output card and visible count
- Build version and date reproduced
- Screenshot or short reproduction note
Troubleshoot a failed stack in a safe order
First confirm that every card name matches the recipe you recorded and that no card is already occupied by another job. Next read the current tooltip for a required building, unlock or action. Then separate the cards and retry the same combination once. If an older guide supplied the recipe, check whether it came from the Demo. Avoid selling materials, deleting saves or reinstalling the game to diagnose one combination; those actions destroy evidence without proving why the stack failed.
Separate discovery progress from complete coverage
Eureka! measures the milestone described by Steam: discover 30 Recipes. It does not state that only 30 recipes exist, that every discovered recipe still works after a patch, or that all players reveal them in the same order. Use the achievement as a personal checkpoint. For a public recipe index, each row still needs independently verified inputs, output and build context even if Steam has already advanced the achievement counter.
Evaluate automation by the bottleneck it removes
Official store copy connects repeated tasks with automation around Harmony. Before automating, identify whether gathering time, card space, a building unlock or a missing ingredient is actually blocking the next goal. Automating a plentiful input can make the board busier without helping progression. Record one manual cycle, then compare the automated state using the same output and time window. This is a decision framework, not a published production-rate table, because exact rates still require current-build measurement.