检查邮箱和密码

• 确认输入的邮箱地址与注册时一致
• 检查密码大小写是否正确
• 清除输入框前后可能存在的空格

尝试重置密码

• 点击登录页面的「忘记密码」链接
• 输入注册邮箱,检查收件箱(包括垃圾邮件文件夹)
• 重置链接有效期为 24 小时

清除浏览器缓存

• Chrome: 设置 → 隐私和安全 → 清除浏览数据 → 选择「缓存的图片和文件」
• Safari: 偏好设置 → 隐私 → 管理网站数据 → 移除所有数据
• 清除后刷新页面重新尝试

尝试其他浏览器

• 推荐使用 Chrome、Safari、Edge 等现代浏览器
• 确认浏览器版本为最新
• 避免使用 IE 等旧版浏览器

确认 Google 账号正常

• 在独立标签页访问 google.com,确认能正常登录
• 检查 Google 账号是否开启了两步验证

检查网络连接

• 确认能正常访问 Google 服务
• 如果使用 VPN,尝试切换节点或暂时关闭

尝试邮箱密码登录

• 如果 Google 登录持续失败,可以使用注册时填写的邮箱和密码登录
• 两种登录方式完全等效

检查浏览器 Cookie 设置

• 确保浏览器允许网站使用 Cookie
• Chrome: 设置 → 隐私和安全 → 第三方 Cookie → 允许第三方 Cookie

清除本地存储

• 打开浏览器开发者工具(F12)
• Application → Local Storage → 右键清除
• 刷新页面重新登录

检查 Token 过期时间

• 登录状态会在 7 天后自动过期
• 过期后需要重新登录,这是正常的安全机制

检查网络连接

• 确认网络稳定,可以尝试访问其他网站测试速度
• 如果使用 VPN,尝试切换节点
• 移动网络用户建议切换到 Wi-Fi

内容较长时需要耐心等待

• 生成 500 字左右的内容通常需要 5-15 秒
• 如果引用了多个文件作为上下文,处理时间会增加
• 建议单次引用文件不超过 5 个

刷新页面重试

• 如果超过 30 秒无响应,可以刷新页面
• AI 会话记录会自动保存,刷新后可以继续对话
• 重新发送相同的问题即可

检查 AI 记忆设置

• 确认当前会话中引用了相关的角色卡、设定文件
• 在对话框中使用 @ 符号明确引用文件
• AI 会优先使用被引用文件中的信息

提供更具体的描述

• 避免模糊指令如"帮我写一段"
• 改为具体描述:"写一段主角在雨夜里独自走在街头,回忆起童年往事的场景"
• 包含人物、地点、情绪、动作等要素

添加相关上下文

• 在对话中简要说明当前情节背景
• 例如:"这是第三章,主角刚发现朋友的秘密"
• AI 会根据上下文调整生成内容的风格和走向

尝试换一种问法

• 如果"描写一个战斗场景"效果不好
• 改为"用武侠小说风格描写两个剑客的对决,重点描写招式和动作"
• 明确风格、视角、重点要素

刷新页面

• 按 F5 或点击浏览器刷新按钮
• 刷新后会话历史会保留
• 重新发送问题即可继续

检查网络连接

• AI 对话使用流式传输(SSE),需要稳定网络
• 网络波动可能导致连接中断
• 确认网络稳定后重试

新建会话重试

• 如果同一会话反复中断,点击"新建对话"按钮
• 新会话可以避免历史数据干扰
• 记得重新引用需要的文件

检查提示词是否清晰

• 明确指定输出格式:"请用列表形式列出"
• 示例:"按照【姓名】|【年龄】|【职业】的表格格式输出"

分段生成

• 不要一次性要求生成超长内容
• 分多次对话,每次生成一个部分
• 例如:"先写开头 200 字"→"继续写中间部分"

检查网络连接

• 自动保存需要网络连接
• 查看编辑器右上角的保存状态图标
• 云朵图标表示正在同步,绿色对勾表示已保存

查看保存状态

• 编辑器底部会显示"上次保存于 XX:XX"
• 如果长时间未更新,可能网络异常
• 手动按 Ctrl+S (Mac: Cmd+S) 触发保存

查看版本历史

• 点击右侧边栏的"历史"标签
• 版本历史会记录每次自动保存的快照
• 可以回滚到任意历史版本

刷新页面

• 按 F5 刷新,等待编辑器重新加载
• 通常可以解决临时加载问题

清除浏览器缓存

• 缓存数据损坏可能导致加载失败
• 清除方法见"登录问题 → 清除浏览器缓存"

检查浏览器兼容性

• 支持的浏览器: Chrome 90+, Safari 14+, Edge 90+
• 不支持 IE 浏览器
• 旧版浏览器请升级到最新版本

文件过大导致性能问题

• 单个文件建议不超过 10 万字
• 如果文件过大,考虑按章节拆分为多个文件

关闭不必要的标签页

• 浏览器打开过多标签会占用内存
• 关闭其他不需要的标签页释放资源

检查设备内存

• 打开任务管理器查看内存占用
• 如果内存不足,关闭其他应用程序

检查项目状态

• 确认当前在正确的项目中
• 项目名称显示在页面顶部导航栏

刷新页面

• 文件树数据可能未及时同步
• 刷新页面后重试

尝试其他文件类型

• 如果某种类型文件创建失败
• 尝试创建其他类型文件测试是否为通用问题

刷新页面

• 文件树数据来自服务器,刷新可以重新加载
• 快捷键: F5 或 Ctrl+R (Mac: Cmd+R)

检查网络连接

• 网络不稳定可能导致文件树加载不完整
• 确认网络正常后刷新页面

清除本地缓存

• 开发者工具(F12) → Application → Local Storage
• 清除后刷新页面

确认删除操作

• 点击删除按钮后会弹出确认对话框
• 需要点击"确认"才会真正删除

检查文件是否被引用

• 如果文件正在 AI 对话中被引用
• 先结束对话或刷新页面后重试

检查网络连接

• 导出需要从服务器下载文件
• 确保网络稳定,避免下载中断

减少导出范围

• 如果项目内容非常多(如超过 50 个文件)
• 尝试分批导出,每次选择部分章节

刷新并重试

• 刷新页面后重新导出
• 建议关闭浏览器插件（如下载拦截类扩展）后重试

使用正确的编码打开

• 导出的 TXT 文件使用 UTF-8 编码
• Windows 记事本: 打开时选择编码为 UTF-8
• 或使用 VS Code、Notepad++ 等编辑器打开

避免二次转换导致乱码

• 若通过第三方工具转换格式，先确认源文件编码为 UTF-8
• 转载到投稿平台前，建议先在本地编辑器预览一次

关闭不必要的标签页

• 浏览器标签过多会占用大量内存
• 关闭其他标签页可以显著提升性能

清除浏览器缓存

• 缓存数据过多可能影响性能
• 定期清理浏览器缓存和 Cookie

检查设备内存

• 打开任务管理器(Windows)或活动监视器(Mac)
• 如果内存占用超过 80%,关闭其他应用程序

检查 CPU 占用

• 其他程序占用大量 CPU 会影响浏览器性能
• 关闭占用 CPU 的程序(如视频渲染、大型游戏等)

首次加载需要下载资源

• zenstory首次加载需要下载 JS、CSS 等静态资源
• 后续访问会使用浏览器缓存,速度会快很多

网络速度影响

• 使用 4G/5G 或高速 Wi-Fi 可以加快加载
• 避免在网络高峰期(如晚上 8-10 点)首次访问

问题截图

• 包含完整的错误信息或异常界面
• 标注问题发生的位置

操作步骤

• 描述详细的操作步骤,便于客服复现问题
• 例如:"登录后 → 点击项目 A → 新建文件 → 输入标题 → 点击创建按钮 → 报错"

环境和设备信息

• 浏览器类型和版本(如 Chrome 120)
• 操作系统(如 Windows 11 / macOS 14)
• 网络环境(如电信 100M 宽带 / 4G 网络)

问题发生时间

• 提供大致时间可以帮助技术人员查看日志
• 例如:"2024 年 1 月 15 日晚上 8 点左右"

Check Email and Password

• Confirm the email address matches the one used during registration
• Check if password case sensitivity is correct
• Clear any potential leading or trailing spaces in the input fields

[Screenshot: Close-up of login page input fields, highlighting email and password fields]

Try Password Reset

• Click the "Forgot Password" link on the login page
• Enter your registered email and check your inbox (including spam folder)
• The reset link is valid for 24 hours

Clear Browser Cache

• Chrome: Settings → Privacy and Security → Clear browsing data → Select "Cached images and files"
• Safari: Preferences → Privacy → Manage Website Data → Remove All Data
• Refresh the page after clearing and try again

Try a Different Browser

• We recommend using modern browsers like Chrome, Safari, or Edge
• Ensure your browser is updated to the latest version
• Avoid using outdated browsers like IE

Confirm Google Account is Working

• Visit google.com in a separate tab to confirm you can log in normally
• Check if your Google account has two-factor authentication enabled

Check Network Connection

• Confirm you can access Google services normally
• If using a VPN, try switching nodes or temporarily disabling it

Try Email/Password Login

• If Google login continues to fail, you can use the email and password from registration
• Both login methods are fully equivalent

Check Browser Cookie Settings

• Ensure your browser allows websites to use cookies
• Chrome: Settings → Privacy and Security → Third-party cookies → Allow third-party cookies

Clear Local Storage

• Open browser developer tools (F12)
• Application → Local Storage → Right-click to clear
• Refresh the page and log in again

Check Token Expiration

• Login status automatically expires after 7 days
• Re-login is required after expiration - this is a normal security mechanism

Check Network Connection

• Confirm network stability by testing other websites
• If using a VPN, try switching nodes
• Mobile network users should switch to Wi-Fi

Be Patient with Longer Content

• Generating about 500 words typically takes 5-15 seconds
• Processing time increases if multiple files are referenced as context
• We recommend referencing no more than 5 files at once

[Screenshot: Loading animation in AI chat dialog, highlighting "Generating..." prompt]

Refresh Page and Retry

• If there's no response after 30 seconds, refresh the page
• AI conversation history is automatically saved, you can continue after refresh
• Simply resend the same question

Check AI Memory Settings

• Confirm relevant character cards and setting files are referenced in the current session
• Use the @ symbol in the chat box to explicitly reference files
• AI prioritizes information from referenced files

Provide More Specific Descriptions

• Avoid vague instructions like "help me write something"
• Instead, be specific: "Write a scene where the protagonist walks alone on a street at night in the rain, recalling childhood memories"
• Include elements like characters, locations, emotions, and actions

Add Relevant Context

• Briefly explain the current plot background in the conversation
• For example: "This is Chapter 3, the protagonist just discovered a friend's secret"
• AI will adjust the style and direction of generated content based on context

Try a Different Approach

• If "describe a battle scene" doesn't work well
• Change to "describe a duel between two swordsmen in martial arts novel style, focusing on moves and actions"
• Specify style, perspective, and key elements

Refresh Page

• Press F5 or click the browser refresh button
• Conversation history is preserved after refresh
• Resend the question to continue

Check Network Connection

• AI chat uses streaming (SSE) and requires a stable network
• Network fluctuations may cause connection interruptions
• Retry after confirming network stability

Create New Session

• If the same session repeatedly interrupts, click "New Conversation" button
• New sessions avoid interference from historical data
• Remember to re-reference needed files

Check if Prompt is Clear

• Explicitly specify output format: "Please list in bullet points"
• Example: "Output in table format: [Name] | [Age] | [Occupation]"

Generate in Segments

• Don't request generating very long content all at once
• Split into multiple conversations, generating one part each time
• For example: "First write the opening 200 words" → "Continue with the middle part"

Check Network Connection

• Auto-save requires network connection
• Check the save status icon in the top right corner of the editor
• Cloud icon indicates syncing, green checkmark indicates saved

[Screenshot: Editor top right corner save status icon, highlighting different icon meanings]

Check Save Status

• Editor bottom shows "Last saved at XX:XX"
• If not updated for a long time, there may be a network issue
• Manually press Ctrl+S (Mac: Cmd+S) to trigger save

Check Version History

• Click the "History" tab in the right sidebar
• Version history records snapshots of each auto-save
• You can rollback to any historical version

Refresh Page

• Press F5 to refresh, wait for editor to reload
• This usually resolves temporary loading issues

Clear Browser Cache

• Corrupted cache data may cause loading failures
• See "Login Issues → Clear Browser Cache" for clearing methods

Check Browser Compatibility

• Supported browsers: Chrome 90+, Safari 14+, Edge 90+
• IE browser is not supported
• Please upgrade older browsers to the latest version

Performance Issues from Large Files

• Single files should not exceed 100,000 characters
• If file is too large, consider splitting by chapters into multiple files

Close Unnecessary Tabs

• Too many browser tabs open will occupy memory
• Close other unneeded tabs to free up resources

Check Device Memory

• Open Task Manager to check memory usage
• If memory is insufficient, close other applications

Check Project Status

• Confirm you're in the correct project
• Project name is displayed in the top navigation bar

Refresh Page

• File tree data may not have synced in time
• Refresh the page and try again

Try Other File Types

• If one file type fails to create
• Try creating other file types to test if it's a general issue

Refresh Page

• File tree data comes from the server, refresh to reload
• Shortcut: F5 or Ctrl+R (Mac: Cmd+R)

Check Network Connection

• Unstable network may cause incomplete file tree loading
• Confirm network is normal then refresh page

Clear Local Cache

• Developer Tools (F12) → Application → Local Storage
• Clear then refresh page

Confirm Delete Operation

• Clicking delete button shows a confirmation dialog
• You need to click "Confirm" to actually delete

Check if File is Referenced

• If file is being referenced in AI conversation
• End conversation or refresh page then retry

Check Network Connection

• Export requires downloading files from server
• Ensure network stability to avoid download interruption

Reduce Export Scope

• If project has very many files (e.g., over 50)
• Try exporting in batches, selecting partial chapters each time

Refresh and Retry

• Refresh the page and export again
• Disable download-related browser extensions and retry

Open with Correct Encoding

• Exported TXT files use UTF-8 encoding
• Windows Notepad: Select UTF-8 encoding when opening
• Or use editors like VS Code, Notepad++

Avoid Encoding Issues During Conversion

• If you convert formats with third-party tools, ensure source file encoding is UTF-8
• Before submitting, preview once in a local editor

Close Unnecessary Tabs

• Too many browser tabs occupies significant memory
• Closing other tabs can significantly improve performance

Clear Browser Cache

• Too much cached data may affect performance
• Regularly clean browser cache and cookies

Check Device Memory

• Open Task Manager (Windows) or Activity Monitor (Mac)
• If memory usage exceeds 80%, close other applications

Check CPU Usage

• Other programs using significant CPU affects browser performance
• Close CPU-intensive programs (like video rendering, large games, etc.)

First Load Downloads Resources

• zenstory's first load requires downloading JS, CSS, and other static resources
• Subsequent visits use browser cache and will be much faster

Network Speed Impact

• Using 4G/5G or high-speed Wi-Fi can speed up loading
• Avoid first visits during network peak hours (e.g., 8-10 PM)

Problem Screenshots

• Include complete error messages or abnormal interface
• Mark the location where the problem occurred

Operation Steps

• Describe detailed operation steps for customer service to reproduce the issue
• For example: "After login → Click project A → Create new file → Enter title → Click create button → Error"

Environment and Device Information

• Browser type and version (e.g., Chrome 120)
• Operating system (e.g., Windows 11 / macOS 14)
• Network environment (e.g., Telecom 100M broadband / 4G network)

Problem Occurrence Time

• Providing approximate time helps technical staff check logs
• For example: "Around 8 PM on January 15, 2024"