Testing & Debugging » Debug Menu
November 9, 2025

Debug Menu

Work in Progress

This documentation is still being expanded and refined. Features, screenshots, and descriptions may change until Talescape's public release. If something is unclear or you need help, please ask on the official Talescape Discord. We're happy to clarify or update pages as needed.

The Debug Menu is a testing tool that lets you inspect and modify the state of your story while previewing it in the editor. It allows you to view logs, edit variables, and simulate inventory changes to test how your story reacts under different conditions.

You can open the Debug Menu during Story Preview by selecting the Debug icon.

1. Overview

The Debug Menu contains three main tabs:

Tab Purpose
Logs Displays story events, actions, and system messages during preview.
Inventory Lets you view and modify item quantities used in your story.
Variables Allows you to view and change variable values in real time.

Any changes made through the Debug Menu affect only the current preview session. They are not saved to your story and will reset when you restart the preview.

2. Logs

The Logs tab shows what happens behind the scenes as your story runs. It helps you follow story flow, test logic, and understand when certain events occur.

What you can see:

  • Trigger activations and action results
  • Dialogue progress and condition checks
  • Variable or item changes caused by player choices

Controls:

  • Search – Filter log entries by keyword.
  • All Levels – Filter by information type (Info, Warning, Debug).
  • All Channels – Filter by system (Scene, Dialogue, Event, etc.).
  • Clear – Remove all visible entries.

The Logs tab is primarily a storytelling aid that helps Bards confirm that story logic runs in the expected order. It does not display technical or runtime errors.

3. Inventory

The Inventory tab lists all items available in the story, not just those currently held by the player. You can adjust their quantities freely to test crafting, puzzles, or item-based conditions.

You can:

  • Add or remove quantities for any item using the + / − buttons.
  • Search items by name.
  • Clear all quantities to reset the inventory to zero.

This allows you to test scenarios such as:

  • Crafting new items using recipes.
  • Checking whether events trigger when an item is present.
  • Verifying story paths that depend on collected objects.

4. Variables

The Variables tab shows all variables defined in your story and their current values. You can modify them to simulate player decisions or test alternate story paths.

You can:

  • Toggle flags (true/false).
  • Change numbers directly.
  • Edit text values.
  • Reset individual variables or clear all at once.

The variable list updates automatically when new variables are created or changed.

5. Testing Workflow

The Debug Menu is designed for creative testing, not technical debugging. It helps you verify that:

  • Choices and variables behave as intended.
  • Items and crafting logic work correctly.
  • Story branches unlock under the right conditions.
  • Player state transitions are consistent.

You can combine the Debug Menu with the Editor Checks System for a complete validation workflow before release.

6. Best Practices

  • Use Logs to trace story flow and confirm event order.
  • Use Variables to jump directly to specific branches for quick testing.
  • Use Inventory to test crafting or item gating without replaying early scenes.
  • Reset often to verify that your story works correctly from a fresh start.

The Debug Menu gives you full control over testing, letting you explore every branch, decision, and outcome before your story reaches Dreamers.