Premise, plot, and setting
Traditional adventures often begin with a plot: scenes the party is expected to visit in a particular order. Bunnyland works better when you begin with a situation: people, places, resources, and pressures that can produce several plausible sequences.
Write a playable premise
A strong premise answers six questions in a few sentences:
| Question | Lantern Ferry answer |
|---|---|
| What is normal here? | A lantern-guided ferry connects the village to the marsh road. |
| What changed? | Floodwater extinguished the lantern and damaged its wick. |
| Who needs something? | Rowan needs to carry medicine across; Sable needs the ferry reopened. |
| What resists them? | Supplies are divided between people who do not trust one another. |
| What happens with no intervention? | The crossing stays closed and the delivery is late. |
| What can reveal a deeper truth? | A ledger contradicts the story behind an old broken promise. |
This is plot material without a prescribed plot. A player might bargain for oil, steal it, repair the lamp another way, reconcile the storekeeper and ferrymaster, or abandon the ferry and search for another route.
Separate truth, belief, and possibility
Keep three columns in your design notes:
- World truth is authoritative state: the lamp is unlit, the oil flask is in the store, the west route is closed.
- Character belief belongs in biography, dialogue, gossip, or memory: Sable believes the storekeeper broke their agreement.
- Open possibility is not yet state: perhaps the ledger will lead to reconciliation.
Do not encode a hoped-for outcome as if it already happened. Likewise, do not put secret truth into every character biography. A character can only reason from facts their projection and memories actually provide.
Design pressures instead of scene order
Use a pressure when you want the setting to keep asking a question:
- a deadline, season, tide, shift, or approaching storm;
- a scarce tool, resource, safe room, or route;
- incompatible goals held by different characters;
- a need that grows over time;
- a public institution or faction enforcing a rule;
- a promise, debt, or injury that cannot be ignored forever.
Tie each pressure to mechanics only when the passage of time or a state transition matters. “Before moonrise” is flavor until world time, light, a due epoch, or an event makes moonrise observable. Flavor is valuable, but do not claim that it is enforced.
Give the setting a usable identity
Write setting material at three scales:
- World promise: the kind of stories the setting reliably supports.
- Regional contrast: why one district, biome, deck, or faction territory differs from another.
- Room texture: what someone can perceive and interact with now.
For Bracken Reach:
- World promise: ordinary rural obligations become strange at the edge of an uncanny marsh.
- Regional contrast: the village is social and rule-bound; the marsh is isolated and shaped by weather and old infrastructure.
- Room texture: wet rope, a dark lantern housing, high water marks, an oil smell, and a ledger with a torn page.
Avoid spending all your detail on world history. Players and agents act on nearby facts. Every paragraph of lore should eventually influence a choice, interpretation, relationship, route, or object.
Establish tone without forcing behavior
Tone comes from consistent evidence: names, descriptions, resources, consequences, and how characters respond. It should not require every controller to narrate in the same voice.
For a hopeful folk-horror tone, make the marsh unsettling but the people capable of repair. The lamp can fail, rumors can distort the past, and the flood can isolate the village, while food, shelter, honest records, and reconciliation remain possible.
Use world policy for actual content boundaries. Use persona fields for a character's voice and role. Do not bury safety rules in a biography or hope that a prompt adjective will enforce them.
Draft a consequence map
Before creating entities, sketch causes and visible results:
| Cause | Immediate result | Persistent evidence |
|---|---|---|
| Lantern is repaired | crossing can reopen | lamp state and ferry notice change |
| Medicine arrives | recipient can recover | delivery ledger records receipt |
| Ledger is read | old story becomes questionable | reader can remember or repeat the fact |
| Promise is fulfilled | obligation closes | status and relationship can change |
| Nobody acts | tide or deadline advances | route remains closed; needs and pressure grow |
This map reveals which ideas need real components, relationships, handlers, scripts, or events. It also prevents the common mistake of letting narration announce a change that the world never records.
Static-pass checklist
- The premise describes a situation, not one mandatory solution.
- Important facts are classified as truth, belief, or possibility.
- At least two characters want things that can come into tension.
- The setting supports the promised kind of play at room scale.
- Any enforced deadline or scarcity has corresponding state.
- Major outcomes have persistent, inspectable evidence.
Next, turn the setting into a navigable graph in Regions, rooms, and routes.