Start with the item you need, not a full inventory
When a task or upgrade calls for an item, first identify its exact name and role. Is it a raw material, a processed ingredient, a crafted piece of equipment, a learned recipe, or a task object? Similar-looking items can belong to different stages of the production chain. Gathering more of the raw material will not solve a request for a processed product until you have the correct station and recipe available.
Open the relevant item description and task wording together when possible. Check quantity, quality, and whether the item must be brought to a person, inserted into an object, or used from the inventory. Those are different actions. A task can remain incomplete even when you own the right material if you have not performed the requested hand-in. Conversely, consuming or processing a task item because it resembles ordinary stock can create avoidable extra work.
Choose one concrete target for the next gathering trip. A list of every possible future recipe is useful as a reference, but it is a poor shopping list for an early inventory. Focus on the upgrade or supply that improves the next objective. Once that requirement is met, you can keep a reasonable reserve for known uses. This keeps the bag useful and makes it easier to notice when the missing ingredient is actually an access problem.
Read the station before reading the ingredient list
The current walkthrough separates recipes by station and purpose, including cooking, equipment, upgrades, decorations, and utility objects. Start in the correct category. If an item is absent from one crafting menu, it may belong to a different station rather than being unavailable in the game. Check the recipe reference and the current station interface before spending time trying unrelated ingredients or searching the same menu repeatedly.
A station's existence is not the only access condition. You may need a blueprint, a task introduction, or an upgrade before the relevant recipe appears. Molly's workshop progression is a useful example: the Elder Gem task connects to a forge upgrade blueprint after earlier workshop steps. Follow the journal and conversation sequence. Owning ore and standing near a forge does not prove that every later equipment recipe should already be visible.
When a guide and your menu disagree, compare the build and save context. Historical developer notes changed crafting descriptions and some learning behavior, and the itch archive does not contain every intermediate version. A recipe screenshot from an older demo can be accurate for that build and still fail to match your current game. Use the present description for quantities and effects, then use the guide to identify the likely unlock you have not completed.
Trace a recipe backward through its inputs
Work backward from the final item. List the immediate ingredients, then identify which of those must themselves be processed or crafted. This reveals hidden costs such as fuel, predecessor equipment, or a separate preparation step. A recipe that appears to require only a few finished materials can involve several earlier operations. Understanding the chain before leaving town prevents a second trip caused by forgetting the input that makes the visible ingredient possible.
Keep the calculation simple and explicit. For a hypothetical recipe requiring several bars, first determine the current ore and fuel needed for those bars, then add any bars already in storage. Do not copy a universal smelting ratio from an unrelated guide. Different recipes and builds can use different costs. The live station supplies the actual numbers; your job is to account for every stage so the gathering trip has a realistic target.
Check whether the craft consumes an existing item. Upgrade recipes can make an older weapon or tool part of the input, which is a reason to read the full chain before selling predecessors. If the required piece is also your current equipment, decide when to craft so you do not leave for an expedition missing the item you intended to replace. Complete the chain and inspect the result before assuming the upgraded loadout is ready.
Distinguish learning from producing
A blueprint or tome can teach something without directly producing the finished object. Read the item's use instructions, apply the learning step where appropriate, and then check the relevant menu. If you already know the recipe, another copy may have a different practical value from the first. Do not assume that finding a book means the associated machine or ability has appeared automatically in the world.
The books reference is useful because it states what a named book teaches. It also shows that not every acquisition source is documented. An entry with a description but no reliable location should be treated as a known item with an unresolved source, not a promise that you can buy it from any shop. Use a documented source when available and avoid building an urgent progression plan around a blank field.
After learning, verify the result before gathering a large batch. Check that the recipe appears, that you can access the required station, and that the output is the item you need. This brief confirmation prevents a common waste: collecting ingredients for a similarly named recipe or a later station tier. It is especially useful when translated names differ between the guide and your game. Match the role, icon, and ingredients as well as the text label.
Read quality and substitution rules carefully
Do not assume that all items in a broad category substitute for one another. A recipe may require a named ingredient, a quality level, or a particular processed form. Read the selectable inputs and the description on your build. If the interface accepts alternatives, compare their other uses before committing the rarest one. An ingredient that works is not always the ingredient you should spend when a common option achieves the same result.
Preserve high-value or task-relevant stock until its role is clear. This does not require hoarding every item indefinitely. Keep a small reserve for known upcoming requirements and use ordinary surplus for routine production. The appropriate reserve changes as new tasks appear. A practical inventory supports the current route and a few foreseeable needs, rather than becoming a museum of every object you have ever picked up.
When output quality or yield differs from expectation, inspect the input and process before calling it a bug. You may have used a different quality version, selected a different recipe, or followed an older table. Repeat a small controlled batch if the cost is reasonable. Large batches amplify a misunderstanding. A single verified production cycle gives you a dependable basis for planning the rest of the materials.
Compare processing with immediate use
Processing can create a more useful ingredient, a better recovery item, or a product for sale, but it also uses time, station capacity, and sometimes fuel. Compare the finished item's purpose with what you give up. If the raw material is needed for a task or an equipment upgrade, selling a processed version may delay more valuable progress. The highest sale price is not automatically the best use of a scarce input.
For combat supplies, compare the practical recovery or effect rather than only the market value. A crafted food that supports several safe encounters may be worth keeping even if it would sell well. Conversely, using a rare ingredient for ordinary recovery can be inefficient when a common meal does the job. Match the supply to the pressure of the route. Save specialized production for situations where its effect makes a meaningful difference.
Processor references should be read with their timing and fuel columns, not just the output column. If a product takes time, start it before the activity that will occupy you elsewhere. If fuel is required, include it in the gathering or purchasing plan. Do not arrive back from a long trip expecting finished materials from a machine that never had the complete input needed to begin.
Prefer predictable sources for urgent needs
Item references distinguish fixed pickups, shops, crafting, task rewards, and possible loot. That distinction should decide the route when you need something soon. A slightly more expensive guaranteed source may be better than repeated costly battles with an uncertain reward. A task reward may be reliable but unavailable until prerequisites are complete. Read the source as a sequence of conditions, not just a place name.
Random reward pools deserve careful wording. If an enemy can drop a material, that does not mean every victory will produce it. A mystery outcome may depend on a particular result, and a shrine bonus may require settings or conditions described elsewhere. Follow the linked explanation before investing time. If the source is incomplete, keep the item as a later possibility rather than claiming you have found a dependable farming route.
For repeated gathering, measure the whole trip. Count the travel, encounters, recovery, and processing needed to turn the resource into the desired item. A location with more visible nodes can still be slower if its battles consume much of the haul's value. Choose the route you can complete reliably with your current tools and equipment. You can move to a more demanding route once the supporting setup makes it efficient.
Investigate a missing recipe in a useful order
First confirm the exact item and station. Then check whether the recipe has been learned, whether the station is upgraded, and whether the relevant task introduction is complete. Next inspect ingredient forms and quantities. Only after those checks should you treat a missing entry as a likely technical problem. This order follows the common dependencies and avoids reinstalling a game because a workshop conversation has not yet happened.
Use the journal to identify the next access step. A letter may need to be read, a task may need a final hand-in, or a person may need to explain the station. The Elder Gem chain is documented with several such stages, making it a good reminder that progression is more than owning a material. If the task appears complete but the expected recipe is absent, record the precise state and compare it with current guidance.
If you report the issue, include the recipe name, station, game version, task stage, and what the menu shows. A screenshot of the relevant menu can be useful if it contains no unrelated personal information. State whether the save began in the demo or a later build. This context helps separate a missing prerequisite from a version-specific issue and gives the developer a much better starting point than a report that crafting simply does not work.
| Symptom | Check first | Next useful action |
|---|---|---|
| Recipe is absent | Station and learning state | Complete the relevant unlock. |
| Craft is unavailable | Ingredient form and quantity | Trace the missing input. |
| Expected loot did not appear | Guaranteed versus random source | Use the appropriate acquisition route. |
| Output differs from a guide | Quality, recipe, and build | Verify one small batch before scaling. |
Keep an item reference useful instead of exhaustive
An effective personal reference records what an item is for, a reliable source, and the next recipe or task that needs it. You do not need to memorize every sale price or copy hundreds of rows. Focus on the items that affect current decisions. When a new ingredient appears, read its description before selling it, then place it in the appropriate plan: immediate use, known reserve, or ordinary surplus.
Update that plan as the game opens up. An item that was once rare may become easy to obtain; a common material may become the bottleneck for several useful machines. Reassess based on the recipes you can now craft and the routes you can now reach. This prevents an early-game habit from controlling inventory decisions long after its original reason has disappeared.
The core method is to verify the output, trace the station and learning requirements, calculate the complete input chain, and choose a source whose reliability matches the urgency. That method works across cooking, equipment, and utility crafting without inventing missing recipes. It gives you a concrete answer to the most common material problem: whether to gather more, process what you already own, or complete the access step that makes the item possible.
An ingredient trip should end with a usable output
Before calling the material trip finished, return to the station and verify that the planned craft is now possible. This final check catches an overlooked fuel requirement, an incorrect processed form, or a predecessor item still in storage. If one input is missing, you can name it precisely and plan a short follow-up instead of returning to the same area with a vague intention to collect more of everything.
After crafting, inspect the output's description and equip or place it where the plan requires. A machine sitting unused in the inventory has not yet improved production, and a weapon that remains unequipped has not changed combat readiness. Follow through to the practical result. Then replenish any routine supplies consumed by the trip before beginning the activity the item was meant to support.
Keep the remaining ingredients according to their next known use. If several recipes compete for the same rare material, decide which one comes next before processing the surplus automatically. This turns crafting into a sequence of completed useful upgrades, rather than a growing pile of intermediate products that do not yet solve the problem you set out to address.
Sources & further reading
Mechanics are compared across cited sources; older-build differences are stated in the articles.