Interrogate Anyone

The gardener says he spent the whole evening in the greenhouse. And you know — the cook mentioned it an hour ago, mid-complaint about mud on her kitchen floor — that the greenhouse path flooded at dusk. Anyone who walked it came back filthy. The gardener's boots, drying by the door, were clean.

The question assembles itself in your head, whole and sharp: then why were your boots dry?

And the game offers you three buttons. Ask about the victim. Ask about the will. End conversation.

This is the quiet failure of almost every game where you interrogate suspects. The genre promises you the detective's chair, then hands you a laminated card of approved questions. A real interrogation game would let you ask the question you actually composed — the one built from your own noticing, your own memory, your own sense of the exact moment to spring it. Anything less is not interrogation. It is a quiz where the suspect already knows the answers you're allowed to want.

What a game where you interrogate suspects usually gets wrong

To be fair to the genre: the menu exists for a reason. Handwritten dialogue is expensive, and a designer can only script so many branches. So most detective games converge on the same compromise. You gather evidence, and the evidence unlocks topics. Present the torn letter, and a new line appears in the dialogue tree. Find the pawn ticket, and the shopkeeper suddenly has more to say.

Played generously, this can still be satisfying. The best of these games hide real craft in which topics unlock when, and there's a genuine click of pleasure when the option you were hoping for finally appears.

But notice what has actually happened. The game did the detective work. It decided which facts mattered, which pairings of evidence and suspect were meaningful, which questions were worth asking. Your job was reduced to inventory management: carry the right object to the right person and press the button the designers left for you. When the option you want appears in the list, it isn't confirmation of your deduction — it's a spoiler. The list itself tells you what the game considers relevant, which is half the mystery given away in the interface.

And when your deduction doesn't match the script — when you've noticed something the designers didn't flag, like dry boots on a flooded path — the game simply has no ears for it. You sit there holding a genuinely good question, and the machine shrugs.

Composing the question is the detective work

Here is the claim worth slowing down for: in detective fiction, the interrogation question is not how you deliver the deduction. It is the deduction.

Think about what has to happen in your head before why were your boots dry? can exist. You have to hold two testimonies in mind at once — the gardener's account of his evening and the cook's throwaway complaint. You have to notice that they can't both be true, which means you have to have been listening to the cook at all, an hour ago, when nothing seemed to be at stake. You have to convert the contradiction into a question narrow enough that it can't be wriggled out of. Were you really in the greenhouse? invites a simple yes. Why were your boots dry? invites a lie you can catch, because you know about the mud and he doesn't know you know.

That whole chain — retention, collision, formulation — is the pleasure of the detective story. It's what the great fictional interrogators actually do on the page: they hoard trifles, wait, and then ask one small precise question that lands like a trapdoor opening. The question is small because the thinking behind it was large.

A menu amputates that chain at every joint. It remembers for you, collides the facts for you, phrases the question for you. What's left is the button press — the one part of the process that was never the point. This is the same hollowness we've written about in games where choices carry real weight: a choice you didn't compose is barely a choice at all.

Timing is a weapon you can't hold in a dialogue tree

There is a second thing menus destroy, subtler than the first: the when.

Any interrogator, fictional or otherwise, will tell you that a contradiction is a one-use weapon. Spring it too early — before the suspect has committed to the lie, before he has repeated it, elaborated it, built his little house on it — and he simply amends his story. "Did I say the greenhouse? I stepped out for a while, of course." The contradiction dies with a shrug, and worse, he now knows what you know.

The move, instead, is to let him talk. Ask the soft questions first. Let him volunteer detail after detail about an evening he never spent among the tomato vines — what he pruned, what he heard, when he came in. Every specific is another nail in the floorboards. Then the boots.

A dialogue tree cannot give you this, because a dialogue tree has no meaningful order. The three buttons sit there simultaneously, patient, interchangeable. Asking about the will before the alibi changes nothing; the suspect's responses were written independently and will be delivered independently. But in a real interrogation — and in a story that actually behaves like one — sequence is everything. The same question is a blunder in minute two and a checkmate in minute ten. A game that wants to deserve the word interrogation has to make the order of your questions matter, which means it has to let the suspect actually live through the conversation rather than dispense it.

Press wrong and the door closes

And then there is the cost — the thing almost no detective game models at all, because a menu-driven suspect is infinitely patient. You can ask the widow the same three questions forty times. You can accuse the vicar, be wrong, and accuse him again after lunch. Interrogation without social cost is target practice against a wall.

But asking is an act, and acts have consequences. Accuse the housekeeper on a hunch and watch her go stiff and formal, answering in monosyllables for the rest of the case — and telling the other servants, so that doors all over the house swing a little more shut. Press a grieving man too hard, too early, and lose the one witness who was actually inclined to help you. The detective's real constraint was never the evidence. It was that every question spends something: goodwill, surprise, the suspect's belief that you know less than you do.

This is what would make accusation thrilling rather than free. In a game where you can accuse anyone, at any moment, in your own words, the accusation should be a cliff-edge — because if you're wrong, you can't unsay it. The room remembers.

Interrogation as free action

All of this points at one design conclusion: interrogation only becomes real when the question is a free action — composed by you, in your words, at the moment you choose.

That is how it works in Runebook, an AI story game where the Storyteller runs the world and you act by typing what you want to say or do. There is no list of approved questions. In a mystery, you ask the gardener about his boots because you noticed the boots; the Storyteller carries the scene forward from there, and the story remembers what matters — the lie he told in the kitchen is still a lie three scenes later, waiting for you to collide it with something. You can circle a suspect gently, or go straight at her and live with how the room turns. You can accuse anyone. You can be wrong.

Scenes come with narration read aloud and imagery to set the room; you can work a case alone or bring friends in to play the bad cop, and it runs in your browser, with the story remembering where you were when you come back to it. If solitary sleuthing is the appeal, we've written a fuller picture of playing a murder mystery you can run entirely alone, and the AI murder mystery game page shows how a case takes shape from the first body to the drawing-room reveal.

The perfect question is already forming in your head. Somewhere there's a suspect who hasn't heard it yet.

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