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
Contents
- Where can you write?
- Writing in the phone app
- Web editor: the Write tab
- — The Map tab
- Script format
- — Scene format
- — Scene types
- — Dialogue rules
- — Choices and effects
- — Conditions
- — Router scene
- — Stats and the approval system
- — Full example
- — Common mistakes
- Tablet and desktop app: Form and Blueprint
- Live Story
- Publishing and community rules
- Frequently asked questions
- AI prompt (for generating a script)
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.
/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.
The quick path to your first story
- My Stories → Write a New Story → Full Story. Your email address must be verified.
- 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.
- Write the intro, add at least two choices to the first choice scene and link each one to a scene.
- 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
- Scenes are grouped by part: Intro, Part 1, Part 2… You can rename the part label in the story settings (for example "Week" or "Day").
- "+ Add scene to this part" and "+ Add part" create new scenes and parts.
- Each card shows the scene's title, first line, type and line/choice counts.
- A colored dot shows the scene's status: green is fine, yellow is a warning (for example, no next scene chosen), red is an error (for example, a link to a scene that doesn't exist). A short description of the problem appears under the card.
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.
- Above the composer at the bottom are speaker chips: Narrator, You (the reader's own line), the characters already in the story, and + Character. Pick a chip, type, and press send (or Enter on the keyboard); the line is added to the scene.
- Bulk paste: if you paste lines like "MERT: Hello" one under another, each one goes to the right character; lines without a prefix go to the selected speaker.
- Tap a line to edit it in the composer. Long-press it to move it up or down, add a condition, or delete it.
- Conditional line: if you add a condition to a line (for example, a flag is true), the line is only read when the condition holds.
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.
- Tap the target to open a list: pick an existing scene, or use "Create a new scene and link it" to open a new scene, titled with the choice's text, in one tap.
- When there is more than one choice, you can leave one open; in a Live Story readers vote on it.
- Choice-less scenes (Intro, Interlude, Chapter Summary) have a single "Then" target. If you leave it empty, the reader continues to the next scene in order; choosing it explicitly is still safer.
- Router (ROUTER) scenes have ordered routes instead of choices; each route is a condition and a target.
Effects and conditions
The "Effects & Conditions" link under each choice opens a panel:
- Feedback: a short message shown after the choice.
- Approval change: plus or minus on the general relationship score (if the story uses approval).
- Stats: plus or minus on the stats you defined (for example, courage +3).
- Flags: true/false markers to check later (for example,
toldTheSecret = true). - Conditions: when the choice is available (a flag, a stat threshold or an approval range). If the condition isn't met, the choice appears locked.
- Outcome dialogue: a few lines read right after the choice.
Story settings and advanced options
- Story settings: starting stats (key, label, starting value), the part label, whether readers enter their own name (and if not, a fixed name), and whether the stats bar is shown while reading.
- In a scene's Advanced section you can change its type, ID and part number, or delete the scene.
- "Edit as script" in the menu opens the story as plain text; the script format below applies here too. "Editor tour" in the same menu walks you through the screens.
- Your work is kept on the device as a draft. If you close the app without saving, the next time you open it you're asked "You have an unsaved draft".
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.
- On a computer the scene list is on the left and the open scene on the right. On a phone you see the list first, and tapping a scene opens its page.
- The line look and the composer are the same as in the app: pick a speaker chip, type, and press Enter to add. Shift+Enter starts a new line inside the same line. Bulk paste works here too.
- Click a line to edit it; the ⋯ menu on its right has move, condition and delete.
- Choices, the target picker, "Effects & Conditions", routes and the "Then" target work just as in the app.
- The menu next to the scene title sets the scene type; the Advanced button manages the ID, part number and links.
- The Script tab shows the whole story as plain text. The symbol bar at the top inserts characters such as
#,>,->,[ ]and{ }with one click. When you're done, press "Apply to form"; the text becomes scenes.
Drafts, import/export and templates
- Your work is saved in the browser automatically ("Saved" appears at the top). If there's an unsaved draft when you reopen the page, you're asked whether to continue it.
- Saving to the server happens in the Publish panel: Save draft stores the story on the server without publishing, Publish opens it to readers (see Publishing).
- The ⋮ menu has story settings, Import JSON, Download JSON and a link to this guide. JSON is handy for backing up a story or moving it to another device.
- For a new story you can pick a template: Romance Story, Medieval Adventure and Text-Based RPG.
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.
- Drag a card to move it. Drag empty space to pan the map.
- To connect, drag from an exit dot and drop it on another card.
- Drop it on empty space and a new scene is created there and linked; the choice's text becomes its title.
- To remove a link, click the arrow and press Delete (or use "Remove link" at the top).
- Double-click a card to open the scene in the Write tab. With a card selected, Edit, Duplicate and Delete appear at the top.
- The mouse wheel or a two-finger pinch zooms; "Fit" fits the whole story on screen, "Auto layout" arranges the cards left to right along the flow.
- Arrow colors show the type: green for a choice, blue for "Then", orange for a router route. A dashed arrow shows where readers go from a scene with no next scene set: the next scene in order.
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
| Field | Description |
|---|---|
key | Used in effects/conditions: {courage+5}, [stat:courage>=30] |
| Label | The name shown to the player |
| Starting value | Value at the start of the game, usually 0-100 |
Stories that don't use stats simply skip these lines entirely.
4.2 Scene Types
| Type | Usage |
|---|---|
INTRO | The first scene. Only one exists. Ends with -> firstScene. |
MAIN | Choice scene. At least one > choice is required; 2-4 choices are recommended for a real branch. |
INTERLUDE | A choice-less transition/atmosphere scene. Ends with -> nextScene. |
WEEK_SUMMARY | End-of-part recap. No choices, links to the next part's first scene. |
ROUTER | A content-free branching point. Routes based on the approval score or a stat/flag. |
ENDING | A final scene. No choices. Ends with -> credits. |
CREDITS | A single credits scene. Every ending links here. |
>) 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):
- Use lowercase letters and underscores:
b1_s1,b2_int_a b{part}_s{order}→ MAIN scenesb{part}_int_{letter}→ INTERLUDE scenesb{part}_summary→ WEEK_SUMMARYb{part}_router→ ROUTERending_a,ending_b,ending_c… → Endingscredits→ fixed, single scene
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 syntax | Description |
|---|---|
{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
| Syntax | Description |
|---|---|
[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
- The most critical mistake: writing
MAINwithout any>choice (the editor shows a red error) or giving anINTERLUDEscene choices (they don't work there). The rule is simple: choices present → MAIN, none → INTERLUDE. - Writing narrative text inside a ROUTER scene — it should only contain
?lines. - Using inconsistent scene IDs — this breaks links.
- Forgetting to add the
creditsscene. - Leaving out the
-> creditslink on an ending scene. - Linking every choice to the same target — this creates no real branching and makes no difference to the reader.
- Writing
@stat:lines inside scenes — they must only appear at the very top of the file.
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
- The screen is split in two: on the left the scene list grouped by part (with colored status dots), on the right the selected scene's fields.
- Scene ID (lowercase and underscores, e.g.
b1_s1), type, title, narration and dialogue lines, choices (text, target, effects, condition), the next scene for choice-less scenes, and route lines for routers are separate fields. - Every field is validated: a broken link or a missing choice is flagged immediately. You can finish a whole story in this mode without knowing the script syntax.
Blueprint
- The story appears as a visual map: each box is a scene, arrows are links. A box's color shows the scene type.
- Drag from the ports on a box's edge and drop on another box to create a link.
- Boxes with a red border are unreachable scenes: nothing links to them, so readers can never get there.
- Double-click a box to open a large window with all of the scene's fields: scene info, dialogue lines and links. If you try to close it with unsaved changes, the app warns you.
- Drag to pan, use the wheel or a pinch to zoom; buttons reset the view or recompute the layout.
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.
- Story details: title, description, tags, language, cover and the AI-assisted flag.
- Intro: the opening of your story; it has no choices.
- 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).
- Start and publish the story. Readers read it and vote at the decision point.
- 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.
- 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.
- Publish the chapter. Readers who follow the story are notified of the new chapter.
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.
- The publish panel has the cover (up to 5 MB), title, description, tags (comma-separated), language (TR, EN, RU), estimated reading time and the AI-assisted flag.
- Save draft stores the story on the server without publishing, so you can continue on another device. Publish opens it to readers. Changes to a published story go live with Update.
- Use the My Stories page to unpublish or delete a story.
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 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]