ExcitingPress ReviewInteractive fiction · gamebooks

Archive

Every article, in reading order

Articles appear here on their publication date. The number is their position in the reading list, not a ranking.

  1. Reading a Branching Narrative: What the Passage Structure Tells You

    How to read an interactive story as a structure rather than a plot — passages, links, hidden state and endings — and what to check before you decide a branch is broken.

    Structure & Craft

  2. What a Save File Actually Remembers About Your Choices

    Saving looks like a pause button, but in an interactive story it is a snapshot of hidden state. Here is what that means for undo, for re-reading, and for the branch you thought you closed.

    Saving & Re-reading

  3. Knots, Diverts and Stitches: A Reader's Guide to Ink Scripts

    You do not need to program to read an ink script. Here are the four marks that carry almost all of its structure, explained from the official writer's manual.

    Tools & Platforms

  4. From Sugarcane Island to The Cave of Time: How the Gamebook Form Was Assembled

    The numbered-paragraph book looks like a single invention. The documented history shows it was assembled from two separate ideas: a branching text and a tabletop rule set.

    History & Industry

  5. Choosing a Twine Story Format Without Regretting It Later

    Harlowe, Chapbook, SugarCube and Snowman are not skins for the same engine. The official Cookbook describes them as dialects with different limits, and the choice is hard to undo.

    Tools & Platforms

  6. The Z-Machine and Glulx: Why Text Games Still Ship as Virtual Machines

    Infocom's 1979 design kept stories separate from the machine that ran them. Two virtual machines later, the same trick is what lets a text game keep working on hardware nobody planned for.

    History & Industry

  7. Who Keeps Text Games Alive: The Institutions Behind the Archive

    Text games outlived the companies that sold them because a set of institutions took custody of the archive, the catalogue, the competition and the authoring tools.

    History & Industry

  8. What the "64K limit" in the Z-machine actually limits

    The standard sets story files at 128K, 256K or 512K depending on version, yet speaks of a 64K limit. A table separating the two figures, with the arithmetic and what moved authors to Glulx.

    History & Industry

  9. A 400-section budget: how many choices can a gamebook afford?

    Fighting Fantasy-style books are built from about 400 numbered sections. A calculation shows why a pure branching tree runs out of pages after a handful of choices, and how bottlenecks fix it.

    Structure & Craft

Back to the cover