DriftNov
EN

How to Write a Story

A guide to writing branching stories on DriftNov: the phone app, the web editor (Write, Script, Map), Live Stories and the script format

This guide explains how to write and publish your own interactive story on DriftNov. You can write in the phone app, in the tablet or desktop app, or in the web editor on driftnov.com. They all edit the same story, so you can start in one and continue in another.

1. Where can you write?

There are three ways to write on DriftNov. Pick the one that fits your screen and habits; the story lives in one place on the server, so you can switch between them at any time.

Phone app — writing in the flow You open a scene from the scene list and its lines look just like the reading screen. In the composer at the bottom you pick a speaker and type; each line drops into place right away. You set up choices and links by picking from a list, without typing scene IDs.
Website — Write, Script and Map driftnov.com → My Stories → Write a New Story (or go straight to /write). On a computer the scene list sits on the left and the open scene on the right; the Map tab shows the whole story as cards and arrows that you drag and connect. On a phone, the list and the scene become separate pages.
Tablet and desktop app — Form, Script and Blueprint The wide-screen app keeps the classic three modes: Form, edited field by field; Script, plain text; and Blueprint, a visual map. Details in the dedicated section.
There are two kinds of story. A Full Story is written from start to finish, with all its branches, and published at once. A Live Story is written chapter by chapter: readers vote at decision points and you continue with the winning choice (see Live Story). You choose one of these when you create a new story.

The quick path to your first story

  1. My Stories → Write a New Story → Full Story. Your email address must be verified.
  2. Pick a template (Romance Story, Medieval Adventure, Text-Based RPG) or start with a blank page. Templates are a good way to see how scenes and choices connect.
  3. Write the intro, add at least two choices to the first choice scene and link each one to a scene.
  4. Write your endings. When no scene has a red dot, press Publish.

2. Writing in the phone app

On a phone the editor has two screens: first the scene list, and when you tap a scene, the scene itself. The idea is that you can write the story the way readers will see it, without typing code or IDs.

The scene list

Writing lines

On the scene screen, lines look just like the reading screen: narration is a plain paragraph, and dialogue has the character's name in color above it and a thin colored line on the left. There are no chat bubbles; while you write, you see the story the way your readers will.

Choices and targets

Below the lines you see where the scene leads. In a choice scene (MAIN) these are the choices; each has a text and a target.

Effects and conditions

The "Effects & Conditions" link under each choice opens a panel:

Story settings and advanced options

3. Web editor: the Write tab

On driftnov.com, My Stories → Write a New Story (or driftnov.com/write directly) opens the web editor. There's nothing to install; being signed in on the site is enough. The editor has three tabs: Write, Script and Map.

Drafts, import/export and templates

The Map tab

The Map shows the whole story as cards and arrows. Each card is a scene; the dots on a card's right edge are the exits for its choices, its "Then" and its routes. The Map only opens on a wide screen (at least 900 pixels); on a phone, use the Write tab.

Card positions are saved with the story. If you edit the story in the app and come back to the web, the map is just as you left it; resizing the window or zooming never pulls the arrows away from the cards.

4. Script format

In Script mode you see and edit the whole story as plain text. This is the fastest method for experienced writers — especially when drafting a long story from scratch. Script changes are not applied automatically; when you're done, press "Apply to form" and the editor parses the text into scenes.

Script exists both in the app and in the web editor. The keyword for the reader's own lines is PLAYER: (if you write YOU:, you get a character named "You"). The intro scene's part number is 0; the editor shows those scenes under "Intro".

4.1 Scene Format

Every scene starts with the following pattern and ends with ---:

# sceneId | TYPE | part | Title
Narrative text here. Setting, atmosphere, character actions.
CHARACTER: A line of dialogue.
PLAYER: What the player says.
> Choice text -> targetSceneId
> Choice text [condition] -> targetSceneId
-> autoTargetSceneId

---

The part field is an integer. The intro scene uses 0, followed by 1, 2, 3… The editor uses this number to know which part a scene belongs to.

If your story uses a stat system, add stat declarations at the very top of the script (before any # scene):

@stat: courage | Courage | 10
@stat: empathy | Empathy | 15
FieldDescription
keyUsed in effects/conditions: {courage+5}, [stat:courage>=30]
LabelThe name shown to the player
Starting valueValue at the start of the game, usually 0-100

Stories that don't use stats simply skip these lines entirely.

4.2 Scene Types

TypeUsage
INTROThe first scene. Only one exists. Ends with -> firstScene.
MAINChoice scene. At least one > choice is required; 2-4 choices are recommended for a real branch.
INTERLUDEA choice-less transition/atmosphere scene. Ends with -> nextScene.
WEEK_SUMMARYEnd-of-part recap. No choices, links to the next part's first scene.
ROUTERA content-free branching point. Routes based on the approval score or a stat/flag.
ENDINGA final scene. No choices. Ends with -> credits.
CREDITSA single credits scene. Every ending links here.
Rule: choices (>) only work in MAIN scenes. Make a scene with choices MAIN and a choice-less transition scene INTERLUDE. A MAIN scene with no choices is marked as a red error in the editor.

Scene ID conventions (recommended):

4.3 Dialogue Rules

# Character dialogue — uppercase name, colon
LEA: I'm so tired today.
MARK: Nah, you're always like that.

# Player dialogue
PLAYER: I get it. Go on.

# Narration — no prefix, plain text
The classroom slowly empties out. You look toward the window.

# Using the player's name
MARK: Hey, {playerName}! So you're here.

4.4 Choices and Effects

# Basic choice
> Choice text -> targetSceneId

# Choice + approval effect
> Choice text -> targetSceneId {approval+10}

# Choice + stat effect
> Choice text -> targetSceneId {courage+5, empathy+3}

# Choice + flag effect
> Choice text -> targetSceneId {flag:joinedGroup=true}

# Choice + condition (locked in the UI if not met)
> Choice text [stat:empathy>=40] -> targetSceneId {approval+15}
Effect syntaxDescription
{approval+10}approval score +10
{approval-5}approval score -5
{statName+3}that stat +3
{flag:joinedGroup=true}set the flag to true
{approval+10, empathy+2, flag:planReady=true}multiple effects, comma-separated

4.5 Conditions

SyntaxDescription
[stat:statName>=40]that stat must be at least 40
[flag:joinedGroup=true]the flag must be true
[approval:60-100]approval score must be between 60-100

Choices whose condition isn't met appear locked to the player and can't be selected.

4.6 Router Scene

A ROUTER scene has no choices or narrative — only an ordered list of lines starting with ?. The engine checks them top to bottom and jumps to the target of the first matching condition.

# b2_router | ROUTER | 2 | Fork in the Road
? flag:joinedGroup=true -> b2_s1_group
? flag:joinedGroup=false -> b2_s1_library

---

# b4_router | ROUTER | 4 | Final Decision Path
? approval:70-100 -> b4_s4_high
? approval:40-69 -> b4_s4_mid
? approval:0-39 -> b4_s4_low

One ROUTER can chain into another to evaluate complex conditions in stages — for example, check a flag first, then branch on approval score.

4.7 Stats and the Approval System

Approval: A single, general relationship/approval score (0-100), used in ROUTER as approval:X-Y. Available automatically in every story.

Stats: Story-specific values, and you can have several (e.g. a mystery might use intellect, observation, persuasion; an adventure might use strength, courage, instinct). Declared at the top of the script with @stat: lines and shown as a bar on the part-summary screen.

Undeclared (hidden) stats: Internal counters used only in effects/ conditions without an @stat: declaration — they are never shown to the player as a bar. Useful for hidden tracking, e.g. "how many clues collected":

> Choice B -> b1_s2 {clue+15}
> Choice C [stat:clue>=30] -> b1_int_special

4.8 Full Example

@stat: empathy | Empathy | 10

# intro | INTRO | 0 | Beginning
-> b1_s1

---

# b1_s1 | MAIN | 1 | Day One
September. A new city, a new job. You step into the office for the first time.
Someone is watching you from across the desks: Ava.
AVA: Are you the new hire?
PLAYER: Yeah, first day today.
> "Getting lost isn't bad — that's why I came to explore." -> b1_int_a {approval+10, empathy+5}
> "It'd be easier if you helped me out." -> b1_int_b {approval+5}
> Just smile, sit down, say nothing. -> b1_int_b {approval-5}

---

# b1_int_a | INTERLUDE | 1 | Lunch Break
Lunch break. You've drifted to the window, holding your coffee.
-> b1_s2

---

# b1_int_b | INTERLUDE | 1 | A Different Break
You run into Ava in the hallway during lunch.
AVA: So, how's the job treating you so far?
-> b1_s2

4.9 Common Mistakes

5. Tablet and desktop app: Form and Blueprint

When you open the app on a tablet or in a wide window on a computer, the editor comes with the classic three modes: Form, Script and Blueprint. All three edit the same data and you can switch between them at any time.

Form

Blueprint

Blueprint is especially useful for finding an unreachable scene, checking that a part really has two different paths, and spotting choices that accidentally all lead to the same scene. The Map tab on the web does the same job in the browser.

6. Live Story

In a Live Story you don't write the whole story up front. You publish each chapter, readers vote at the decision point, and you write the next chapter with the winning choice. It has its own editor: in the app, My Stories → Write a New Story → Live Story; on the web, driftnov.com/write/live.

  1. Story details: title, description, tags, language, cover and the AI-assisted flag.
  2. Intro: the opening of your story; it has no choices.
  3. First scene: a title, lines and at least two choices for readers to vote on. You can add an image to the chapter (up to 5 MB).
  4. Start and publish the story. Readers read it and vote at the decision point.
  5. When you reopen the editor, previous chapters appear read-only, followed by the open vote with each choice's percentage. Pick the choice you'll continue with.
  6. New chapter: write what happens after the winning choice. The chapter is either a new decision point (again with at least two choices) or a scene that ends the story.
  7. Publish the chapter. Readers who follow the story are notified of the new chapter.
Published chapters can't be changed later, because readers voted on them. Reader comments appear in the Reader comments section at the bottom of the editor, grouped by scene.

7. Publishing and community rules

The Publish button checks the story first. If any scenes are marked red (error) or yellow (warning), you get a list; tap an item to open that scene. You can continue with errors, but readers may get stuck on a broken link.

Every story you publish must follow the Community Guidelines. DriftNov is open to readers aged 13 and over; any sexual content involving minors is strictly forbidden. Tick "AI-assisted" for stories you wrote with the help of AI. Content that breaks the rules can be reviewed and removed after a report.

8. Frequently asked questions

Where should I start?
On a phone, start with the editor in the app; on a computer, start with the web editor's Write tab. When the branches multiply, the Map tab makes the flow easier to see. If you had an AI write the story, paste it in with Script.

Why don't my Script changes show up?
Script changes aren't applied by themselves; you need to press "Apply to form".

Can I continue on the web a story I started in the app?
Yes. Save it to the server in the app with Save draft or Publish, then open it from My Stories on the web. It works the other way too.

How many parts or scenes should I write?
There's no limit; you can write a short one-part story or a long multi-part novel. What matters is that the choices in each choice scene really lead to different content.

What's the difference between approval and stats?
Approval is a single, general relationship score built into every story. Stats are story-specific values you define yourself, and you can have several.

Can readers enter their own name?
Yes. If "readers enter their name" is on in the story settings, readers type their name at the start and {playerName} in the text is replaced with it. If it's off, the fixed name from the settings is used.


AI Prompt

AI Prompt for Generating a Script

Paste the text below as-is into an AI chat tool (ChatGPT, Claude, etc.) together with your story's premise. This isn't a prompt tailored to any specific story — it's just the general rules that define the DriftNov editor's script format. Simply replace the topic placeholder with your own premise.

You are an interactive/branching story script writer. Following the format below
WITHOUT ANY EXCEPTION, write a complete story script based on the premise I give you.

GENERAL STRUCTURE
- Every scene starts with "# sceneId | TYPE | part | Title" and ends with "---".
- The "part" field is an integer: 0 for the intro scene, then 1, 2, 3, ...
- If the story uses stats, add declarations at the very top of the file (before any
  "#" scene):
  @stat: key | Label | starting_value
  If the story doesn't use stats, skip these lines entirely.

SCENE TYPES (only these seven types exist, do not invent new ones)
- INTRO        : Exactly one, part=0. No choices. Ends only with "-> firstSceneId".
- MAIN         : 2-4 "> ..." choices are REQUIRED. Never write MAIN without choices.
- INTERLUDE    : Has NO choices. Ends only with "-> nextSceneId".
- WEEK_SUMMARY : End-of-part recap. No choices, links to the next part's first scene.
- ROUTER       : Contains NO narrative or dialogue. Only "? condition -> target" lines.
                 The engine checks them top to bottom and jumps to the target of the
                 first matching condition.
- ENDING       : No choices. Ends only with "-> credits".
- CREDITS      : Exactly one, at the very end of the script. Has no outgoing link.

STRICT RULE: if a scene has any ">" choice its type MUST be MAIN; otherwise it MUST
be INTERLUDE. There is no exception to this rule.

WRITING DIALOGUE
CHARACTER: Character name in uppercase, a colon, then the dialogue line.
PLAYER: What the player says.
Lines with no prefix are narration/description text.

CHOICES AND EFFECTS (only inside MAIN scenes)
> Choice text -> targetSceneId
> Choice text -> targetSceneId {approval+10}
> Choice text -> targetSceneId {statName+5, flag:flagName=true}
> Choice text [stat:statName>=40] -> targetSceneId
> Choice text [flag:flagName=true] -> targetSceneId
> Choice text [approval:60-100] -> targetSceneId

ROUTER CONDITION LINES (only inside ROUTER scenes)
? flag:flagName=true -> targetSceneId
? stat:statName>=50 -> targetSceneId
? approval:60-100 -> targetSceneId

MANDATORY RULES
1. Scene IDs use lowercase letters and underscores (e.g. b1_s1, b1_int_a) and must
   be unique.
2. Every MAIN scene's choices must lead to at least 2 different target IDs. If all
   choices lead to the same scene, that's invalid — rewrite it.
3. Every ENDING scene must end with "-> credits".
4. The script must contain exactly one CREDITS scene.
5. "@stat:" lines appear ONLY at the very top of the file; never inside a scene.
6. A ROUTER scene must NOT contain narrative text or dialogue, only "?" lines.
7. Every "->" target and every choice target must point to a real scene ID that
   exists in the script — never leave a broken link.

OUTPUT FORMAT
Produce a complete, playable script that strictly follows the rules above. Do not
add any explanation, commentary, or markdown code fences outside the script —
output only the script text itself.

Now write a story for the following premise:
[WRITE YOUR TOPIC / CHARACTERS / THEME HERE]
↑ Back to top