Story Dashboard

The Story Dashboard is the central control panel for a single story in Talescape. It provides an overview of all systems that make up a story and offers direct access to the tools used during development, testing, and publishing.

Each story has its own dashboard. From here, Bards can navigate to every component of the project, manage assets and logic, validate structure, and prepare releases.

The dashboard summarizes the current state of the story and provides quick access to its main modules. Each tile represents a system within the editor.

The counters on each tile indicate how many elements currently exist in that category. For example, the number of scenes, dialogues, or events that are part of the story.

Tiles act as navigation shortcuts and open the corresponding editor section.

At the top of the dashboard, the following information is displayed:

• Title: The name of the story currently being edited.
• Status: Indicates the current publication state of the story, such as Draft or released versions.
• Language: Shows the primary language used for the story.
• Metrics: Small indicators display runtime statistics such as emotional reactions, engagement, or playtime once the story is published. These metrics remain empty while the story is still in development.

• Scenes: Scenes form the structural backbone of the story. They define locations, backgrounds, and scene transitions. Chapters and narrative progression are organized through scenes.
• Characters (& Poses): Characters define the participants of the story. They include portraits, poses, and other visual or behavioral properties used during dialogues.
• Dialogues: Dialogues contain branching conversations and player choices. They determine narrative flow and player interaction.

• Items: Items represent objects that can be collected, inspected, or used by the player.
• Recipes: Recipes define combinations of items that create new outcomes. They can be used for crafting systems or puzzle mechanics.
• Events: Events trigger actions when specific conditions occur. They are commonly used to advance story progression or modify the game state.
• Variables: Variables store values that can change during gameplay. They are used to track conditions such as choices, player state, or puzzle progress.
• Timers: Timers introduce time based mechanics. They can delay actions or create time pressure within a scene.

• Achievements: Achievements define milestones that players can unlock during the story. They are typically tied to important decisions, discoveries, or narrative outcomes.

• Media: The media library contains all images, audio files, and other assets used in the story. Assets are uploaded once and can then be reused across scenes, dialogues, or characters.
• Asset Packs: Asset packs allow importing collections of licensed assets into the project. These packs can extend the story with reusable art, sound, or other content.

• Checks: The checks system analyzes the story structure before release. It detects issues such as missing assets, broken links, or structural inconsistencies.
• Releases: The releases section manages published versions of the story. Bards can create release builds, track review status, and manage updates.

• Feedback: Feedback displays reviews and emotional responses submitted by Dreamers after playing the story. These responses help creators understand how their story is received.
• Logs: Logs provide debugging information and system activity for the story. They are primarily used to diagnose technical problems during development.

• Settings: The settings section contains story level configuration such as metadata, collaborators, and publishing details. This includes information required before a story can be released.

The Story Dashboard serves as the entry point for managing a story project. It brings all editing systems, management tools, and publishing controls into a single overview. Instead of navigating through multiple menus, Bards can quickly access every part of the story from one location.