Getting Started » Closed Beta
March 17, 2026

Closed Beta

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.

Introduction

Welcome to the Talescape Closed Beta.

This phase is focused on testing the editor workflow under real conditions. The goal is to identify usability issues, technical problems, and edge cases before the official release.

The beta is primarily aimed at creators (Bards). You are encouraged to actively build stories, experiment with systems, and push the editor to its limits.

Key principles of this beta:

  • The focus is on creation and testing, not on polished publishing
  • No real payments are processed via Stripe (see Purchases section for details)
  • Moderation is intentionally more relaxed to allow faster iteration
  • All story data and savegames persist during the beta

Before launch, the platform will be reset:

  • All purchases will be revoked
  • All published stories will be unpublished (not deleted)
  • Stories will go through a proper review and moderation process before release

If anything is unclear or not working as expected:

  • Use the Help & Support section inside the app
  • Or reach out directly via DM

Help and documentation are available throughout the app:

  • Click the Help icon in the header to open documentation
  • Use the Help icon next to specific components for contextual help
  • Or access the full documentation from the sidebar
  • Additional documentation is available via the Beta badge in the header

Feature Requests

This beta is not only about fixing bugs but also about improving workflows.

If you notice friction, missing features, or unclear behavior:

  • Submit feedback via the in-app support system
  • Or send a direct message

Focus especially on:

  • Editor usability
  • Missing quality-of-life features
  • Confusing workflows or unclear UI behavior

Bard Verification

To test creator-related systems, Bard verification is available in a limited form.

PayPal (Sandbox Mode)

  • PayPal is running in sandbox mode
  • No real money is transferred

Access

If you want to test publishing paid stories:

  • Send a DM or create an in-app support request
  • You will receive sandbox credentials for testing

Purchases

Purchases behave differently depending on the selected payment provider.

Stripe (Test Mode)

Stripe is running in test mode, which means no real charges are made.

To simulate a purchase, use the following test credit card:

  • Card Number: 4242 4242 4242 4242
  • Any future expiration date
  • Any 3-digit CVC
  • Any name and ZIP code

Important:

  • These values do not represent a real credit card
  • No money will be charged
  • Payments are only simulated to test the purchase flow

Steam

Steam purchases are not in sandbox mode.

  • Real payments may occur if you complete a purchase
  • If you accidentally buy something: Contact me and I will refund it immediately.

Pricing & Taxes

  • Pricing categories are not final
  • Tax calculation is not final

Expect changes before release.

Missing Features

The following systems are not yet implemented or incomplete:

  • Payouts through PayPal
  • Subscriptions
  • Florins (tips for Bards)
  • Manual savegame management
  • Certain advanced statistics and analytics

These features will be added in later phases.

Known Issues

The following issues are currently known:

  • Sequential events can bleed into the pause menu
  • Hidden elements sometimes flicker on scene change
  • Dialogue nodes may occasionally become unresponsive
  • Story state (e.g. number of scenes) can be outdated

These issues are already tracked and will be addressed.

Troubleshooting

If something is not working as expected, try the following:

  • Leave the story / dialogue or scene and return to it
  • Reload user data via the Maintenance section in Settings
  • Log out and log in again

If the issue persists:

  • Report it via Help & Support
  • Include as much detail as possible