Short scenarios Contents

Building a world

Short scenarios

Small worlds with an end: Play it now from one sentence, the Scenario tab, play switches, countdowns and meters, how a story ends, tables and publishing.

A story you can finish

A short scenario is a small world with an end: most often one town, a premise with a twist, a truth the player finds out, and two or three ways it can end. Players find them on the Short scenarios page, pick one, and play it to an ending in an evening.

Each play is a private table of its own, so every player's story is theirs: what they change, who they win over and how it ends stay at their table. Friends can join a table by invite and share the story.

The storyteller tells it, but the engine keeps the parts that decide it: the day, the counts the scenario keeps, which endings can still be reached, and when the story is over. Engine

Making one

There are two ways in, both from the box at the top of the Short scenarios page, and the Studio for everything after.

Play it now

Type one sentence: who you are, or what is going on. In about a minute Worldtable has drafted a town with its people and their secrets, a few ways to begin and a few ways it can end, and seats you at a table of your own to play it.

A sentence
You run a tiny ramen stall in a rainy harbour town for one week; if the stall still stands on Sunday night, it is yours for good.
A harbour town with its regulars, a landlord with plans for the corner, a countdown to Sunday night, and endings for keeping the stall and for losing it. The first scene opens at the counter.
  • A draft costs 5 credits. Nothing is charged if it can't be written.
  • Not what you meant? Before your first turn, Not quite? Change it drafts it again with your words (1 credit); anything you don't mention stays as it is.
  • A story made this way is yours and unlisted. Each account keeps up to 20 of them, apart from the worlds it builds.

Build it in detail

For a scenario others will play, use Build it in detail in the same box: give it a name and a sentence, and the Studio opens with a draft written from it for you to change. Every part is yours to rewrite before anyone plays.

In the Studio itself, the new-world wizard has A short scenario from one sentence, and any world can become one on its Scenario tab. More on the wizard and the Studio in Making a world.

The scenario page

Everything that makes a world a scenario is on its Scenario tab. Every part is optional, and a world that sets none of it plays as usual.

Premise
What the story is. Left blank, the world's own premise is used.
How it works
The rules of the twist: what the powers do, what the future knowledge covers. Write limits and costs only if you want any.
What's really going on
For the storyteller only: who did it, what the town hides. Players never see it; they find it out in play, from signs first, never the fact handed over.
When it begins
The part of the day the story starts at. A night that runs until dawn begins in the evening; every character starts on it, and the first scene is written at it. Left out, stories begin in the morning.
At the edge of town
One line: what happens when someone tries to leave a world that is one town (the road floods, the ferry has gone). It can end the story with one of its endings, and only when leaving is the player's own choice.
Endings
Each has a title, a line saying in plain words what has happened when the story ends this way, and an epilogue (left blank, the storyteller writes one from the story). Tick Only a plugin ends it this way for an ending a plugin of yours decides, and the storyteller never reaches it by itself. Without any endings, the story never ends by itself.

To make the whole world one town, use One town on the Map tab: players see only its town map. Every place is in the town, or is one of the few landmarks you place around it, which the town map points to with how far each is. A place none of the town's kinds is (someone's house, a clinic) goes under Its own places on the town's card.

Play switches

Which parts of the game the scenario plays with. Left as they are, it plays like any other world.

Fights
Off: no fight system. Violence is told in the story, never fought out, and no health is shown.
Money
Off: no purse, prices or markets, and travel is free.
Limits
Anything goes: the player's powers and claims are not held to the world's scale. For a premise like waking up with superpowers.
What drives the story
Where the pressure comes from: situations, story arcs and encounters as in any world; only this page; or nothing unless the player asks for it.

What the story keeps count of

A scenario can keep a deadline, a meter, a time loop or rounds by the numbers, set on the Scenario tab. The player sees each one by its name, as a chip under the story's header, and the storyteller is told where it stands. Engine

KindWhat it doesGood for
CountdownComes on a day of the story, at a part of the day. When it comes the story ends with an ending, or something happens and the story goes on.The ferry on day 4, the vote on day 8, Sunday night
MeterA number from 0 to its top, moved after each scene by what the scene shows. At the top (or, for one that runs out, at 0) the story ends with an ending.Suspicion that fills, stores that run out, a crowd's mood
Time loopThe same day again, from late in the day or when something happens, with a count of the loops. A reset is never an ending.Waking in room 6 at midnight, again
RoundsA contest in rounds, each set with its right answer: the player's answer is judged against it, so it can be wrong. With wrong answers to lose set, it is first to either: enough right wins at once, enough wrong loses at once.A game show, a trial in stages, a riddle contest
The four kinds. A one-sentence draft switches on the ones its premise needs.

How a story ends

A scenario ends in one of three ways:

  • The scene reaches it. After each scene, from the fifth on, the storyteller's judge reads whether the story has reached one of the endings as they are written. Storyteller
  • The player leaves. Leaving town by their own choice, when the edge line names an ending.
  • A count or a plugin decides it. A countdown coming, a meter at its top, or a plugin that ends the story itself. Engine
  • A death. On the ending the player's death should bring, tick The player dying ends it this way: the story ends there the moment they die (or, in a world where nobody dies for good, the moment they fall), whatever scene it is. Engine

Then the end screen plays, for everyone at the table:

  • The ending's title and its epilogue, the builder's or written from this story.
  • The endings found so far: the player sees the ones they have reached, and the rest stay hidden until they do.
  • Play again starts a new table of the same scenario, with a new character.
  • Keep playing goes on from where it ended, with no ending left to reach.

Undoing the turn that ended the story takes the ending back, along with anything that turn set off.

Playing at a table

Every play of a scenario is a private table: a copy of the world for the people at it, so nothing one player does reaches another's story. The scenario's own page, cast and endings come from the world; everything that happens is the table's.

The player who starts the table can invite others to share it, and the ending is the whole table's. More in Playing together.

Publishing

Publish a scenario as you would any world, then tick List it on Short scenarios, with a public page on the Players tab. Only scenarios with at least one ending are listed there; its public page shows the town plan and the premise, never the truth.

A one-town world with no endings is open-ended: it is an ordinary world, listed in the worlds directory like any other. Who pays for play is the same as for any world: Players, keys and costs.

Plugins for a scenario

When the four counts aren't the game you want (a case board to pin clues to, a planning window before a heist, the town's trust in a new witch), a plugin can do it. Ask Hob in plain words. What a plugin can read and do in a scenario:

  • wt.scenario.page() reads the scenario page: premise, rules, the truth (for judging, never to show a player), the endings and which ones only a plugin reaches, the switches, the counts, and the ending this story has reached.
  • wt.scenario.end(character, id) ends the story with one of its endings, once, for the whole table. Undo takes it back.
  • byPlugin on an ending keeps the storyteller's judge off it: set it on every ending a plugin decides, the Scenario tab's Only a plugin ends it this way.

An ending a plugin calls before the scene is told (a vote that falls due as a turn begins) makes that turn's scene the last one: the storyteller is told to play how it comes, and the end screen follows the scene. From a button, the story ends at once, so say what happens in the ending's epilogue.

Hob plays a plugin through before you see it, as a careful, a careless and a breaking player, and fixes what they break. More in Hob writes them for you · The plugin API.