How to Fish Wiki hook and wave mark

Release log

Patch 1.0.10 Guide

How to Fish Patch 1.0.10 released on August 27, 2026. Its official notes save up to 64 dropped ground items between sessions, let water clean cooked-on weapons and tools, nerf Anglerfish, cap explosive item velocity and fix a Tuna-death problem that could stop Albatross spawning. These are practical route protections, but the announcement gives no numeric balance values or guarantee that every lost item will return.

Guide status

published

Reviewed 2026-09-05. Evidence scope: Official Patch 1.0.10 · released 2026-08-27. This guide is updated when key route details can be checked.

01Read the release as a route-reliability patch

Patch 1.0.10 combines persistence, tool maintenance, creature balance and encounter fixes. The official notes say that up to 64 dropped ground items can be saved between sessions, with priority for weapons, tools, quest items and creatures. That directly matters when a crew must preserve an unusual catch or hand-in. It does not define a safe storage system or promise every lower-priority item will persist.

The same notes name Anglerfish as nerfed and cap the velocity of items shot from explosions. Neither statement includes a numeric value. A guide should therefore identify the patch and avoid transforming a broad balance note into a damage chart or a guaranteed physics result. Treat the release date as a useful boundary when checking older player reports.

02Handle dropped items conservatively

Saved ground items are a recovery improvement, not an invitation to scatter route-critical objects around an island. The published priority order favours weapons, tools, quest items and creatures, but it still has a 64-item limit. Keep the current hand-in in inventory when possible and complete the prompt before beginning optional selling or combat. That route discipline remains useful even after later Steam Cloud support arrives.

If an important item is missing after returning to a session, first verify the active quest and retrace the documented trigger. Do not assume a persistence failure without checking whether the item was sold, handed in or replaced by a different objective. Note the platform, patch and item state if you report the issue. Those details give developers and other players something testable instead of a vague loss report.

03Clean equipment with water when cooking leaves residue

Patch 1.0.10 says water now cleans weapons and tools after cooking. That is a clear utility interaction, but the note does not set out every affected item or a full cleaning sequence. Use water as the first practical check when cooking leaves a tool in an awkward state. Avoid claiming that a specific weapon is permanently repaired or improved by the action.

This change is most useful when it prevents a small maintenance problem from interrupting a route. Test it with non-critical equipment before relying on it during a boss sequence. If your result differs, record the item, platform and current patch. The page deliberately separates the official water-cleaning statement from any unverified optimisation routine.

04Understand the Tuna and Albatross fix

The developer says Patch 1.0.10 fixes an issue where killing Tuna could prevent Albatross from spawning. This explains why a pre-patch discussion may describe a broken progression trigger. It does not prove that every modern Tuna or Albatross problem has the same cause. Confirm the active route and retry the documented trigger before looking for an unsupported workaround.

The focused Albatross guide keeps Tuna as a route trigger while avoiding claims about fixed coordinates or hidden spawn odds. That is still the right page for a player who is currently stuck at the Rocks route. Use this update page when you need the historical reason an old guide may be obsolete. Keeping those jobs separate reduces the risk of duplicate or contradictory advice.

05Place Patch 1.0.10 in the current timeline

Patch 1.0.11 later added save checks and backups, while Patch 1.0.12 added Steam Cloud support and further item-velocity work. Those releases build on the same reliability concerns without changing the original 1.0.10 record. Read the newest relevant page before testing a current issue. Do not collapse several patches into one made-up rule about saves or items.

For a stable run, preserve the exact hand-in, finish the quest, then move to the next objective. For a research run, change one factor and capture the patch version with the outcome. This gives the site a repeatable evidence trail instead of a copied list of notes. It also helps players decide whether a newer guide applies to their current problem.

Next verified routes

Continue with the exact next question

Keep a stable beginner routePrioritise current hand-ins over optional dropped-item experiments.Use the Albatross trigger guideCheck the current Tuna route before relying on older spawn reports.Protect a quest-item routeFollow a focused hand-in workflow rather than an assumed persistence trick.Review the current Patch 1.0.12 pageSee the later Steam Cloud and item-reliability context for the live build.

Evidence boundary

What this guide can confirm

  • The official Patch 1.0.10 notes state that water cleans weapons and tools after cooking and that up to 64 dropped items persist with a published priority order.
  • The same announcement identifies the Tuna-death issue that could prevent Albatross spawning and says it was fixed.
  • Anglerfish and item-velocity changes are documented without official numeric values, so this guide does not infer a balance table.

Sources and review scope

Check the evidence behind this route