How to Fish Co-op, Save, and Troubleshooting Guide

How to Fish currently supports online co-op lobbies for up to eight players on Windows PC. The Steam description launched around a one-to-four-player structure, but Dazed Games expanded the lobby cap to eight in Patch 1.0.4. Patch 1.0.5 added private invite-only sessions. If the host changes a lobby between public and private, the session must restart before the change takes effect.

• Platform: Windows PC through Steam. Mac and Linux versions are not listed on the official store.
• Lobby size: up to eight players on the current version.
• Private play: use an invite-only session and invite friends through Steam.
• Session changes: switching public/private status requires a restart.
• Solo: fully supported; every quest and boss can be completed alone.

1. Update How to Fish in Steam so every player is on the same current build.
2. Create the session and choose public matchmaking or a private invite-only lobby.
3. For a private game, invite the intended players through Steam instead of waiting for public discovery.
4. If the session type changes, save, restart the session, and send fresh invites.
5. Before sailing, confirm that every player has loaded, can move items, and sees the same quest state.

A large lobby creates more physics, dropped items, and opportunities for a quest trophy to move. Eight players can be fun, but two to four coordinated players are easier for a first story clear. Add more people after the group understands who is carrying progression items.

The game does not lock players into classes, so roles can change at any time. A temporary division of labor is still useful because the group needs fishing, damage, crowd control, food, shopping, and item management at once.

• Quest carrier: holds the bait and boss trophy, performs hand-ins, and avoids unrelated selling or gambling.
• Angler: equips the correct lure and controls where the target lands.
• Boss damage: brings the strongest reliable weapon and focuses the main creature.
• Crowd control: clears smaller Piranhas, moving birds, and other threats that pressure the carrier or damage player.
• Support: cooks food, watches ammunition and spare equipment, and collects ordinary catches for the next purchase.

Before each boss, say who needs a specific achievement. The player pursuing a final-hit, dynamite, bare-hands, or hand-in achievement should perform that action personally whenever possible.

Patch 1.0.9 added Easy and Hard. The official modifiers are creature-side: Easy gives creatures 25% less health and makes them deal 50% less damage; Hard gives creatures 25% more health and makes them deal 25% more damage. Use Easy when a story boss is blocking the group or when practicing the Bean speedrun. Use Hard when a geared group wants longer fights.

More players do not automatically make the session cleaner. Extra guns shorten fights, but extra bodies can also scatter items, block lines of fire, move the boat, or trigger chaotic physics. Choose difficulty and lobby size for the experience the group wants rather than assuming the largest lobby is always easiest.

The current save system writes progress when the player selects Save, returns to Main Menu, or quits normally, and it autosaves every minute. Patch 1.0.6 also added save-file validation and stopped the game from writing a save when the application crashes. Later patches added another save-corruption fix. A crash therefore should not be treated as proof that the latest minute was written.

• Before a boss lure: use the explicit Save option.
• Before leaving: choose Save, Main Menu, or Quit and allow the normal exit to complete.
• After a crash: reopen the game and inspect the current quest, inventory, and island state before doing anything else.
• During co-op: have the host and quest carrier verify the hand-in after a major boss rather than assuming every client saw it.

Do not repeatedly force-close the game to test an item outcome. Normal saves provide an auditable recovery point; crashes intentionally do not write a new save.

Patch 1.0.10 made up to 64 dropped items persist across sessions. When the limit matters, the game prioritizes weapons, tools, quest items, and creatures. This is useful protection for a busy co-op beach, but it is not unlimited storage.

• Keep progression objects visible: place the shell, trophy, fin, head, or tail away from the sale area and grill.
• Reduce clutter: sell or use ordinary low-value objects rather than building a pile around an NPC.
• Designate ownership: one player should announce before dropping a quest object.
• Do not rely on item 65: the persistence cap is a safety net, not a reason to use the island as infinite storage.

1. Confirm every player has finished the Steam update and fully restart the game after a version change.
2. If the host changed public/private status, restart the session before sending another invite.
3. Create a fresh private lobby and invite one player first to separate a lobby problem from an eight-player load problem.
4. Watch the relay status. Patch 1.0.9 added feedback when Steam networking reports a relay problem.
5. Allow the longer current connection window to finish; Patch 1.0.10 increased connection time before timeout.
6. If one player still fails while others join, have that player restart Steam and the game before rebuilding the whole host session.

Patch 1.0.4 addressed black- and gray-screen problems, while later patches fixed additional connection and player-loading states. An old workaround may no longer describe the current failure. Start with matching versions and a clean lobby rather than deleting saves.

• Read before writing: load the save and inspect the current island, quest hand-in, inventory, and boat state.
• Check the host: a joining player may be looking at a different local state than the person who hosted the progression session.
• Use a normal restart: Save or Main Menu, close the game, reopen it, and verify one known checkpoint.
• Do not overwrite blindly: if the expected state is absent, avoid a long new session until you know which save is current.
• Preserve evidence: the current player.log includes the game version after Patch 1.0.10. Keep the version and symptom if a support report becomes necessary.

The official patches improved validation specifically to prevent corruption and to avoid saving during a crash. Deleting, replacing, or manually editing files is not a first-line fix and can destroy the only readable state.

• Controllers: the Steam page lists full controller support, DualShock, and DualSense support. Patch 1.0.8 added PlayStation button glyphs.
• Inverted camera: Patch 1.0.5 added separate invert options for mouse and controller axes.
• Low frame-rate lock: the minimum locked setting was reduced from 50 to 30 FPS in Patch 1.0.5.
• Fire volume: Patch 1.0.8 moved fire sound under the FX volume control.
• Minimum PC baseline: Windows 10+, 8 GB RAM, an Intel i5-5257U or Ryzen 3 1200-class CPU, and a GTX 1050 or RX 460-class GPU are listed on Steam.

When one player reports a control or performance issue, test that machine without assuming it is a lobby-wide failure. Matching game versions and a short solo test make the boundary much clearer.

• The local quest giver has accepted the boss trophy.
• The next coordinates, boat keys, or progression trigger appeared.
• Quest bait and important dropped objects are accounted for.
• The host used a normal save action.
• The player who needed a specific achievement confirmed the unlock.
• The lobby is still using the intended public/private setting.

This thirty-second check prevents most expensive backtracking. How to Fish is intentionally chaotic; the progression state does not have to be.