# Script editor overview

> Nine meaningful line types, Tab and number keys, four structure layers, one undo stack.

Source: https://loomworld.ai/docs/editor-overview

## Where the editor sits

The script editor is the center of Loomworld. Reference modules, timeline, foreshadows, and AI collaboration all turn around the draft. The script records the scenes you actually wrote; the library records the facts you chose to maintain. The two connect through references and structure. Neither rewrites the other on its own.

## Nine structured nodes

The script is made of nine node types. Each has a clear meaning:

- Description: scene narration and ordinary prose.
- Character: the name of who speaks, linked to a character card.
- Dialogue: that character’s lines.
- Dialogue action: something that happens while the line is being spoken.
- Narration: the narrator’s voice, or a voice offscreen.
- Comment: a memo for the author only; it ends the current speaker.
- Transition: a cut mark between scenes.
- Scene setting: a place or time shift inside a scene (the cards label it “Setting”).
- Scene: the structural anchor of a dramatic unit.

Structure pays off immediately: the editor can render and fold by type; AI can tell “line” from “action”; the library can find characters and places in the draft with precision.

## Shape a line: Tab and number keys

Writing rhythm should not be broken by formatting. Loomworld turns shaping into muscle memory:

- `Tab` opens the type menu; at the start of an empty line you can also use `/`;
- `1`–`9` choose the matching type while the menu is open;
- After a character line, Enter defaults to dialogue. After other content types, Enter returns to description.

Shaping only changes the node’s type mark. It does not change the words you wrote. There is nothing to lose. Press away.

## Scenes and chapter structure

A script is organized in four layers: chapter, scene, scene setting, and script nodes. A scene establishes a dramatic unit; scene setting records place and time shifts inside it. Chapter intent records what this chapter should move, and can also serve as the goal when you ask the chat box to continue.

## How the script and the library connect

A selection in the script can right-click to connect characters, places, props, and lore. Long-text fields such as lore descriptions support inserting a reference with @. The chapter companion only shows and adjusts chapter, scene, and scene setting structure. It does not carry AI suggestions.

For entries and the auto/manual boundary, see [Entity mentions and @](https://loomworld.ai/docs/references) and [Cross-module links](https://loomworld.ai/docs/cross-sync).

## What happens when an old draft comes in

Choosing “import as the script” for a TXT or DOCX file in the project hall parses the text into content lines in its original order, locally, with no model rewriting it and no characters, locations or props filed on your behalf. If it is interrupted the import resumes from the cursor without duplicating. Want the library to grow from an old draft? Shape lines and connect passages after it lands.

## Limits and troubleshooting

- Not a typesetting engine: no font sizes, margins or paper specs. For delivery use Settings → Project data → delivery export, in Word, PDF, or Quilldown.
- Copy leaves styling behind: selecting across lines gives plain text.
- Scene numbers follow the order of scene nodes in the script; a hand-made scene mixed with script scenes numbers by the script.
- Empty fields take no space in the rendered view, and Narration is the only narrative node—there is no second, near-identical type to maintain.