How to Fish Patch 1.0.10 notes and known issues

What Patch 1.0.10 added

Weapons and tools that were accidentally cooked can now be cleaned by dipping them in water. This is a recovery feature for equipment; it does not change the 1.5x cooking route for catches you intend to sell.

Items dropped on the ground now persist between sessions, with a maximum of 64 saved items. Weapons, tools, quest items, and creatures receive priority. The limit means the ground still should not be treated as unlimited storage.

Balance and interface changes

The Anglerfish was slightly nerfed because its health made the encounter more frustrating than intended. Patch 1.0.10 also removed the Radar X that represented the player's last death; it was not a new destination or quest marker.

The end-game screen no longer shows item dots, chat rich text was removed after abuse, and the game version is now written to player.log to make bug reports easier to identify.

Connection, item, and roulette fixes

The patch increases the allowed connection time and attempts to fix equipment appearing far away, items falling through the level after loading, and a respawn lock caused by dying to Tuna while spawning Albatross.

Roulette received fixes for endless ticking, the ball clipping through the wheel, and sessions breaking after a player leaves mid-game. These are fixes to reported bugs, not a published change to reward odds.

The Patch 1.0.9 changes that still matter

Patch 1.0.9 added Easy, Normal, and Hard modes and allows difficulty to be changed in the main menu or during a session. Easy reduces creature health by 25% and damage by 50%; Hard raises both creature health and damage by 25%.

The same patch added Steam relay status text to the main menu and attempted to fix corrupted saves. Use the relay indicator when diagnosing joins, but keep manual save backups because a fix cannot recover a file that was already damaged.

A clean update checklist

Restart Steam, confirm the build in player.log when necessary, and make sure every multiplayer participant is updated. Back up the host save before loading a long-running world for the first time after a patch.

• Restart Steam instead of repeatedly launching an old cached build.
• Back up the complete Saves directory before testing item persistence.
• Use a temporary session when reproducing a multiplayer or roulette problem.
• Record version, island, player count, and the last action in any bug report.