What's new
Each release, newest first: what changed and what it means for you, in the words its changelog uses. Storyletter shows the same list in its What’s New dialog. The full notes, with every detail, are on GitHub Releases; the installers and runtime zips are on the Download page, and what a version number promises is on Versions and compatibility.
Storyletter
Section titled “Storyletter”The desktop editor. Its What’s New dialog (Help menu) shows the same list in the app.
1.4.0 (17 November 2026)
Section titled “1.4.0 (17 November 2026)”- A template hand’s slots can be unbounded. On a hand made from a template, Slots now offers as the template, unbounded, or a count, so one hand can hold everything while the others keep the template’s cap.
Fixed:
- A slot count that isn’t a whole number is a problem.
1.3.0 (12 November 2026)
Section titled “1.3.0 (12 November 2026)”- A calmer welcome. With no project open, Storyletter shows its name, a few buttons, and your recent projects, and nothing else. The first time, it starts you off with The Hamlet. The kits and examples are all in New Project.
- What’s new waits until you ask. After an update nothing opens over your work: a “What’s new” button in the top bar opens a short list of what changed, with a link to the full notes.
1.2.0 (11 November 2026)
Section titled “1.2.0 (11 November 2026)”- A field can take any name, and suggests the ones you’ve used.
- A page shows the extensions you use, and Add offers the rest.
- An extension’s settings are easier to read.
- Extensions in plain words. File > Extensions says which installed version of an extension this project uses, and says what the project loses before you uninstall that one.
1.1.0 (10 November 2026)
Section titled “1.1.0 (10 November 2026)”- Extensions can tuck their extra fields away.
- Patterplay 1.0.1 inside: joining strings with
+now fails in Play, as it already did when compiling. Text built from pieces can’t be translated, so put the value into the line’s own text instead. - What’s New tells you more about each change.
1.0.0 (8 November 2026)
Section titled “1.0.0 (8 November 2026)”- Your work is safe across updates: a project from an earlier Storyletter opens in 1.0, and a bundle you publish today will play in every Storylet Engine 1.x to come.
- Version numbers now tell you what an update does: 1.0.1 and 1.0.2 are fixes, 1.1 and 1.2 add things without taking anything away, and only a 2.0 may change how something you rely on works.
- Two old settings are gone: a card’s Copies, which Across hands replaced, and map positions kept in a box’s view file. A card that still has Copies shows a problem saying how to clear it.
0.28.1 (6 November 2026)
Section titled “0.28.1 (6 November 2026)”Fixed:
- The Full release notes link in What’s New works: it opens the release page in your browser. It did nothing before, because Storyletter only let its About links open in the browser.
0.28.0 (6 November 2026)
Section titled “0.28.0 (6 November 2026)”- A game catches up when it connects: a game that says hello over Live Link on an older build (one started from an older bundle, or back after edits) is sent the current bundle straight away, rather than at the next save.
- Live Link now shows when the game runs unpublished edits. While the connected game runs edits Live Link pushed that you haven’t published, the Live Link icon says Unpublished edits, as Patterpad’s does. It clears once you publish the bundle.
- Patterplay 0.46.0 inside, playing a card’s Patter scene on the Board and in an exported playable page, in place of 0.45.0. Nothing changes how a scene plays.
- Show Scene in Patterpad finds Patterpad without stalling. It looks where you last pointed it, then the usual places, and only then searches the Mac, as Patterpad finds Storyletter, so Storyletter no longer stalls when Patterpad isn’t installed.
- A game reconnects by itself when Storyletter comes back. Every engine’s Live Link client tries again when Storyletter restarts or turns its link on after the game started (1 second, doubling to 10).
Fixed:
- Live Link recognises an in-sync game when the project uses Patter. A project paired with Patter used to show every game as a different build, so the icon stayed red however in sync the game was.
0.27.4 (5 November 2026). Patterplay 0.45.0 inside, playing a card’s Patter scene on the Board and in an exported playable page, in place of 0.38.0. Full release notes.
Earlier Storyletter releases are on GitHub Releases.
Storylet Engine
Section titled “Storylet Engine”The four runtimes (JavaScript, Unity, Unreal, Godot) share one version and move together; each runtime’s zip carries its own notes.
1.1.0 (17 November 2026)
Section titled “1.1.0 (17 November 2026)”- A hand can set its own slots to unbounded.
1.0.3 (15 November 2026)
Section titled “1.0.3 (15 November 2026)”- Nothing new in this runtime. 1.0.3 is the Godot runtime’s fix (a C# game no longer crashes as it quits), released in lockstep so every runtime keeps one version.
1.0.2 (12 November 2026)
Section titled “1.0.2 (12 November 2026)”- The play helpers work with app-shell 2.0 as well as 1.x (
@storylet-studio/play-helperstakes@wildwinter/app-shell>=1.0.0 <3.0.0), so a game that also uses Patter’s play helpers, or Storyletter’s own tree, installs one copy of it. The runtime itself is unchanged.
1.0.1 (10 November 2026)
Section titled “1.0.1 (10 November 2026)”+on two strings is now an error at play, as it already was at compile. Text built from pieces can’t be translated, so put the value into the line’s own text instead.
1.0.0 (8 November 2026)
Section titled “1.0.0 (8 November 2026)”- Every 1.x plays the bundles and loads the saves you have today. From 1.0.0 a patch fixes, a minor adds, and only a major may change behaviour your game relies on, with its notes saying what and why.
- Runs on the same shared libraries as Patter 1.0, so a game with both still holds one expression registry.
@wildwinter/exprand@wildwinter/expr-specificityare^1.0.0, and the@wildwinter/scoperegistrypeer is>=1.0.0 <2.0.0, the same range as Patter 1.0’s.
0.17.0 (6 November 2026)
Section titled “0.17.0 (6 November 2026)”- A game’s Live Link reconnects by itself, on every runtime. Restart Storyletter, or turn its Live Link on after the game has started, and the Board and live edits come back by themselves. In JS it’s
@storylet-studio/play-helpers’createLiveLink.
0.16.0 (5 November 2026)
Section titled “0.16.0 (5 November 2026)”- Your code can read which Storylet Engine version it runs on, so a game, a tool or an extension that ships apart from the engine can check it at start-up.
0.15.0 (29 October 2026)
Section titled “0.15.0 (29 October 2026)”- Your game hears what a refitting load put back.
EngineOptions.onRefit(misfits)hears each saved value a refitting load puts back to its default, so a drifted save is never silent. - Property paths can be written in Patter’s form too.
getPropertyandsetProperty, on the engine and on a flow, take a leading@, as Patter’s do. - Declare game scopes of your own, not only world. A project can declare its own scopes beside
@world(@player, say), in Patter’s shape: a token, a scope-levelwritable, and declarations, or none for an opaque scope that takes any name. - The engine reports a mistake in how it was set up. As the constructor ends,
onErrorhears aPlayErrorofkind“setup” for a host scope the bundle doesn’t declare or an option it doesn’t take. - Discard a card from a hand without playing it.
discard(card, hand)takes it out when the player turns it down or the game wants the room. There’s no outcome, no move of the clock, and nothing in the play log. - Weight, In one hand and Across hands replace copies, for finer control over how a card is dealt.
- Your game can move a box’s clock. A box with
turnand nosecondsadvances nothing on a play, as a timed box doesn’t: a calendar, ticked by the game. - Your game hears about a condition that failed. A condition the engine can’t evaluate still counts as false, and now also reaches
EngineOptions.onError, whether or not anything is tracing. - The bundle, save and load report types are exported, so a game can type what it hands the engine and what a load hands back without depending on the model package. They are
Bundle,SaveEnvelopeandLoadReport. - One engine option now binds every game scope. The
worldoption has gone: bind@worldand any other scope the bundle declares throughhostScopes, one map of token to resolver. - Bundles move to a new format version, and older ones still load. Bundles are
storylets/bundle@2: the game’s scopes arescopeRegistry, and theworldblock is gone. - A deal now puts the best eligible cards in the hand. A deal ranks everything eligible, including what the hand holds, and the hand becomes the top of that ranking, full or not.
- A load drops a held card that no longer qualifies. A save made before a content edit could put back a card whose condition the edit made false, and nothing said so.
- A card made again keeps its place in a save. Saves now name cards by Game ID, so a card deleted and made again under the same Game ID keeps its place, its cooldown and its play count.
Fixed:
- A load checks the hand against the saved world, not the old one, so a held card gated on @world isn’t dropped for a world the save no longer has.
- A refitting load keeps “none chosen”. A saved
""on an enum whose own default is""(none chosen) now comes back as saved, instead of being reported as a misfit that never happened. - A host write must fit what the content declared.
setPropertyrefuses a value the property doesn’t take, and says what it takes. - A broken bundle or save says what’s wrong with it.
new Engine(null), a bundle missing its boxes, or a save with the wrong schema used to fail as a raw TypeError; each now says what it got and what’s missing. - Changing a dealt card no longer changes the bundle. A dealt card’s fields, an outcome’s, and a field’s structured default are copies now.
Earlier Storylet Engine releases are on GitHub Releases.
Open source under the MIT licence, made by Ian Thomas.