FURINACLANK CHAT ATELIER
DOCUMENTATIONStory Tools
Browse Guides
STORY TOOLS

Don't just remember the story. Organize it.

Furina's story tools keep track of where a scene is, what changed, what happened before it, and where you might want to return later.

Scene State, recaps, timelines, snapshots, bookmarks, chapters and Story Bibles are stored on Furina's side of the experience. They organize your roleplay without rewriting Clank's backend conversation.

Think of this as the story's production notebook.

Director tells the AI how to play the scene. Continuity preserves important facts. Story Tools preserve structure and history around the scene.

01
SCENE STATE

What is happening right now?

Scene State gives the current moment an explicit structure instead of leaving every important detail scattered through old messages.

CURRENT SCENE

The Abandoned Station

SCENE 12
LOCATIONNorth Station
TIME11:47 PM
WEATHERHeavy rain
MOODUneasy
PRESENTAya · Mira
OBJECTIVEFind the missing journal
IMMEDIATE THREATSomething is following them
TitleScene / dayLocationTimePresentNot presentWeatherMoodObjectiveThreatConditionsNotes
02
SCENE WORKFLOW

Start it. Play it. Preserve it.

START SCENE

Establish the situation.

Set the title, location, cast, mood, objective and anything immediately important before continuing the RP.

03
SCENE PRESENTATION

Start a scene like a scene.

Normal chat can show scene title cards, transitions and an optional caption above the composer. These are presentation tools; they do not inspect the roleplay text.

The Abandoned StationScene 12 · North Station · 11:47 PM
Scene caption

Keep title, location and time visible as a small normal-chat reminder.

Atmosphere preset

Start Scene can optionally apply one of Furina's scene-atmosphere presets at the same time.

Screenshot view

Temporarily hide selected UI, widen the transcript and optionally use a 0 / 3 / 5 / 10 second countdown for capture.

04
SCENE RECAPS

“Wait. What happened last time?”

Scene Intelligence stores user-reviewed recaps. Furina does not need to invent a summary from nowhere.

SCENE 11COMPLETE

The Forest Attack

SUMMARY

Aya and Ren were attacked while returning from the western ruins.

MAJOR DEVELOPMENT

Aya discovered that Ren had known about the danger before they entered the forest.

OPEN THREAD

Ren still refuses to explain who warned him.

RETURNING LATER?
05
STORY TIMELINE

Keep important events in order.

Timeline entries preserve significant events separately from individual chat messages and can be marked completed, ongoing or planned.

Completed Ongoing Planned
DAY 4 · COMPLETEDForest attack

Aya discovers Ren had prior warning of the attack.

DAY 5 · ONGOINGSearch for the missing journal

Aya and Mira investigate the abandoned station.

FUTURE · PLANNEDConfront Ren

Aya intends to demand the full truth once the journal is recovered.

06
SCENE SNAPSHOTS

Save the scene before an alternate take.

A snapshot records the current Scene State plus useful story context for reference and alternate-scene packages. Its Restore action reapplies the saved Scene State.

CURRENT SCENE STATE
SceneAbandoned Station
MoodUneasy
ObjectiveFind the journal
SAVED SNAPSHOT
No snapshot yet.

Capture the current Scene State first.

!
Restore means Scene State — not every recorded setting.

The snapshot also records its chapter, Director preset, active Guard Rails and enabled Continuity for the copied alternate-scene package/reference. Restore Scene State reapplies the saved Scene State only; it does not automatically re-enable those other systems or rewind Clank messages.

07
BOOKMARKS & CHAPTERS

Hundreds of messages deserve landmarks.

Bookmarks make individual messages easy to find again. Chapters divide a long conversation into named sections.

CHAPTER 4The Station

“I found something,” Mira whispers, holding up the silver key.

Aya turns toward the sound at the end of the platform.

The journal is lying open beneath the broken station clock.

ORGANIZATION
2 bookmarksImportant messages saved
Chapter 4Current section
08
STORY BIBLE

Package the Furina side of the story.

Story Bible portability can export the current conversation's Furina story data as JSON, with a readable Markdown export also available.

FURINA STORY BIBLEThe Station Arc

7 story-data groups included automatically

Story Bible export builds the versioned package from the conversation's available Furina story data. These are contents, not selectable export switches.
Import supports merge or replace workflows.

Story Bible data is versioned and validated before Furina uses it. Keep backups before replacing important story state.

NEXT GUIDE

Now change the entire way the conversation is presented.

Visual Novel Mode and Phantom Chat are Furina's experimental alternate interfaces.