How to Fish Wiki hook and wave mark

Release log

Patch 1.0.11 Guide

How to Fish Patch 1.0.11 released on September 1, 2026, adding GeForce NOW support, Steam Deck Verified status, input toggles and save safeguards. It also changed explosive self-damage and removed Iron Sight from purchasable upgrades. Use the update as a practical compatibility and safety reference, not as evidence for unlisted balance numbers or a permanent best build.

Guide status

published

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

01Know what this release officially changes

Patch 1.0.11 is a broad quality-of-life and platform update. Its official notes add GeForce NOW support, mark the game Steam Deck Verified and provide toggle options for aim, sprint and nametags. The same release checks saves before loading and creates a backup if a save is corrupt. These are released features, not a guarantee that every hardware or save issue has disappeared.

The announcement also includes weapon, inventory, cooking, roulette and player-visibility fixes. A patch page is useful because it ties those details to the developer’s own release date. It should not be read as a full replacement for a current route guide. When the task is catching a fish or handing in a quest item, use the specific guide after confirming the installed version.

02Use input and platform options deliberately

Toggle aim, toggle sprint, hold attack and toggle nametags are accessibility and control options introduced in this release. Try one setting at a time in a low-risk situation rather than changing a full combat routine during an important boss attempt. The notes do not claim that any option improves damage, aim assistance or fish behaviour. Choose the control mode that lets you perform a repeatable input comfortably.

Steam Deck Verified and GeForce NOW support expand where players can use the game, but they do not make a route platform-neutral by themselves. On a new device, check controls, audio and save availability before starting a timed achievement or a final encounter. Keep a brief note of platform-specific behaviour when reporting a problem. That makes a community report more useful than a general claim that a patch is broken.

03Keep save safeguards in perspective

The official save work checks a save before loading and creates a backup when corruption is detected. That is a valuable recovery safeguard, especially for long progression routes. It does not make careless item handling or skipped quest dialogue reversible on demand. Continue to finish a hand-in when possible instead of depending on a backup as a route step.

Patch 1.0.10 had already begun preserving dropped ground items between sessions with stated priority rules. Together, the two releases improve resilience but do not erase the difference between a held item, a ground item and a completed quest. Keep irreplaceable route items visible and avoid selling them in a clean-up pass. The beginner guide uses that conservative approach rather than promising a particular recovery result.

04Reconsider explosive and shop assumptions

Patch 1.0.11 says that a player’s own explosives can kill them even when friendly fire is disabled. This is a direct safety change for solo and co-op players. Do not infer that an explosive becomes harmless when teammates cannot be damaged. Test spacing and escape routes before using one in a progression fight.

The update also removes Iron Sight from purchasable upgrades and says a suppressor cannot be downgraded to a compensator. Those are shop and attachment boundaries, not a ranking of the remaining options. A current purchase plan should begin with the route blocker and the items actually available in the build. Avoid copying a buying list that assumes the removed item is still sold.

05Use later updates for later fixes

Patch 1.0.12 follows this release with Steam Cloud support, later Piranha and Tuna balance work, item-velocity limits and a Final Boss explosive fix. That newer note does not rewrite the 1.0.11 record, but it can change what a player needs to test today. Compare dates before treating an old clip or discussion answer as current. The update index lists both releases with their official sources.

For a normal run, keep the simple priority order: current build, active quest, exact hand-in and a familiar control setup. For a test run, change one variable and note the patch number. This protects a progression attempt from becoming an accidental experiment. It also creates evidence that other players can reproduce or challenge constructively.

Next verified routes

Continue with the exact next question

Start with the updated beginner guideUse source-backed first-run priorities for saves, quests and equipment.Check the current upgrade contextKeep a shop decision separate from a historical attachment assumption.Apply explosive safety to the final routePrepare around the self-damage rule before testing a combat tactic.Read the later Patch 1.0.12 impactSee the current Steam Cloud and Final Boss fix context before testing today.

Evidence boundary

What this guide can confirm

  • The official Patch 1.0.11 note confirms GeForce NOW, Steam Deck Verified status, control toggles and save backup checks.
  • The same primary source says a player’s own explosives can kill them even when friendly fire is disabled and that Iron Sight was removed from purchasable upgrades.
  • Later Patch 1.0.12 work is linked separately so this historical page does not imply that 1.0.11 is the current build.

Sources and review scope

Check the evidence behind this route