Corsair Cove Patch Notes and Update History

The latest official Corsair Cove update in the collected material is Patch #2, labeled v1.1.2.241844 on Steam News. It focuses on stability and includes crash fixes, ship clipping fixes, an incorrect crew-upkeep display fix, and interface, visual, and localisation improvements. Patch #1, labeled v1.1.1.241792, focuses on tutorial hints and event progression, while demo history is tracked separately.

Patch #2 focuses on stability

Patch #2 is described by the developer as a step toward a smoother and more reliable game. Its official changelog lists several crashes that could occur during gameplay and a crash related to the Hair Graphics Quality setting. It also lists a rare crash when entering the Barbos Bay event.

The same update includes fixes outside pure stability. It addresses ships clipping through islands around Buccaneer's End, incorrect crew upkeep values in the shipbuilding menu, and an incorrect “No drifters available” message while a Pirate Camp is under construction. The changelog also records visual fixes in event scenes and localisation fixes.

Patch #1 focuses on tutorials and events

Patch #1 is labeled v1.1.1.241792 in the captured official Steam News page. It fixes a rare case where the tutorial could become stuck after closing the journey summary for the Barbos Bay event. It also removes community events other than immigration events while the tutorial is active.

The update fixes the “Place your Pier here” hint when it becomes stuck and adds a save guard system intended to remove stuck hints during progression and save loading. It also fixes a case where the objective would not continue after returning from Barbos Bay unless the Pier was selected again. These changes target tutorial state and event progression rather than a general balance rebalance.

Why event fixes matter

The patch history shows that an event problem can be a progression issue rather than a ship-build issue. Patch #1 addresses tutorial and journey-summary state around Barbos Bay, while Patch #2 addresses a crash when entering the same event. These notes do not provide a universal solution for every event, but they show why the current build and save state should be checked before repeating a failed sequence.

House of Fortune does not have a complete official walkthrough in the collected research. Its dedicated Wiki page is empty, so its choices, rewards, prerequisites, and current behavior remain To be confirmed. Do not use the Barbos Bay fixes as proof that House of Fortune follows the same event logic.

Demo history is separate

The collected Steam history includes a separate Corsair Cove Demo product. Demo updates and the full game's Patch #1 and Patch #2 should not be merged into one changelog because they can represent different builds and different content. The captured FAQ material also states that demo saves are not transferable to the official 1.0 release.

When troubleshooting, record whether the issue appears in the demo or full game. Include the product name, platform, build label, save origin, and the exact reproduction steps. A fix listed for the full release may not exist in the demo, and a demo behavior is not evidence of the current full game.

How to use these notes

Start with the official Steam News entry for the version that matches your installation. Compare the listed problem with the changelog, then restart the game and reproduce the issue on a backed-up save if necessary. A patch note can confirm that a bug was addressed, but it cannot confirm that every old save has automatically recovered.

For a crash, record the event or screen where it happens and any graphics setting involved. For a ship clipping issue, note the region and ship route. For a construction message, check whether the issue matches the fixed Pirate Camp or Drifter message before assuming that your production chain is broken.

What the patch notes do not confirm

The collected official notes do not provide a complete list of every balance change, map change, or community-requested feature. They also do not verify a universal trainer, cheat code, House of Fortune solution, best map, or best ship. Those search topics need their own sources and should not be filled with guesses from unrelated patch posts.

The latest verified version in this research is the captured Patch #2 label. A newer update may exist after the retrieval date, so current status is To be confirmed until the live Steam News hub is checked. Keep the official Steam News page as the authority for future additions.

Track a patch against your save

Write down the version shown by Steam before troubleshooting and keep the save's origin clear. A save from the demo, an older full release, or a build with a mod can produce different behavior from a clean current installation. The collected notes do not guarantee that an old save is repaired automatically after a patch.

After updating, reproduce the issue with the same map, event, ship, or construction screen. If the problem disappears, keep the original reproduction details so the fix can be explained without claiming that every related bug is solved. If it remains, compare it with the exact changelog wording and report the difference.

Check the official news hub again

Patch pages can be followed by hotfixes or platform-specific changes that are not present in an older capture. Use the official Corsair Cove Steam News hub and the game's current version display as the live check. Search pages, SteamDB mirrors, videos, and forum comments are useful leads, but the official changelog should decide what is presented as a confirmed fix.

Record the date you checked the hub when maintaining this guide. That keeps the difference between a captured historical note and the current update status visible to readers. Any release after the captured Patch #2 is To be confirmed until the official page is reviewed.

Direct answer for players

For the collected release notes, Patch #1 covers tutorial hints and event progression, and Patch #2 covers crashes, ship clipping, crew-upkeep display, Pirate Camp messaging, visual scenes, and localisation. Demo updates are separate from the full release. The latest captured official full-game entry is Patch #2 v1.1.2.241844.

If you are troubleshooting, match your product and version first, then compare the issue with the official changelog. Save compatibility, newer patches after the capture, and the effect on an old campaign are To be confirmed until checked against the current Steam News entry. Keep the exact version and reproduction details with the save so a later update can be checked against the same state.