Craft

Visual novels

A visual novel is a story readers click through one page at a time. A backdrop fills the stage, the speaker's cutout stands on it, and the line sits in a text box below, with music and narration if the author added them. You can make one from a stretch of a game you played, or write one from scratch in a project with no game at all. When it's ready you share it by link or list it on Discover, where anyone can read it.

How it is used

  • A story is its own thing. It isn't a file in the project. It is one document with its pages, cast, chapters and music, and it belongs to the person who made it. Only they can edit it. Editing it never changes the game or the world it came from, and deleting the game doesn't break it.
  • A story made in a project is listed there. The whole team sees it in the project's Visual Novels settings, with stories the team made from their own games of it. Each person still edits only their own.
  • The draft and the published version are separate. Every edit saves to the draft. Readers get the version that was last published, so nothing they see changes until you publish again.
  • Who can read it. A new story is private. Unlisted shares it with anyone who has the link. Public also lists it on Discover and on its world's page. Publishing a public story runs the same content review as publishing a world, which sets its content rating (see the content policy).
  • Reading. Readers click or tap to turn pages, or let auto play turn them, waiting for each page's narration. They can jump between chapters. The last page is the ending. On a phone held upright the stage is narrow, so a story can place cutouts, pictures, backdrops and clips differently for phones.
  • It isn't the game's story view. A game already plays like a visual novel while you play. A visual novel is a frozen copy you can edit and share after the game.

Making one

There are two ways to start, and both open the same editor:

  • From a game. A player turns part of a game into a story from inside the game: a message's menu has Visual novel from here and Visual novel up to here, and the game's share button and the Visual Novels section of its settings open the same picker. The range is any first and last message, a whole scene, or the whole game. Any player in the game can do this, and the story is theirs.
  • From scratch. To start a blank story in a project, open your project's settings, then Visual Novels, and click New visual novel. It opens on one empty page standing on the project's cover, and it can cast the project's Game Master and characters and use its locations as backdrops.

Then the story is written in the visual novel editor.

Your stories are under Your Visual Novels in the sidebar. In the editor, the outline on the left lists chapters, scenes and pages, the page shows in the middle as readers will see it, and the inspector on the right edits the page: its kind, speaker, text, narration, scene and music. The gear opens the novel settings (cast, music, narration), and Preview plays the story from any page.

To share it, set who can read it with the editor's Share popover. After changing a shared story, open Share in the editor and click Publish changes to give readers the new version.

What a game becomes

A story made from a game is built from the messages in the range you pick:

  • The GM's narration becomes narration pages, a paragraph each. Its dialogue, read-aloud boxes, handouts and scene headings become pages of the same kind.
  • Everyone who speaks joins the cast with their portrait, cutout and voice, and each line wears the expression the GM gave it when the character has one by that name.
  • What a player wrote becomes a line said by their character.
  • Scene images become scene pages and the backdrop from there on. Scene videos become video pages. Moving to a location changes the backdrop to its picture.
  • A change of music starts a new music cue. Dice rolls become short pages with the result.
  • Scene headings open chapters, with a Prologue when the range starts in the middle of a scene. A range with a great many headings becomes one chapter instead; split it into chapters in the editor.
  • Narration already played in the game comes along with its page.

One story holds at most 2,000 pages and one export takes at most 500 GM turns. A long campaign makes several stories, one per arc.

Art, music and narration

  • Cast and backdrops come from the world, through the editor's cast settings (From the project or From the game) and its scene picker, which list your world's characters and locations. A story with no world builds its cast and backdrops from the studio and uploads.
  • Expressions and cutouts come best from character files that already have them. The editor can also make them for a cast member from their portrait, which costs energy like any image generation.
  • Music is a track from your studio.
  • Narration is a voice reading each page aloud. For each page, generate or upload it in the page's Narration section, or narrate every page at once from Narration in the novel settings. Generated narration costs energy; an uploaded clip doesn't. When a page's words change, its generated narration goes out of date until it is made again.
  • Every picture, clip and track must be stored on Craft (made or uploaded in Craft). An address from anywhere else is refused.

Doing it well

  • One beat per page. A line of dialogue, or a short paragraph of narration. Readers click after every page, so long pages stall them.
  • Let the characters carry it. Keep narration between lines short, and save read-aloud boxes and handouts for moments a reader should stop on.
  • Open scenes with a change of backdrop, and chapters with a scene heading.
  • Give every speaking character a portrait and a cutout, and match their expression to each line.
  • Stage conversations. Give each recurring character a default spot, on opposite sides, and move them on a page only when they move. Check the phone layout too: a spot that works on a wide stage can push a cutout off a narrow one.
  • Place a prop once. A picture that should stay through a conversation is placed on its first page and kept on, not placed again on every page.
  • End on a page worth ending on. The last page is where auto play stops.
  • Before publishing, give the story a description (it shows on Discover), read it through in the preview, and on a phone.

Mistakes

  • Editing a shared story and not publishing. Readers keep the old version until the draft is published.
  • A line that names a cast member or expression that doesn't exist. Use the ids the cast has. A save doesn't refuse a dangling one: it turns the line into an "Unknown" speaker, or drops the expression so the line wears the member's base art.
  • The backdrop set on every page. Set it only where it changes; later pages keep it.
  • Images from outside Craft. They are refused. Use art made or uploaded in Craft.
  • Expecting the game to change. A story is a copy. Edits stay in the story, and later turns of the game don't reach it; make a new story from them.
  • Changing words after narrating. The narration still reads the old words until it is made again.

Reference

  • The visual novel document: The story's JSON document: pages and their kinds, speakers and the cast, expressions, where cutouts stand, pictures, chapters, music and settings.