6.5 Patch History
There is no patch-notes list on this page, and that is not an omission waiting to be filled. Letters of Marque does not publish a numbered changelog, so an honest patch-history page has to explain where change information actually lives rather than invent a version table.
6.5.1 No published changelog
The game is distributed as a Steam playtest under active solo development. Builds go out when work is ready, and Steam applies them quietly in the background. There is no changelog on a store page, and no news feed of the kind a released game usually carries.
There is, however, a patch-notes channel on the official Discord, and it is the closest thing to a changelog the project has. Entries are versioned — v0.5.13, for instance, is the build that added repairs — and short, sometimes listing the balance figures a change shipped with. They are not exhaustive: not every build is announced, and a note describes what the developer chose to mention rather than everything that moved.
So a change can still reach your installation with no document describing it. If something behaves differently from the way a page here describes, a build update is the most likely explanation rather than an error in the original observation — though both are possible, and both are worth reporting.
6.5.2 Where changes are actually announced
Five places carry change information, each with different reliability:
| Where | What it tells you | Limitation |
|---|---|---|
| Developer devlogs | What was worked on, in the developer’s own account, often with the reasoning | Mixes released work with plans; not tied to a build |
| Development board | Tasks moving to completed, and current priorities | A completed task does not say which build contains it |
| Discord patch notes | That a specific version shipped a specific change, with the date and sometimes the balance figures | Not every build is announced, and notes are brief rather than complete |
| Community Discord | The fastest notice that something changed or broke | Informal; player reports may be mistaken or specific to one machine |
| Your Steam client | That an update was downloaded, and when | Says nothing about what the update contained |
Used together these are workable. The Discord tells you something moved, the devlogs and board tell you roughly what, and the game itself tells you the truth. Links are on Useful Links.
6.5.3 Working out what changed since you last played
A practical routine when returning after a break:
- Let Steam finish updating before drawing any conclusion. A good deal of apparent breakage is simply an old build.
- Read the newest devlog, then skim back to roughly when you stopped playing.
- Check the development board’s completed work over the same period.
- Open your controls menu. Bindings are the change most likely to catch you out, and the menu is authoritative.
- Dock and read your ship’s stat sheet before sailing anywhere valuable. Balance changes show up here first.
- Test in something you can afford to lose. Turning, stopping, and gunnery are all worth re-learning after a long gap.
6.5.4 What this Guide records instead
In place of patch numbers, every page carries the date its claims were last verified, and pages written by observing the game name the day the build was examined. That provides the one thing a version number would have given you: a way to judge whether a statement is likely still true.
The most recent Guide-wide observation of the client was 28 July 2026. Pages describing the interface, default controls, ship stat fields, market structure, and sign-up were checked against the build available that day. Anything about them that no longer matches your game changed after it.
For the longer story of how the game reached its present state — a different question from what changed last week — see Dev History.
Sources & Credits
This page draws on facts from, and gratefully credits: Letters of Marque — Official Patreon Developer Posts · Letters of Marque — Official Development Trello · Letters of Marque — the Steam playtest client · Letters of Marque — the official community Discord. Prose is original; see how this guide is made.