Editor Checks System
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 Editor Checks System helps you verify that your story is complete, consistent, and ready for release. It automatically scans your story for common issues (from missing assets to incomplete metadata) and gives you detailed feedback on what to fix.
These same checks are also used during the automated review that runs before publication. Running them inside the editor lets you resolve problems early and avoid rejection during release.
1. Running Checks
You can trigger checks in two ways:
| Scope | Description |
|---|---|
| Global Check (Overview) | Runs all available validations for your entire story. Accessible via the Checks panel in the sidebar. |
| Local Check (Per Element) | Runs validations for the element you are currently editing, such as a specific chapter, scene, or dialogue. |
Results are displayed immediately and grouped by category (e.g., Marketplace, Chapters, Scenes, Characters). You can rerun checks at any time by clicking Run Checks.
2. Severity Levels
Each issue is assigned a severity level to indicate its importance:
| Severity | Description | Action |
|---|---|---|
| Info | Informational notes or suggestions. | No action required, but may help improve quality. |
| Warning | Potential issues that could cause problems depending on context. | Review and fix if relevant. |
| Failure | Critical errors that prevent your story from being released. | Must be fixed before creating a release. |
Failures are clearly highlighted. A story with any failures cannot be published until they are resolved.
3. Typical Checks
The system covers both technical and structural validations, such as:
| Category | Example Checks |
|---|---|
| Marketplace | Description length, screenshots, and tag requirements. |
| Chapters | Every chapter has a start scene and at least one exit. |
| Scenes | Each scene has a background and is used somewhere in the story. |
| Dialogues | No unreachable branches or missing targets. |
| Media | All referenced assets exist and match the required formats. |
| Items / Crafting | Recipes and item references are valid. |
Each check displays its result, timestamp, and detailed message so you know exactly what to adjust.
4. Local Checks While Editing
You can also run local checks directly inside editors like Scenes, Dialogues, or Chapters.
These focused checks verify only the content you’re currently working on, perfect for quick validation before continuing development.
Example: While editing a scene, local checks confirm it has a background, valid exits, and is used somewhere in the story.
5. Release Integration
The same validation system is used during the Automated Review phase of the release workflow. If you’ve already fixed all issues shown in the Editor Checks System, your story will automatically pass the automated review stage.
This ensures a smooth transition from development to publication.
6. Best Practices
- Run full story checks regularly, especially before submission.
- Fix all Failures and review Warnings to prevent surprises during review.
- Use local checks frequently while editing to catch problems early.
- Review timestamps to track when each check was last performed.
The Editor Checks System acts as your internal quality gate, ensuring every story released on Talescape is stable, complete, and ready for Dreamers to explore.