Nice Day for Fishing / GAME HISTORY
Nice Day for Fishing In Dire Straits: The Wrong-Bank Save Report
Team17 support acknowledged a report of loading on the wrong bank during In Dire Straits. A player reported recovering through a save-position edit, but the checked exchange does not establish a universal repair or a final patch version.
Short answer
Team17 support acknowledged a report of loading on the wrong bank during In Dire Straits. A player reported recovering through a save-position edit, but the checked exchange does not establish a universal repair or a final patch version.
Scope: June 2025 Steam support exchange for Nice Day for Fishing. Historical report, not a claim that every current build has this fault.

The position changed after Continue
SeaCow reported starting In Dire Straits, quitting through the menu and then loading on the opposite bank of Honeywood Lake. The campaign had not provided the transport needed there. Jumping and restarting did not get that player back onto the intended route.
The sequence to match before trying advice
This is more specific than a general missing-save problem.
- Begin the In Dire Straits quest.
- Quit the active session.
- Select Continue.
- Find the character on the opposite bank, without the route or boat expected for that quest state.
If your file is missing from the menu or a different quest is blocked, this report does not establish the same failure. Record the quest name and where the character actually loads.
The reported edit was not a support guarantee
SeaCow said changing PlayerSavePosition to HoneywoodSpawn recovered the character. That is one player’s save edit, not an instruction endorsed by support for every campaign. Do not overwrite the only copy of a save merely because its symptom sounds similar. Retain the original and seek game-specific support before making a manual change.
What happened afterward
Team17_Helper acknowledged the issue on June 2, 2025 and said it was being passed to the team, without a repair timetable. The checked exchange does not show a final patch version. That absence is not proof no fix was ever released. Install current updates and include the platform, build, quest and load location in a new report. The concrete failure was access to the intended route; the record does not justify calling all progress permanently destroyed.
Join the conversation
Have a question, correction or a different take? Share it below. Comments appear immediately after submission.
Reader comments
Loading comments…