AVG and visual novels
Preview: author workbench, production revision, release, and player saves are connected. Generated literary and audiovisual quality still require per-work acceptance.
Entry: AVG → Library (AVG → 作品库). Try the no-API built-in work first to understand the stage and choices.
Recommended workflow
- Define goals in Production → Story and experience (制作台 → 故事与体验), and branches in Routes and ending goals (路线与结局目标).
- Select a world version; confirm candidates and the production plan through Planning conversation (方案会谈).
- Start Production flow (制作流程), checking Narrative graph and dialogue (叙事图与对白) and Variables and endings (变量与结局).
- Check assets and presentation references under Backgrounds and sprites (背景与立绘), Audio and presentation (音频与演出), and Asset management (素材管理).
- Run Checks and playtest (检查与试玩), revise issues, and retain a release.
- Play at Play → Player stage (游玩 → 玩家舞台), managing progress through Saves and routes (存档与路线).
Text and presentation
Story beats can reference backgrounds, characters, and audio. Missing assets or invalid references affect the stage; successful text generation does not mean audiovisual delivery is complete.
Check that each important route reaches its intended ending and that stage state is correct after loading a save.
Current boundaries
Built-in works use prepared story and assets to demonstrate a playable result. This does not mean arbitrary worlds automatically produce comparable quality. Audiovisual assets require lawful sources and actual service support.
Continue: Shared interactive workflow · Backup and recovery.