Project items
In Arcweave, a project holds the structure and content of your interactive story, allowing you to design, test, share, and export it.
This section covers all the Arcweave items you can use to build your story. You will learn everything there is to know about the following:
- Boards are the canvases where you design your story flowcharts.
- Use elements and connections to map out story events and write scenes or dialogue trees. To connect distant elements, create jumpers—links to or aliases of elements. These items define how your story flows.
- Represent story objects with components, storing data in the form of attributes.
- Add logic using variables, Arcscript, and branches.
- Add image and sound assets to enrich your story with visuals and audio.
- Use notes and comments to communicate with collaborators—or your future self.
To send someone directly to a board, element, jumper, note, branch, connection, or component, use its Copy link action. See Share an item or board position.
How project items relate
A project's story flow lives on its boards. Components, assets, and global variables belong to the whole project and can be used from any board.
| Item | Where it lives | What it holds | How it relates to other items |
|---|---|---|---|
| Board | The project's Boards section, optionally in board folders. | Elements, connections, branches, jumpers, notes, and comments; board attributes. | Its variable-type attributes are board variables; boards can be mentioned in text. |
| Element | A board. | A title and rich text content with optional Arcscript segments; a cover, audio, attached components, and attributes. | Sends and receives connections; can be the target of jumpers. |
| Connection | A board. | An optional label with text and Arcscript, shown as option text in Play Mode. | Goes from an element or branch to an element, branch, or jumper on the same board. |
| Branch | A board. | if and elseif conditions written in Arcscript, and an optional else. | Receives connections; has at most one output connection per condition. |
| Jumper | A board. | A link to a target element. | Receives connections and continues the flow at its target element, which can be on another board; has no output connections. |
| Note | A board. | Rich text annotations. | Not part of the flow; has no connections, components, or Arcscript. |
| Component | The project's Components section. | A name, custom ID, cover, and attributes. | Attached to elements, mentioned in text, and listed in Component List attributes; its variable-type attributes are component variables. |
| Attribute | A board, component, or element. | A label and a value of a given type. | Component List and Asset List attributes reference components and assets; Boolean, Integer, Float, and String Field attributes of boards and components act as variables. |
| Variable | Global (project), board, or component scope. | A value that can change during play. | Read and changed by Arcscript in element content and labels; read by branch conditions. |
| Asset | The project's Assets section. | Image, audio, and video files. | Used as element and component covers, element audio and video, and in Asset List attributes. |
In Play Mode, the story starts at the starting element and follows connections from element to element. Connection labels become the options the player chooses, branches send the flow down the connection of the first condition that is true, and jumpers continue the flow at their target element. Along the way, Arcscript in element content and labels reads and changes variables, and branch conditions read them to choose a path.