How to Fish Wiki hook and wave mark

Support log

Steam Cloud Guide

How to Fish added Steam Cloud support in Patch 1.0.12. The developer’s stated setup is to play and exit the game once on the PC that holds the save, which uploads that save to Steam Cloud. Do that before judging a second device or a local save as missing, and do not delete or edit a save while you are still determining which copy is current.

Guide status

published

Reviewed 2026-09-05. Evidence scope: Official Patch 1.0.12 · Steam Cloud scope reviewed 2026-09-05. This guide is updated when key route details can be checked.

01Use the exact Patch 1.0.12 Cloud setup

Patch 1.0.12 is the first official How to Fish note that says save files are stored through Steam Cloud. Its specific instruction is to play and exit on the PC where the save already exists once. That creates the initial upload step described by the developer. The note does not publish a conflict-resolution flow, a sync timer or an exception list for every device.

Treat the PC holding your expected progress as the source copy until you have completed that step. Opening a different device first can make it harder to tell which local state you are comparing. The safest first result to record is whether the original PC still opens the expected save after a normal exit. This page does not assume that a missing second-device save means the original has been erased.

02Check one device transition at a time

Start on the device with the known save, launch the game, confirm the expected progress and exit normally. Then restart Steam if an update has just installed, as the current patch note instructs players to do. Only after that should you open the other device and compare the visible progress. Keep the test limited to one transfer so an unrelated quest, item or co-op change is not confused with Cloud behaviour.

Write down the patch number, the source device and the destination device before trying again. Steam Deck, GeForce NOW and a Windows PC can present different environments even when the same Steam account is involved. The official notes establish platform support and Cloud storage, not that every device pair behaves identically. A short record is more useful than repeatedly opening several versions of the same save.

03Do not turn a sync check into a save-loss event

Avoid deleting a save, overwriting files or following a save-editing post while the source copy is still available. Those actions change the evidence you need to identify the problem and can create a new loss. Patch 1.0.11 says the game checks saves for corruption and creates backups when corruption occurs. That is a safety feature, not an instruction to force a corruption test or rely on an automatic restore.

A forum post can show that another player saw a similar symptom, but it cannot prove a universal remedy. Keep community reports as symptom context and prefer the official patch scope for what the game actually changed. If a local copy is valuable, stop changing variables once you have confirmed the symptom. The page intentionally does not publish unverified save-folder paths or file-edit instructions.

04Separate Cloud sync from a missing route item

A missing save, a missing inventory item and a dropped ground item are different problems. Patch 1.0.10 added between-session persistence for up to 64 dropped ground items with a stated priority order. That rule does not describe Steam Cloud conflict handling or guarantee recovery for an individual object. Use the Lost Items guide when the save opens but a weapon, creature or quest item is absent.

If the expected save opens on one device but not another, do not assume that item persistence caused the difference. First complete the Cloud upload step on the source PC, then compare the same progress marker on the other device. If both devices open the save but only one route item differs, record whether it was held, dropped, sold or handed in. These distinctions prevent a broad Cloud page from making an unsupported recovery promise.

05Make a report another player can reproduce

When the safe checks do not change the result, record the game patch, Steam client state, device, source device, destination device and visible save difference. Include the moment you launched, exited or changed devices rather than only saying that Cloud failed. Do not share private account details or upload an unreviewed save file publicly. This is a troubleshooting record, not a guarantee of developer-side recovery.

Return to the Patch 1.0.12 page when a new release changes the official Cloud wording. It separates the original announcement from later player observations, so historical reports do not become permanent rules. Keep your regular route and timed-achievement attempts separate from a sync test. That reduces the cost of a problem that needs more evidence.

Next verified routes

Continue with the exact next question

Read the Patch 1.0.12 source scopeSee the official Cloud announcement alongside its other current changes.Check a missing item separatelyUse the ground-item guide when the save opens but a route item is absent.Protect the current quest routeKeep hand-ins organised while confirming the save you expect to use.

Evidence boundary

What this guide can confirm

  • Patch 1.0.12 is the primary source for Steam Cloud support and its stated play-and-exit upload step on the PC holding the save.
  • Patch 1.0.11 says saves are checked before loading and have backups for corruption, but it does not publish a manual Cloud conflict procedure.
  • No official source in this set publishes a universal save-folder path, file-edit method or guaranteed Cloud recovery result.

Sources and review scope

Check the evidence behind this route