The Game That Answers Whatever You Type

Try this. You are in a story set in a drowned fishing village, standing over the body of a man everyone insists fell from the cliffs. The obvious moves are laid out for you: examine the body, question the widow, climb the cliff path. Instead you type: I sing the old net-mending song my mother taught me, to see who in the crowd knows the words.

That is the whole test of a game that responds to whatever you type. Not whether the box accepts the sentence — any text box accepts any sentence — but what comes back.

Here is the short version of what this essay argues. A game that responds to whatever you type is only as good as its answers, and a real answer has to pass three tests: it must be specific to what you actually did, consistent with everything that came before, and consequential for everything that comes after. "You can do anything" is a claim about the input box. The claim that matters is about the world.

Now watch the two ways the singing can go.

The cheap answer: You sing a song. The villagers look at you strangely. The investigation continues. Do you want to examine the body or question the widow? Your action was absorbed, padded, and returned to you as lint. The words "net-mending song" appear nowhere. The crowd is a crowd. The game has quietly told you the truth about itself: the box was open, but nobody was listening.

The real answer: an old woman near the back mouths the third verse before catching herself — the verse only menders from the northern coves would know, and she told you an hour ago she'd never left this village. The widow doesn't sing, but the dead man's brother does, too loudly, the way a man sings when he wants to be seen singing. And the story remembers that you did this — that you are the kind of investigator who tests a crowd with a song instead of a badge — which will matter later, when someone decides whether you can be trusted with the thing they've been hiding.

The difference between those two answers is the difference between a gimmick and a game.

What a game that responds to whatever you type owes you

The promise of typing anything is old. Text games have offered an open input line for decades, and every generation of them has run into the same wall: the input was open but the world was narrow, so most sentences hit the wall and bounced. You can't do that here. The fantasy was a conversation; the reality was a lock and a hundred keys that didn't fit.

The newer promise — a story that genuinely improvises — swings at the opposite wall. The world says yes to everything, floridly, and the yeses don't add up. You can do anything, and therefore nothing you do means anything.

So it's worth being precise about what responsiveness actually is. It is not permissiveness. It is craft, and it has three parts.

Specific: the answer is to your action, not the category of your action

Take the singing again. "You sing a song" answers the category — a Sound Was Made. The real answer engages with the particulars: this song, this mother, this crowd of people who may or may not know a mender's verse. A useful test for any story game: swap your action for a neighboring one — hum instead of sing, a hymn instead of a work song — and ask whether the response would change. If any sentence in the same genre would have earned the same paragraph, the game is answering categories. You wrote a specific sentence; you are owed a specific reply.

Specificity is also why open input beats a menu at its own game. A menu of four options can be brilliantly written, but the four options are the author's guesses about you. The sentence you typed is not a guess. It carries your logic, your suspicion, your mother's song — material no menu could have predicted, and material a real answer can actually use.

Consistent: the answer honors what came before

An improvised world with no memory is a hall of one-way doors. The village that was starving in one scene throws a feast in the next; the man you saved denies knowing you; the knife you pocketed evaporates. Each individual scene may read beautifully. The story is still broken, because a story is not a sequence of scenes — it's a ledger.

Consistency is where "respond to anything" gets genuinely hard, because every new answer is constrained by every old one. The woman who mouthed the third verse is now, permanently, a woman who lied about the northern coves. A world that keeps that ledger honestly is doing something much rarer than generating prose. It is the same discipline that makes a story with meaningful choices meaningful at all: a choice only weighs something if the world is still carrying it much later.

Consequential: the answer changes what comes next

The third test looks forward. A specific, consistent answer that alters nothing is a well-written cul-de-sac. If the crowd's reaction to your song is vivid but the investigation proceeds exactly as it would have — same suspects, same doors, same ending — then your action was flavor, not play.

Consequence is the whole reason to want a story with no predetermined ending: not because "anything can happen," but because what happens next is downstream of what you actually did. The song opened a door the badge never would have. Some other door quietly closed. That's what it feels like when a world takes you seriously.

Where "anything" should fail

Here is the uncomfortable part of the promise, and the part worth defending: a game that responds to whatever you type must sometimes respond with resistance.

Suppose, standing over the body, you type: I raise the dead man and ask him who did it. If you're playing a necromancer in a story where the dead can be questioned, wonderful — that's the genre keeping its word. But if you're a village schoolteacher in a grounded mystery, a world that shrugs and hands you a talking corpse has not been generous. It has told you the setting was scenery. Nothing you do in a world like that can matter, because the world has no shape for your actions to press against.

The real answer to the impossible move isn't a flat refusal, either — you can't do that is the old wall again. It's the world responding in character: you kneel, you say the words half-remembered from a book you shouldn't have read, and nothing happens except that the sexton saw you try, and now the village has a second mystery. Your action was impossible and it still left a mark. That is resistance as craft: the no is specific, consistent, and consequential too.

The same goes for out-of-character moves. If the story has established you as someone, the world is entitled to notice when you act like someone else — not to stop you, but to react to the swerve as a swerve. Friction is not a limit on the promise. Friction is the evidence that there's a world on the other side of the input line. This is the quiet contract behind any story where you're truly the main character: protagonists are made by what pushes back.

How Runebook plays it

Runebook is an AI story game built around exactly this contract. The Storyteller runs the world — the drowned village, the crowd, the woman who knows the verse — and you act by typing what you want to say or do, in your own words. You can take a suggested action when one fits, or speak your move aloud, but the open line is the heart of it: the sentence you'd actually write, answered on its particulars.

And the story remembers what matters. The lie about the northern coves, the song, the sexton who watched you kneel — the ledger stays open across scenes, so consequences can arrive late and land. Stories come with narration read aloud and scene imagery, in fantasy, mystery, romance, horror, historical, manga-style, sci-fi and more — or a custom story spun from your own idea. Play solo, or bring friends into the same world and let the Storyteller answer all of you at once. It runs in your browser, and when you step away, the story remembers where you were.

Bring it a strange sentence. See what comes back.

Create an account and start your first story — it's included. Start your story