Inventory and storage: keep useful supplies within reach

Organise around your next action

The most useful inventory is one in which you can find the tool, food or task object needed right now. It does not need a separate container for every possible category. Start with the few distinctions that affect decisions: supplies for today's trip, items reserved for accepted tasks, materials for the next craft and surplus you can sell or store. These are purposes, not necessarily four different chests. Keep the arrangement simple enough that you remember it after a few days away from the game.

Elderfield connects many systems through the same items. A fish can be a task object, a cooking ingredient or a sale; ore can be needed raw or as a bar; an old tool can be an upgrade ingredient. Sorting only by appearance will not protect those uses. Before a bulk transfer or sale, identify the pieces already committed to a plan. This takes less time than repeating a fishing or mining trip because the one requested item was automatically processed or sold with the rest of the day's haul.

• Clear search and category filters before declaring an item missing.
• Check independent chests separately from primary storage.
• Review the displayed list before a bulk transfer.
• Preserve exact task ingredients and old tools needed by upgrades.

Know which storage you are using

Primary storage and an independent chest are not necessarily the same inventory. The community crafting reference explicitly describes the Small Wood Chest as separate from primary storage. If an item seems missing after you placed it in a newly built container, check that container rather than assuming every storage interaction shows the same contents. Give independent chests a clear purpose so they do not become several anonymous places where an important item might be hiding.

A useful independent container is one whose role you can explain immediately: reserved task materials, a small collection of decorations or supplies for a particular project. If you cannot remember why an item belongs there, it may be easier to keep it in the main system and use available sorting or search. Building more storage can make searching worse when the real problem is unclear organisation. Add a container to solve a specific separation need, not simply because the main list has become visually long.

Remember the crafting and processing exception

The developer has explained that ordinary crafting can draw from storage. Processors are deliberately different: the input must be carried, although fuel can come from storage. This is why a recipe may recognise stored materials while a Furnace or Grinder does not offer the item you expected to load. The distinction is intentional and should be checked before treating the machine as broken.

For a processing route, withdraw the input quantities you intend to use, then visit the machines. For regular crafting, inspect the recipe at the correct station first and identify what is actually missing. Do not automatically carry every building material to every workbench. If the relevant item is in an independent chest, verify how that container is treated rather than assuming the primary-storage rule applies identically. A small test with an ordinary material is enough to establish the behaviour without moving the whole stockpile or constructing replacement stations.

Clear filters before replacing a missing item

When an item disappears from view, first clear any search text and category selection. A filter changes the displayed list; it does not prove the object has been consumed or lost. Search the inventory side and the storage side separately, then inspect independent containers you have used. If the item is equipment, check the equipment screen as well. If it was a processor input, consider whether it has already become an output waiting at the machine.

Only after those checks should you decide that the item must be gathered or purchased again. Reconstruct the last action: did you sell, craft, load a processor, transfer a whole stack or simply change the view? That sequence often explains the apparent disappearance. For an important task object, read the objective to see whether the hand-in already consumed it or advanced the task. A missing inventory entry can be normal after successful progress. Searching is faster when you test those concrete explanations instead of opening every menu repeatedly without a plan.

Use sorting to answer a question

Sorting is useful when you know what you are trying to see. Alphabetical order helps locate a known name; a category view helps review similar items; a recent-items view can clarify what a trip brought home; a price-oriented view can help identify potential sale surplus. The documented demo interface added several sort modes and manual arrangement, but use the labels available in your installed build rather than following a screenshot whose controls may have changed.

Do not spend an entire session maintaining a perfect custom order if ordinary sorting already answers the question. Manual arrangement is most valuable for a short group you use repeatedly. If changing to another sort makes that arrangement appear different, inspect the available manual mode before assuming it was erased. Likewise, when a stack has been completely removed and later reacquired, its position may not behave like an item that remained present. Treat sorting as a viewing tool, not as evidence of item ownership. The count and location of the item are what matter.

Review the visible list before a bulk transfer

Bulk actions are convenient only when the displayed selection matches what you intend to move. Check the visible items before using a deposit command, especially with category or search filters active. The June demo documentation describes Deposit All in relation to the items shown in the inventory list. Do not assume the action means either every owned object or only the currently highlighted stack without reading the current interface.

A practical sequence is to narrow the view, inspect it, transfer, then clear the filter and verify the remaining travel supplies. Pay particular attention to food, bait and tools you expected to carry. If a bulk deposit leaves a processor unable to load, the input may simply have moved into storage. If fishing no longer starts, check the rod and loaded bait rather than assuming a new fishing problem. The inventory action and the later failed interaction can be connected, and tracing that connection is often quicker than troubleshooting the second system from scratch.

Follow current transfer controls

Inventory inputs changed during the demo, including quick stack transfer and custom quantity actions. An older guide may describe holding a modifier together with another button, while your current interface uses a single input. Read the on-screen hint before repeating the old sequence. Test the action with an ordinary item and check the resulting count on each side before using it on a rare ingredient or a reserved task stack.

Dragging outside the inventory area can be a discard action with a confirmation rather than a transfer to storage. Check where you release an item and read the confirmation if one appears. Do not rush through a prompt merely because you expected to deposit something. If the input behaves unexpectedly, inspect controller notation or key bindings and compare the current hint. Resetting all controls is a broad change; first determine whether the issue is one misunderstood transfer command. A precise correction preserves the settings that already work for the rest of the game.

Carry the tool needed for the route

Tools have practical presence requirements. A fishing rod or a collection tool left behind cannot help merely because you own it somewhere. Before leaving, name the interactions planned for the destination and check that the necessary tools are carried. If you intend to fish after mining, bring both the relevant rod and suitable bait. If you are collecting milk before departure, finish that interaction before putting away the bucket.

Keep earlier tools until you inspect the next upgrade recipe. The forging references show chains that consume previous tools, so an old pickaxe is not automatically disposable after a new purchase. Separate equipment you actively wear from tool ingredients held for an upgrade. That makes both the current setup and the next crafting project easier to understand. If you are unsure whether an item is needed, read the recipe rather than preserving every old object forever. The aim is to protect known requirements without turning the entire inventory into a museum of possible future uses.

Reserve exact task objects and ingredient forms

Task wording matters when organising supplies. A request for Copper Ore is not necessarily satisfied by Copper Bar, and a requested finished meal is not the same as its raw ingredients. Keep the required form available until you complete the hand-in. If the objective says to speak after gathering or crafting, return to the task giver; an item remaining in inventory does not prove the task is broken. Some progress requires the conversation that acknowledges it.

For a multi-stage objective, reserve the next required item and any difficult-to-replace components. Do not move them to a forgotten independent chest solely to prevent accidental use. A clearly understood reserve in the main inventory system may be safer than elaborate separation you cannot remember. Before selling, review the active task list against the proposed sale goods. This is especially useful after a long trip that returned several unfamiliar objects: the one that seems like ordinary loot may be the reason you entered the area in the first place.

Compare item variants before merging their purpose

Quality and product variants can create several similar entries. Read the full name, quality and use instead of relying on a shared icon. A higher-quality ingredient can have a different sale value, while a recipe may accept an ordinary version. A processed product can resemble the raw ingredient's category without being interchangeable. When a crafting requirement looks satisfied but remains unavailable, compare the exact accepted variant and quantity.

Use the current tooltip price when deciding what to sell. An old reference table may contain different values or incomplete quality rows. Sort or search can help locate the variants, but the decision still depends on their purpose. Keep the one needed for a task, recipe or collection and sell genuine surplus if the money has a use. Do not equate every duplicate-looking entry with clutter: some are different materials. Equally, do not protect them all indefinitely merely because they have slightly different labels. Read, choose and simplify.

Use one return-home sequence

After a trip, first identify task items and supplies you want to keep. Next load the processors that are part of a current project, placing the necessary inputs in carried inventory. Store materials that are not needed on the next route, collect any completed output and prepare the next trip's food or bait. Sell only after those decisions, so the sale list consists of actual surplus rather than everything newly acquired.

A stable return sequence reduces the amount of organisation needed later. You do not have to remember which trip supplied a particular item if its current purpose is already clear. If a machine batch is waiting, collect it before looking for the same product in storage. If a tool upgrade is nearly ready, keep its remaining materials together in your plan. The goal is to leave the next session with one obvious action instead of a bag full of unsorted objects and a vague memory that one of them was important.

For a concrete example, imagine returning with ore for a tool, a fish for Herb and a few ordinary ingredients. Keep the requested fish for the conversation. Withdraw or retain the ore batch needed at the Furnace, while leaving any raw ore already reserved for another objective untouched. Store the ingredients without a near-term use, and check that the food and tools for tomorrow remain with you. Once the bars are ready, finish the intended upgrade instead of starting several unrelated crafts. This sequence is useful because each item gets a decision exactly once: deliver it, process it, reserve it, carry it or sell it. It does not require a new chest for each action. If the same object has two competing uses, choose which task matters first and obtain another copy only when the second use becomes the actual priority.

Diagnose an inventory problem without changing the save

If a material is missing, clear filters and check inventory, primary storage, independent chests, equipment and processors. If a machine rejects it, verify the carried input and the accepted recipe. If a transfer moves too much, check the current quantity or stack command. If a task does not complete, inspect the exact item form and return conversation. These are different problems, and each has a small, testable explanation. None initially calls for deleting or editing a save.

If the problem persists, record the build, input method, item name, starting count, action and resulting count. A short description such as moving one selected stack from this container caused this result is useful to the developer or other players. Avoid replacing game files based on a guide for an unrelated demo bug. First reproduce the behaviour with an ordinary item if that can be done safely. Good inventory organisation is not about elaborate rules; it is about knowing where an item is, why you are keeping it and which interaction will use it next.