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.
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
- Characters walk between spots in a room or across rooms, finding their own way.
- Each character can follow a routine ("walk to the cellar, wait a while, walk back") and be interrupted when something more urgent happens, then pick up where they left off.
- Rules watch the world and fire when something becomes true: "when the cat is holding the cheese, the guard turns to look".
- Things can be temporary: a distraction that lasts ten seconds, a smell that fades, a fire that burns out.
- A whole village can run itself: people get hungry and tired, work, trade, steal, gossip, and a sheriff makes arrests, without anyone scripting each event.
Tell a story
- Branching conversations where the options depend on what you know or have done.
- Characters who believe, doubt, or reject what they are told.
- Several scenes and rooms, several playable characters, and items passed between them (even between time periods, in one demo).
- Characters with their own goals who come and find you when you threaten them.
- Typing commands such as "take the slip" or "ask pell about the slip", alongside clicking.
Play with time
- Rewind at any moment and watch the world replay exactly the same way.
- Scrub backward and forward through recent history, like a video.
- Save and load to slots, each with a small picture of the moment.
- Run a temporary "what if" copy of the world that either merges back or collapses.
Make sound and music
- A built-in synthesizer plays retro-style music and sound effects, with no sound files needed.
- Music can be written as short lines of notes inside the game script, and changes with the scene.
- One demo uses musical notes as spells: play four notes on a staff and the world changes.
Help the people making the game
- One command creates a new, ready-to-run game project.
- A checker reports mistakes in a script with the line and column.
- A "state inspector" shows everything the world currently knows, as a map of who relates to what.
- A game can be packed into a single program to hand to players, or built for a web page.
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
- 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). - 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 - Check it.
bespoke checkpoints at mistakes. Running the game "headless" prints what happens, line by line, without opening a window. - Play it in a window with
zig build run. - 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.
- 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
| Demo | What it shows | Browser |
|---|---|---|
| The Tavern Heist | A cat steals cheese while a bard distracts the guard; no cutscene, just rules reacting | Yes |
| The Pip-Spitting Green | Rigging a fair contest with a conch, moved pegs, and a thick treacle cider | Yes |
| The Borrowed Beard | A disguise built from items gathered across three scenes | Yes |
| The Living Village | Six villagers living their days; theft, gossip, and an arrest emerge on their own | Yes |
| The Lochmarne Goat | Getting past a goat by tangling its rope | Yes |
| Day of the Tentacle Trio | Three characters in three eras passing items through time | Yes |
| Caustic Grog | Carrying grog that eats through its cups, pouring before each fails | Yes |
| Brackwater Barbs | Duels won with comebacks you learn by hearing them | Yes |
| Algiers: Three Paths | One puzzle, three approaches; choosing one closes the others | Yes |
| The Middlesex Anomaly | A temporary copy of the world on a countdown | Yes |
| The Bell Tower | Spells played as four-note tunes; backwards, they do the opposite | Yes |
| The Castle Fire Escape | Fire, smoke, and water spreading room by room | Not yet |
| The Larkspur Observatory | Staff with their own agendas who intercept you; typed commands | Not 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
- Graphics are simple. Rooms, people, and objects are drawn as shapes and labels by code. There is no way yet to load your own artwork or sprite images.
- Nobody has listened to the sound on real speakers. It has been checked by measuring the sound waves, not by ear.
- Mac and Windows are untested. The automatic builds for them exist but have never run.
- The public website is uploaded by hand. A tool prepares the page; nothing in the repository publishes it.
- In the browser, two demos are missing and typed commands do not work.
- Small writing gaps: inside an event handler, a placeholder such as
victimis not yet filled in with the actual character (conditions on the handler now are), and clicking a person in the basic window does not start a conversation (type "talk to" instead). - Once you choose a path in a multi-path puzzle, you cannot switch.
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.