How to Fish Wiki hook and wave mark

Support log

Lost Items Guide

How to Fish Patch 1.0.10 saves up to 64 dropped ground items between sessions, prioritising weapons, tools, quest items and creatures. That is useful protection, but it is not a promise that every dropped object returns or that an item was not sold, handed in or left in another state. Identify how the item was handled before changing saves, restarting repeatedly or attempting a risky workaround.

Guide status

published

Reviewed 2026-09-05. Evidence scope: Official Patch 1.0.10 and 1.0.12 item-safety scope reviewed 2026-09-05. This guide is updated when key route details can be checked.

01Know what ground-item persistence actually covers

Patch 1.0.10 says items dropped on the ground are saved between sessions. The official limit is up to 64 total items, with priority for weapons, tools, quest items and creatures. This describes a persistence system rather than a personal inventory guarantee. It also does not list every condition that can remove, sell, hand in or replace an item during normal play.

Patch 1.0.12 later limits item velocity in an effort to make items harder to lose. That reduces one kind of risk without changing the 64-item limit into permanent storage. Keep an important route item in inventory and finish the relevant hand-in when possible. Do not use the ground as a long-term stash simply because persistence exists.

02Trace the item state before retrying a route

First name the missing object and the last confirmed state: held, dropped, sold, cooked, handed in or left in a co-op session. Those states lead to different questions, and only one is covered by dropped-ground persistence. Check the active quest and recent hand-ins before assuming the game discarded a required object. A finished progression step can make an item disappear for a legitimate reason.

For a creature used as special bait, check whether the next encounter was already triggered before treating it as ordinary loot. For a weapon or tool, check the visible inventory and the last play area without discarding anything else. For a quest item, reread the objective before farming a replacement. This short trace is safer than repeatedly loading, quitting or moving items while the situation is unclear.

03Use the priority limit conservatively

Priority does not mean immunity. The official wording says the system prioritises certain item types, but it does not promise the order for every 64-item situation. Avoid creating a test pile of dropped items around an active route. A crowded ground state makes it harder to distinguish a persistence limit from a normal location or inventory mistake.

When a crew is playing together, also record who last held the item and whether the host or a guest ended the session. Patch notes mention several inventory and joining fixes, but they do not define a universal co-op ownership rule for every object. Keep one player responsible for the current hand-in where possible. That is a coordination practice, not an official recovery mechanic.

04Avoid destructive recovery attempts

Do not delete saves, edit files or install an unverified workaround to test a lost-item theory. Those actions can create a second problem and remove the evidence needed to compare the current state. Patch 1.0.11 adds checks and backups for corrupt saves, but it does not authorise manual recovery methods. Preserve the current state while you identify whether the missing object was actually ground-dropped.

Community reports confirm that players have experienced missing ground items, but a report is not a tested fix. Use it to recognise the symptom, then compare it with the official patch boundary. If the game opens normally, keep the save problem separate from the item problem. The Steam Cloud guide explains why cross-device syncing is a different investigation.

05Record a useful lost-item report

A useful report states the item name, patch, solo or co-op state, last known item state and what happened before it went missing. Include whether you ended a session, joined a lobby, changed boats, used an NPC or saw the item fall through the level. Do not add guessed drop rates, storage limits or blame a patch without a reproducible sequence. The reported sequence matters more than a general statement that inventory is broken.

If the item is part of a named boss chain, use its focused guide to determine whether a documented trigger can be repeated safely. If it is a general persistence concern, revisit the Patch 1.0.10 and 1.0.12 pages for the official timeline. Keep any test away from a timed run or a one-off achievement attempt. That lets the site expand evidence without encouraging players to risk progress.

Next verified routes

Continue with the exact next question

Read the original persistence updateCheck the official 64-item limit and later reliability context.Separate Cloud sync from item lossUse a distinct check when the expected save changes between devices.Keep the next hand-in protectedUse the core route checklist before treating quest progress as lost.

Evidence boundary

What this guide can confirm

  • Patch 1.0.10 states that up to 64 dropped ground items persist between sessions and identifies its priority categories.
  • Patch 1.0.12 limits item velocity to make items harder to lose, but does not promise recovery for an individual object.
  • Community reports are used only as symptom evidence; this guide does not publish file edits, deletion steps or a guaranteed recovery claim.

Sources and review scope

Check the evidence behind this route