This page tracks updates for the released Corsair Cove base game on Steam, AppID 1368140. As of 2026-08-02, the newest verified base-game milestone is the 1.0 release on 2026-07-31. No later official base-game patch note was found in the Steam sources checked for this page.
That last sentence is deliberately narrow. It does not claim that no depot build, hotfix, support reply, or community observation exists. It means this tracker will not promote a numerical BuildID, a Demo announcement, or an unsourced player report into a public base-game patch label.
Current status at a glance
- Current public label: 1.0
- Base-game AppID: 1368140
- Public release date: 2026-07-31
- Newest verified base-game news item: the 1.0 release announcement
- Later base-game patch note found through 2026-08-02: none in the official Steam sources checked
- Separate Demo AppID: 3858730
Use the Steam store and the base game’s Steam news hub as the primary current sources. The official Hooded Horse wiki is useful for system explanations, but it is not a substitute for a dated patch announcement.
Update timeline
2026-07-31 - Corsair Cove 1.0 released
Type: Release
Corsair Cove left its pre-release window and launched as the public 1.0 base game on Steam. The store identifies the release date as 2026-07-31 and lists the developer as Limbic Entertainment and the publisher as Hooded Horse.
For players, this milestone is the reference point for building connections, resources, Crew and Cohesion, ships, the Compass, and the published system requirements. Those systems should be read as 1.0 behavior unless a later official note identifies a change.
The release also separates base-game support from Demo history. A player troubleshooting the retail installation should report AppID 1368140 and should not assume a Demo update title or Demo BuildID identifies the same files.
Source: Official Corsair Cove Steam store
Why the Demo update is not a base-game patch
Steam exposes a separate Corsair Cove Demo under AppID 3858730. Official search results and news history can surface Demo Update #1 from 2026-06-10. That item predates the retail release and belongs to the Demo product scope.
It is valid historical evidence about the Demo, but it must not be placed after the 1.0 launch as if it were the latest base-game patch. If a future official post applies to both products, this page should record that shared scope explicitly rather than inferring it from a similar title.
The same rule applies to saves and requirements. A Demo installation may have different files, lifecycle, compatibility test, and upgrade behavior. Always check the AppID before copying a fix or changelog detail.
How to tell whether a patch applies to your game
A candidate update should have a dated, attributable source and a clear product scope. The strongest evidence is a post in the base game’s official Steam news feed or another developer or publisher channel that names Corsair Cove and describes the released game.
When reading a new announcement, compare:
- The publication date and the date the change became available, if those differ.
- The exact public label used by the developer, such as 1.0 or a named patch.
- Whether it applies to base game 1368140, Demo 3858730, a beta branch, or more than one product.
- Platform scope when the note is limited to Windows, Steam Deck compatibility, or another environment.
- The direct source and the player-facing changes it actually describes.
- Any remaining uncertainty, especially when a fix is described without reproduction conditions.
A news title alone can establish that an announcement exists, but detailed mechanical claims should come from the body of the official note or a reproducible in-game check.
BuildIDs are evidence, not version names
SteamDB and similar databases can show when a depot build changed. A BuildID helps compare delivery state across machines and can support a troubleshooting report. It does not explain what changed, prove that a player-facing patch was published, or replace the developer’s semantic version label.
For example, a large numerical BuildID must not be presented as “Corsair Cove version 23854077.” The public label remains 1.0 until an official source establishes a different label. Steam Deck test metadata tied to a BuildID is also a compatibility observation, not a native Linux release announcement.
What to recheck after an official patch
An update can affect several guide areas even when its title sounds narrow. Review the patch against this checklist:
- Building: camp reach, road and pier connections, worker assignment, Fetcher behavior, production speed, building costs, and defensive effects.
- Economy: construction inputs, intermediate chains, upkeep, Coin flow, storage, and resource conversion.
- Crew: recruitment, job capacity, Crew thresholds, satisfaction, Cohesion gains or losses, and firing penalties.
- Fleet: ship tiers, pier requirements, allowed crew, costs, upkeep, movement, combat roles, and hybrid unlocks.
- Progression: Compass tier gates, point requirements, automatic ship unlocks, buildings in each bundle, and quest rewards.
- Troubleshooting: minimum or recommended requirements, startup behavior, save compatibility, Steam Cloud, controllers, and Steam Deck status.
Do not assume every system changed merely because Steam downloaded a new build. Match the official note to the affected areas, then recheck those mechanics in the stated version and platform context.
What players should record before updating
Steam normally manages the live build automatically. If a campaign or technical problem matters to you, preserve useful context before changing settings or resolving a cloud conflict:
- Note the public version wording in the main menu and the date.
- Record the Steam AppID and whether the installation is base game or Demo.
- Back up important saves when possible without overwriting the affected copy.
- Capture the current Compass unlock, Crew and Cohesion state, active quests, ships, and the exact building or production symptom.
- Write down custom launch options, compatibility settings, and controller layout.
- After the update, test the same state before making unrelated changes.
This creates a before-and-after comparison. It is much stronger than attributing every difference noticed later to the newest download.
Sources and confidence labels
This hub uses three practical evidence labels:
- Official: the Steam store, the base game’s Steam news feed, or a clearly identified Limbic Entertainment or Hooded Horse channel supports the claim.
- Third-party observation: a database such as SteamDB records delivery or compatibility metadata. Useful, but not a semantic changelog.
- Needs current verification: a player report, behavior visible in only one save, or a value that no checked official source presently confirms.
If an official wiki and the running game disagree, record the date and the exact mismatch. The live 1.0 interface is relevant evidence for immediate play, while the official page may need an update. Neither justifies silently inventing a patch number.
No later base-game patch note was found as of 2026-08-02
The official base-game Steam store and news destinations were checked through 2026-08-02. The latest verified base-game milestone remained the 2026-07-31 launch. This is a dated observation, not a permanent claim.
When a later official base-game patch appears, compare its date, AppID, branch, platform, and named changes with this launch entry. The older release remains useful history, while the newer official post becomes the relevant source for systems it explicitly changes.
What is the current Corsair Cove version?
The latest public version label verified from official sources is 1.0, released on 2026-07-31. A Steam BuildID is not used as the public version name.
Was Demo Update #1 released after launch?
No. The official Demo update item verified as of 2026-08-02 is dated 2026-06-10, before the 2026-07-31 base-game launch. It belongs to Demo AppID 3858730.
Does a new Steam download prove that mechanics changed?
No. It proves that Steam delivered files. Use an official changelog or a controlled comparison before asserting a specific gameplay change.
Where should I report a launch problem?
Start with the Troubleshooting hub and include the AppID, system information, exact failure stage, and reproduction steps when using an official support channel.
Why is the 1.0 launch still the newest base-game item here?
No later official base-game patch note was found in the Steam sources checked through 2026-08-02. Demo news, depot BuildIDs, and community observations do not replace a dated base-game announcement, so the 1.0 launch remains the newest verified item for AppID 1368140.
Sources
- Corsair Cove on Steam, checked 2026-08-02 for AppID, release date, developer, publisher, features, and public requirements.
- Corsair Cove Steam news hub, checked 2026-08-02 for official base-game announcements.
- Corsair Cove Demo on Steam, checked 2026-08-02 to keep Demo scope separate.
- SteamDB: Corsair Cove, checked 2026-08-02 as third-party build and compatibility metadata only.