BeSpoke Engine, today

Where the engine stands on 13 November 2026, written for people who will play with it, test it, or build on it. No background in programming languages needed.

13playable demo games
11of them also play in a web browser
562automatic checks, all passing
0outside libraries in the core

What it is

BeSpoke is a toolkit for making story-driven adventure games, the kind where you walk characters around rooms, pick things up, talk to people, and solve puzzles. Think of the classic point-and-click adventures, with one difference: the world keeps running on its own. Characters have routines, they notice things, they react to each other, and a puzzle can be solved in ways nobody wrote down step by step.

It comes in two parts. One is a small, readable writing language for describing a game: who is in a room, what they do, what they say, and what happens when something changes. The other is the program that reads that writing and runs it as a game, in a desktop window or in a web page.

What it can do

Run a living world

Tell a story

Play with time

Make sound and music

Help the people making the game

How it does it

Four simple ideas carry nearly everything.

1. The world is a notebook of facts

Everything true about the game is written as a short line: "Guard carries Cheese", "Bard charmed Guard (until 2 minutes from now)". There are no hidden objects with private settings. To ask a question, the engine reads the notebook. Because the whole world is one notebook, saving a game or rewinding it is copying the notebook (with a checksum to catch damage), which is why rewind is quick and exact.

2. Time moves in ticks

The game moves forward in small, counted steps (ticks), like the hand of a clock. Nothing depends on how fast your computer is. Given the same start and the same button presses, the game plays out identically every time, which makes replays, rewinds, and testing reliable.

3. Characters have to-do lists

Each character runs a routine, a list of things to do, which can pause ("wait 5 ticks", "wait until the door is open"). When something important happens, the routine is set aside, the interruption runs, and the routine resumes. Writers describe behaviour in the order it happens, without building complicated state machines.

4. Pictures and sound only watch

The window, the web page, and the speakers never decide anything. They look at the world each tick and draw or play what they see. The same game therefore runs in a desktop window, in a browser, or with no screen at all (handy for automatic testing).

Underneath, the engine is written in a language called Zig. It turns game scripts into a compact internal form and runs them quickly, with nothing borrowed from other engines.

Why we made it

Most game tools fall into two camps. Big engines (Unity, Godot, RPG Maker) are built around graphics and physics, and story logic gets bolted on as small scripts scattered across objects. General programming languages give you total freedom but make you build all the plumbing yourself: timers, save systems, state tracking, cleanup.

Story and simulation games need different things at their core: a clear record of what is true, characters that act over time, rules that react, and the ability to save or rewind without bugs. BeSpoke puts those at the centre and treats graphics as a window onto them.

The inspirations are the deterministic simulations of RollerCoaster Tycoon, the actor-and-cue design of the old Sierra and LucasArts adventure engines, and the emergent relationships of Dwarf Fortress. The goal is whimsical, systemic games where puzzles fall out of how the world works, and where the writer spends time on the story instead of on plumbing.

How to make a game with it

  1. Create a project. Run bespoke init my-game. You get a folder with a starter story, a test file, a desktop version, a web version, and a setup for automatic builds on Linux, Mac, and Windows (written, not yet run).
  2. Write the story in scripts/main.bespoke. Describe the rooms, the characters, their routines, the conversations, and the rules. A small example:
    scene Tavern:
      cast: Guard, Bard, Cat
      marks: Hearth, Bar, Cellar
    
    routine Patrol(Guard):
      walk Guard to Cellar
      wait 5 ticks
      walk Guard to Hearth
    
    when Carries(Cat, Cheese):
      interrupt Guard with:
        face Guard toward Cat
        wait 2 ticks
  3. Check it. bespoke check points at mistakes. Running the game "headless" prints what happens, line by line, without opening a window.
  4. Play it in a window with zig build run.
  5. Lock it in with tests. Write a short check for each puzzle ("after these steps, the door is open"), so later changes cannot quietly break it.
  6. Share it. Build one program file for players, or a web version for a website.

The authoring guide in the repository (docs/AUTHORING.md) walks through a scene, a conversation, and a puzzle, and every example in it is tested automatically. The full language reference is script_spec.md.

The demo games

DemoWhat it showsBrowser
The Tavern HeistA cat steals cheese while a bard distracts the guard; no cutscene, just rules reactingYes
The Pip-Spitting GreenRigging a fair contest with a conch, moved pegs, and a thick treacle ciderYes
The Borrowed BeardA disguise built from items gathered across three scenesYes
The Living VillageSix villagers living their days; theft, gossip, and an arrest emerge on their ownYes
The Donkey of Lamp PointGetting past a donkey by tangling its ropeYes
The Well of Three TidesThree characters in three centuries passing items through a wellYes
Caustic GrogCarrying grog that eats through its cups, pouring before each failsYes
Brackwater BarbsDuels won with comebacks you learn by hearing themYes
Algiers: Three PathsOne puzzle, three approaches; choosing one closes the othersYes
The Copper WeathercockA temporary copy of the world on a countdownYes
The Bell TowerSpells played as four-note tunes; backwards, they do the oppositeYes
The Castle Fire EscapeFire, smoke, and water spreading room by roomNot yet
The Larkspur ObservatoryStaff with their own agendas who intercept you; typed commandsNot yet

Several demos borrow situations, characters, and lines from classic adventure games and a film. They are being rewritten one at a time as original stories that show the same engine features (Phase 35 in the roadmap).

What it cannot do yet

Most of these are listed as Phase 34 in the roadmap, alongside the hand-testing pass; the rewrite of borrowed demos is Phase 35.

For testers

Every feature above has automatic checks, but none of it has been played by hand at length. That is the next job. The step-by-step guide is docs/runbooks/release-hand-test.md in the repository: it lists what to try in each demo, what you should see and hear, and a table to record results. A full pass takes about four hours; a useful short pass (the basics, the desktop demos, the browser, and a listening check) takes about ninety minutes.

Anything odd is worth writing down with the demo name and roughly when it happened. Every run plays the same way, so a problem you can describe is a problem that can be reproduced and fixed.