结构化制卡与角色表现获认可;主要痛点是字段难理解、保存不可靠、聊天推进过快。 导入、私密试聊和状态显示也有改进诉求。长回复偏好不同,核心是给玩家保留参与和控制空间。
创作侧|信息分区和 Private Notes 有价值。 little_note 认可独立设置人物、行为规则和世界观,并向 AI 提供不展示给玩家的指令。
little_note:“I appreciate having dedicated spaces for personality, behavioral rules, relationships, and worldbuilding details.”
消费侧|人设、具体细节和情绪回应好。 Nanjing 也反馈,要求放慢后,角色能自然调整节奏。
Nanjing:“Bot stayed sharp and in character with concrete details.”
!聊天好评
创作侧|不知道字段怎么用。 little_note 曾把性格填到 Story Setup,也不确定 AI 是否读取 Public Profile;希望逐字段说明用途、填写示例和公开范围。
little_note:“My biggest difficulty was understanding what each section was actually used for.”
little_note:“A short example under each field could show creators what kind of information belongs there.”
创作侧|备注丢失,报错难定位。 Nanjing 反馈新增配角后主角备注被清空,显示 Saved 后刷新仍为空;20001 没有指出错误字段。
Nanjing:“After reload, notes showed empty despite ‘Saved’.”
创作侧|旧内容迁移和更新费力。 Nanjing 希望支持 JSON/角色卡导入,避免拆填十几个字段;Vega 另提出修订稿更新已有故事、选择性替换。
Nanjing:“Copying a card from another platform meant pasting 15+ fields by hand.”
!导入迁移
Vega:“Review the detected changes and choose which sections to replace, while keeping everything else intact.” — 原帖
创作侧|希望发布前能私密试聊。 Nanjing 未找到这一路径。
Nanjing:“No test chat before publishing — you have to go public just to try your own bot.”
!私密试聊
消费侧|长回复与重复描写影响互动。 Nanjing 反馈每轮4–5个气泡;RedFeathers 还反馈剧情替玩家推进。创作侧需让作者的节奏约束生效。
Nanjing:“Replies are too long (4–5 bubbles per turn). Narrator repeats details already shown.”
RedFeathers:“I was just left with very little to do even if I didn’t want those things to happen.”
平台侧|作品状态显示矛盾。 Nanjing 不清楚卡片是否已公开。
Nanjing:“Chat header can say ‘Public’ while the Me page shows draft / ‘Needs attention’.”
进展:回复长度自定义已纳入计划,状态不一致待排查,均未确认解决。
范围:整理于2026-10-29。历史频道覆盖13个非官方账号,私信涉及5位作者,跨渠道重叠不累加人数;材料主要为10月21—27日,Nanjing截图未显示原发日期。以上为用户报告,未独立复现;私密试聊入口是否已有待核验。完整来源见历史证据。
Oct 29, 2026 · @gaayik
制卡结构是作者公认的卖点(5 人);最集中的痛点在制卡上手——字段看不懂、报错不定位(各 4 人);对话侧 AI 抢戏替玩家推进 3 人提及,回复过长 2 人,二者分开处理。
[embedded content: Discord #general、#creator-chat、FAQ/feedback 频道 + 4 位作者私信,按提及作者人数\]
分栏结构清晰,不用写 JSON(5 人)
[image: RedFeathers 私信\]
RedFeathers · 私信 · 10/26 · 原消息
Secrets、NPC 别家没有(3 人)
[image: ЧАЛЕЛ 私信\]
ЧАЛЕЛ · 私信 · 10/26–10/27 · 原消息
| 问题 | 类型 | 提及 | 现状 |
|---|---|---|---|
| 字段用途看不懂(哪些 AI 读、哪些玩家可见) | 制卡 | 4 人 | 承诺出新手教程 |
| 报错 20001 不指出是哪个字段 | 制卡 | 4 人 | 仅口头答复 |
| AI 抢戏,替玩家推进剧情 | 叙事 | 3 人 | 未回复 |
| 回复过长、多气泡堆叠 | 回复长度 | 2 人 | 长度设置已入计划 |
| slow burn 卡推进太快 | 叙事 | 2 人 | 未回复 |
| 描写跨轮重复 | 叙事 | 2 人 | — |
| 不能发布前私测 | 制卡 | 2 人 | 未回复 |
不列为问题:Private Notes 丢数据(内部未复现,疑似作者未保存);AI 自创 NPC 和支线(RedFeathers 测的是自己的卡,觉得偏离设定,但她本人也补充玩家看不出差别,玩家视角反而更沉浸)。
对话侧原话:slow burn 推太快、回复过长(RedFeathers),AI 抢戏(Vega)
[image: creator-chat 讨论\]
\#creator-chat · 10/23 · 原消息
制卡侧原话:字段看不懂(little\_note)
[image: little\_note 私信\]
little\_note · 私信 · 10/27 · 原消息
范围:公开频道 10/21–10/29;私信 10/24–10/29(RedFeathers、little\_note、Nanjing、ЧАЛЕЛ)。
| 反馈主题 | 中文反馈整理 | 反馈人 | 英文原文与原帖链接 | 已有回应/进展 |
|---|---|---|---|---|
| 上传后只提取了少量内容 | Vega: 上传 Manuscript 后,只抓取到少量条目,没有提取全部内容;仍在摸索合适的文件格式。 | Vega | Vega · 2026-10-23 14:15 EDT · 🎨┃creator-chat<br>原帖<br>only downside i can see, is the Manuscript upload,<br>It only grabs a small amount of entries, not all the entries.<br><br>Vega · 2026-10-23 14:21 EDT · 🎨┃creator-chat<br>原帖<br>figuring out a format | — |
| 希望用新版稿件更新已有故事 | Vega: 希望重新上传修订后的 TXT、MD 或 DOCX,由系统识别变更,再自行选择替换哪些内容,避免手动更新或重建项目。 | Vega | Vega · 2026-10-23 10:52 EDT · 💡┃feature-feedback-archive<br>原帖<br>Feature Suggestion: Update Existing Story from Manuscript<br><br>Currently, if a creator makes significant changes to their manuscript, they may have to manually update the existing character and story details or create an entirely new project. It would be much easier if we could re-upload a revised TXT, Markdown, or DOCX manuscript to an existing story, allowing Tropii to detect and update the relevant information automatically.<br><br>Ideally, creators could review the detected changes and choose which sections to replace, while keeping everything else intact. This would save time, prevent duplicate projects, and make it easier to maintain character consistency as a story develops.<br><br>Audience: Primarily creators who build and maintain characters and stories on Tropii. | 团队表示已纳入计划;本轮未确认上线。迁移后的讨论帖。<br><br>Gabby · 2026-10-23 11:27 EDT · 💬┃general<br>原帖<br>Great idea—actually, we've already added it to the plan. |
| 只有角色资料的文件能否上传 | HarjamuktiVreY: 询问能否上传只有角色资料的文件,随后表示准备使用 character sheet 制作第一张卡。 | HarjamuktiVreY | HarjamuktiVreY · 2026-10-22 08:23 EDT · 💬┃general<br>原帖<br>Also is it still ok when I only put up a file that only contains a character's data?<br><br>HarjamuktiVreY · 2026-10-22 09:37 EDT · 💬┃general<br>原帖<br>I guess I'd create my first bot using a character sheet haha | — |
| 认可结构化制卡流程 | Vega: 使用整理好的 Markdown 文件制卡,认为目前的设置方式清楚,有助于减少模型误解。 | Vega | Vega · 2026-10-22 11:30 EDT · 💬┃general<br>原帖<br>i shoved everything into a very organized .md and currently waiting on the system.<br><br>Vega · 2026-10-22 11:49 EDT · 💬┃general<br>原帖<br>i like what I see so far of the creation process. | — |
| 反馈主题 | 中文反馈整理 | 反馈人 | 英文原文与原帖链接 | 已有回应/进展 |
|---|---|---|---|---|
| Private notes 没有保存 | Nanjing: 反馈角色编辑器中的 Private notes 未保存。 | Nanjing | Nanjing · 2026-10-24 08:29 EDT · pioneer-chat<br>原帖<br>Private notes dont get saved in character creator | — |
| 20001 报错没有指出具体问题 | RedFeathers、Vega、Colin: 遇到或见过 Please check your input. (20001)。RedFeathers 后来确认自己的问题与 trigger words 超过 6 个有关;Vega 删除部分 Lorebook 条目后绕过报错,但没有确认具体原因。 | RedFeathers、Vega、Colin | RedFeathers · 2026-10-22 19:31 EDT · 💁┃help-and-faq-archive<br>原帖<br>@Gabby I'm getting an error on the Story page; "Please check your input. (20001)". How can I fix this?<br><br>RedFeathers · 2026-10-23 11:20 EDT · 💁┃help-and-faq-archive<br>原帖<br>Sorry, I wasn't clear. I meant trigger words. I had more than six trigger words in a single entry. It appears that is what caused the error.<br><br>Vega · 2026-10-23 18:17 EDT · 💬┃general<br>原帖<br>Getting Please check your input. (20001)<br>But it's not telling me *where* or show how many characters I've written in a text box<br><br>Vega · 2026-10-24 13:36 EDT · 💬┃general<br>原帖<br>for me it was the lorebook, i had to delete entries.<br><br>Colin · 2026-10-24 01:36 EDT · 💬┃general<br>原帖<br>hmm, I also saw it before | Gabby · 2026-10-23 11:21 EDT · 💁┃help-and-faq-archive<br>原帖<br>max=6 |
| 不理解两个 Lorebook 开关的区别 | RedFeathers: 不清楚 Include in card 和 Always available 分别控制什么;团队解释后,作者表示理解了。 | RedFeathers | RedFeathers · 2026-10-23 11:18 EDT · 💁┃help-and-faq-archive<br>原帖<br>Lower left corner "Include in card" ... what does it do? What I mean is ... how is it different from "Always available"?<br><br>RedFeathers · 2026-10-23 11:42 EDT · 💁┃help-and-faq-archive<br>原帖<br>OH! That's very important to know. That wasn't clear to me at all. Thank you. | Gabby · 2026-10-23 11:24 EDT · 💁┃help-and-faq-archive<br>原帖<br>Great question! They control two different things:<br><br>"Include in card" = whether the entry is ON at all.<br>Unchecked, the entry just sits in your editor as a draft and the model never sees it, no matter what the load setting says.<br><br>"Load this entry" = WHEN an included entry gets used.<br>• Always available: the model keeps it in mind for the whole chat, every message.<br>• When mentioned: the model only pulls it in when one of its trigger words comes up.<br><br>So the load setting only matters if "Include in card" is checked. Use Always for core facts the story can't forget (world rules, the main relationship), and When mentioned for side details (a magazine, a minor character, a location) so they don't crowd out the important stuff.<br><br>Unchecking is handy for drafts or for testing the card without an entry, without deleting it. Hope that helps! |
| 角色回复中的关键词是否能触发 Lorebook | RedFeathers: 观察到关键词出现在角色回复里时,条目似乎没有触发,因此询问是否只检测玩家消息。 | RedFeathers | RedFeathers · 2026-10-22 21:23 EDT · 💁┃help-and-faq-archive<br>原帖<br>Also, do lore entry triggers only fire on player messages? Because one of mine doesn't seem to be working properly when it came up in the bot's message. | — |
| 反馈主题 | 中文反馈整理 | 反馈人 | 英文原文与原帖链接 | 已有回应/进展 |
|---|---|---|---|---|
| 找不到发布前的试聊入口 | RedFeathers: 想在发布前测试角色,但没有找到入口。 | RedFeathers | RedFeathers · 2026-10-22 20:59 EDT · 💁┃help-and-faq-archive<br>原帖<br>Is it possible to test chat before publishing? I didn't see any way to do that. | — |
| 不清楚审核时长和结果通知方式 | Vega: 询问审核需要多久、如何得知通过或拒绝、是否会收到修改要求。机器人当时回复了字段字数上限,没有回答审核问题。 | Vega | Vega · 2026-10-22 12:28 EDT · 💁┃help-and-faq-archive<br>原帖<br>How long can review take, what happens if declined or approved? Are we told if anything needs to be changed? | Tropii Bot · 2026-10-22 12:28 EDT · 💁┃help-and-faq-archive<br>原帖<br>How long can each field be?<br><br>• Story title: 120 characters<br>• Opening title (optional): 160 characters<br>• Opening message: 100,000 characters<br>• Lorebook entry: title 100 characters, content 1,600 characters<br>• Secrets: the secret 600, how it can come out 400, after the reveal 600 characters<br>• Supporting characters: up to 4; appearance, relationship to the lead and overview up to 1,200 characters each<br>• All other text fields: no limit<br>• Portrait: PNG, JPEG or WebP, up to 10 MB<br>• Novel source (for adaptations): TXT, MD or DOCX, up to 10 MB<br>• Player message: 8,000 characters<br><br>How long should my character definition be?<br><br>There's no required length, and clear beats long. We suggest keeping everything about one character under about 2,000 words; past that, details may get condensed. Your characters and world stay in effect for the whole story and never get pushed out as the chat grows. |
| 卡片仍在等待审核 | Nanjing: 表示等待一天仍在审核;Vega: 随后表示自己的卡也在等待。Van: 提到两张卡待审,但未表示等待超时。 | Nanjing、Vega、Van | Nanjing · 2026-10-24 08:29 EDT · pioneer-chat<br>原帖<br>Why is my card 1 day in review<br><br>Vega · 2026-10-24 13:27 EDT · pioneer-chat<br>原帖<br>i have one in review aswell.<br>Not sure what is happening at the moment,<br><br>Van · 2026-10-22 23:20 EDT · 💬┃general<br>原帖<br>made 2 bots. currently in review me thinks | — |
| 审核中的卡能否继续编辑 | HarjamuktiVreY: 询问待审期间是否可以修改角色。 | HarjamuktiVreY | HarjamuktiVreY · 2026-10-22 09:49 EDT · 💁┃help-and-faq-archive<br>原帖<br>Does a card still under review be able to be edited? | Gabby 当时回复可以编辑。 |
| 希望增加角色链接分享按钮 | RedFeathers: 希望有 Share button,方便复制角色链接。 | RedFeathers | RedFeathers · 2026-10-23 12:07 EDT · 💡┃feature-feedback-archive<br>原帖<br>Feature Request: Share button<br><br>that's basically it. A button to share, that copies the bot's link so you can easily paste it somewhere. | 团队表示已纳入计划;本轮未确认上线。<br><br>Tropii · 2026-10-23 12:43 EDT · Share button for character links<br>原帖<br>It's already been added to the plan. |
| 反馈主题 | 中文反馈整理 | 反馈人 | 英文原文与原帖链接 | 已有回应/进展 |
|---|---|---|---|---|
| 慢热角色推进关系过快 | RedFeathers、Jane: 角色很快变得强势或主动推进关系。RedFeathers 提到,角色在故事内 14 小时就提出同居;Jane 比较不同创作路径后,觉得从零创作不那么强势,但又偏冷。 | RedFeathers、Jane | RedFeathers · 2026-10-23 11:57 EDT · 🎨┃creator-chat<br>原帖<br>I created what is supposed to be a slow-burn bot, and I also tested someone else's (is the creator of All Access - Desert Rose in here?) and it seems like the characters end up very pushy very quickly, not really slow burn at all. Like immediately small touches, etc. and my character ended up suggesting we move in together within 14 hours in story time. Is it the platform that's doing this?<br><br>Jane · 2026-10-23 20:06 EDT · 🎨┃creator-chat<br>原帖<br>Had the same I added some restrictions hope he wont be that forcy anymore<br><br>Jane · 2026-10-23 20:08 EDT · 🎨┃creator-chat<br>原帖<br>I made one on default and one from scratch and one with the Adapt thingy and the one from scratch is not that pushy but somehow cold af haha I have to test more to see how to find the middle way | — |
| 回复太长,玩家参与空间小 | RedFeathers: 一回合出现多段长回复,玩家主要是在阅读和回答问题,参与感不足。 | RedFeathers | RedFeathers · 2026-10-23 11:58 EDT · 🎨┃creator-chat<br>原帖<br>Also ... is there any way to control how much the bot writes in a turn. Because it writes several very long replies, all stacked together, and I feel like as the player, I get hardly any chance to do anything except read a huge wall of text and answer a bunch of questions. | — |
| AI 跳过或代写玩家行动 | Vega: 玩家说“给我 10 分钟”,AI 就直接写成玩家已经回来。RedFeathers: 表示有同感,增加叙事限制也没有奏效。 | Vega、RedFeathers | Vega · 2026-10-23 12:00 EDT · 🎨┃creator-chat<br>原帖<br>i found with my own bot, there is slight narration hogging by the AI.<br>I said to character eg ' give me 10 minutes to do such and such.' to wait and the narration just then jumps to me returning, even though i hadn't given any indication of a return, let alone had my interaction with a npc. But i'll figure it out ig<br><br>RedFeathers · 2026-10-23 12:02 EDT · 🎨┃creator-chat<br>原帖<br>Glad to know I'm not the only one ... I even tried putting things in the Narration rules about it, but it didn't seem to help | — |
| Lambert 互测:有好评,也有重复和抢行动问题 | tbma: 总体评价为 Good,肯定人物、环境与对话;同时指出重复描写、临时 NPC 频繁打断、主线被拉长,以及替玩家决定动作等问题。以下保留同一份完整反馈,不拆散到多个位置。 | tbma | tbma · 2026-10-23 06:27 EDT · Lambert Of Kaer Morhen + The Stranger (Player)<br>原帖<br>BOT FEEDBACK — Lambert of Kaer Morhen + The Stranger (Player)<br><br>Overall Experience:Good<br><br>Character Behavior<br>Feedback:<br>↳ Lambert serves his role as the lead! He's cynical, blunt, sarcastic, and aggressive, which makes his personality fit with the setting. He shows his care through soft words, which is nice and unlike his norm. Geralt feels recognizable, but Ciri, Eskel, and Vesemir do not appear enough to judge properly.<br><br>Narration & Immersion<br>Feedback:<br>↳ The Velen atmosphere is vivid and the combat is easy to picture. However the descriptions of mud, rain, rot, and swamp smells repeat too often. It kind of slows down the plot in my opinion<br><br>Dialogue & Interactions<br>Feedback:<br>↳ His dialogue feels natural and distinct, responds well to sarcasm and jokes too. The banter is entertaining, but the story introduces too many side characters and interruptions after the drowner contract.<br><br>Player Agency<br>Feedback:<br>↳ I was able to make pretty cool choices, especially during combat! It usually avoids describing my emotions but sometimes would choose my actions for me.<br><br>Issues & Bugs<br>Repeated descriptions of mud, rain, swamp water, and bad smells.<br>Too many NPC interruptions make the main contract feel stretched.<br>Some protective gestures from Lambert repeat too often.<br>The narration occasionally stacks too many descriptions into one paragraph.<br><br>Examples (if applicable):<br>↳ You swing downward, your steel edge biting into rubbery clavicle and sending thick ichor splashing across the mud. (Chose my action)<br><br>Suggestions for Improvement<br>• Suggestion 1: Reduce the number of side characters appearing in one sequence.<br>• Suggestion 2: Give Eskel, Vesemir, and Ciri clearer moments to show their personalities.<br>• Suggestion 3: Let the player control their own combat actions.<br><br>Final Verdict:<br>Minor adjustments needed<br><br>T | — |
| 希望使用第三人称,但仍被写成 you | Van: 希望角色使用第三人称叙述,但输出仍以 you 称呼玩家。tbma: 也表达了对第三人称的偏好。 | Van、tbma | Van · 2026-10-23 03:17 EDT · 💬┃general<br>原帖<br>also has anyone tried to write the bot in 3rd POV? i've only gotten bots to reply and write user/player as you<br><br>tbma · 2026-10-23 03:35 EDT · 💬┃general<br>原帖<br>still not beyond my wattpad days smh i still dig 3rd POV hahahahahah | — |
| 希望切换聊天语言或自动翻译 | Olivia: 希望单次聊天可以切换语言或自动翻译,具体提到意大利语。团队回复可以用意大利语输入,角色用英文输出。 | Olivia | Olivia · 2026-10-22 08:42 EDT · 💁┃help-and-faq-archive<br>原帖<br>How can I change the language or enable automatic translation in a single chat? | Gabby · 2026-10-22 09:13 EDT · 💁┃help-and-faq-archive<br>原帖<br>u can chat in Italian but it replies in English |
| 固定文本的引用不一致 | 团队测试与作者回应: Gabby 测试 Seo Jun 时发现,同一评论的逐字引用出现不同版本。RedFeathers 表示已配置 Always-on Lorebook,并考虑移除允许改述的表述。这是团队测试上下文,不计为额外一位用户投诉。 | Gabby、RedFeathers | Gabby · 2026-10-23 12:10 EDT · He Doesn't Know It Was You | Kang Seo Jun (강서준)<br>原帖(节选)<br>His history held up beautifully: Jeonju, the word "timid," the lost Seoul commission, the studio running on savings, and Yuna's "bitter old man" theory . Even the details he made up himself stayed consistent!<br>The one thing that drifted is the review quote. I asked for it word for word three times and got three different versions:<br>• "A retreat disguised as subtlety… a building that apologizes for occupying space."<br>• "A timid gesture dressed in modesty, mistaking withdrawal for virtue."<br>• "An architect who mistakes modesty for virtue, producing a public hall so quiet it refuses to exist." (no "timid" this time )<br><br>RedFeathers · 2026-10-23 12:20 EDT · He Doesn't Know It Was You | Kang Seo Jun (강서준)<br>原帖<br>Thank you so much!!<br><br>I already had the review as an "always on" lorebook entry like this:<br><br>Lintel's review of the Jeonju community center ran in Munteok eight months ago. It was about the Jeonju building only; it never mentioned Home. Seo Jun knows the published text by heart: "The best thing in Jeonju is a window, and Kang knows it; he steps out of its way. The doorways are generous, the light is careful, and nothing in the building is willing to raise its voice. Kang Seo Jun builds the way some people listen, so completely that you forget he's there. Call it humility. I call it timid. What would Kang build if he stopped asking permission?" He quotes or paraphrases only these lines; the review says nothing else. He pretends he can't quote it.<br><br>The review cost his studio a major cultural-center commission in Seoul. He has never learned who Lintel is.<br><br>The user's original draft read: "Kang Seo Jun builds the way some people listen, so completely that you forget he's there. It's a rare gift, and occasionally a risk." It never used the word "timid." The editor changed it.<br><br>RedFeathers · 2026-10-23 12:21 EDT · He Doesn't Know It Was You | Kang Seo Jun (강서준)<br>原帖<br>@Gabby Oh maybe I should get rid of "paraphrases" so he only directly quotes? | — |
| 反馈主题 | 中文反馈整理 | 反馈人 | 英文原文与原帖链接 | 已有回应/进展 |
|---|---|---|---|---|
| 不知道反馈应该发在哪个频道 | RedFeathers: 询问是否应在 Pioneer 聊天区反馈,以及其他成员是否也都是 Pioneer。 | RedFeathers | RedFeathers · 2026-10-23 11:43 EDT · pioneer-chat<br>原帖<br>If I want to put some general feedback about Tropii, is this the right place to put it?<br><br>RedFeathers · 2026-10-23 11:45 EDT · 💁┃help-and-faq-archive<br>原帖<br>Is everyone currently a "pioneer" -- should we use the pioneer-chat at this stage to talk to each other? | 团队引导到 creator-chat。 |
以下为其他参与者的发言,不均属于产品问题。
| 反馈主题 | 中文反馈整理 | 反馈人 | 英文原文与原帖链接 | 已有回应/进展 |
|---|---|---|---|---|
| Hardgore:角色构思卡住 | 讨论创作构思和使用的应用,没有明确反馈 Tropii 功能故障。 | Hardgore | Hardgore · 2026-10-22 07:10 EDT · 💬┃general<br>原帖<br>I'm actually trying to come up with more characters lol I'm having a blockage in my brain | — |
| rosechyme:正在制作角色 | 表示想把内容写得充分,因此进度较慢,没有归因于工具故障。 | rosechyme | rosechyme · 2026-10-22 08:56 EDT · 💬┃general<br>原帖<br>I've started creating, but progress is slow because I want it to be really fleshed out! | — |
| Rag:更偏向玩家,愿意体验熟悉作者的作品 | 表示通常只有找不到想玩的内容时才会自己创作。 | Rag D'Mezzegis | Rag D'Mezzegis · 2026-10-22 09:21 EDT · 💬┃general<br>原帖<br>im more of a player but i sometimes create when i cant find something i want.. so ill be glad to play some bots when they come | — |
| Colin:喜欢已体验的作品 | 表达对游玩体验的肯定,以及继续体验更多内容的兴趣;其 20001 报错附和已放在对应问题下。 | Colin | Colin · 2026-10-23 00:04 EDT · 💬┃general<br>原帖<br>I love it a lot, and Geralt has come, love them all, I went through first combat with Lambert, now hoping to see more characters. | — |
| nanoirelle:询问其他平台的个人资料装饰 | 这条是在询问 Janitor AI 的资料装饰代码,不是 Tropii 功能反馈。 | nαnoi dun sαmyαng! | nαnoi dun sαmyαng! · 2026-10-22 08:03 EDT · 💬┃general<br>原帖<br>anyone know how to use code for decoration profile j.ai? 😞✋ | — |
更新:2026-10-29
| 体验 | 简洁归纳 | 创作者原文节选/来源 |
|---|---|---|
| 创作工具 | 四步流程清楚;Secrets、开场预览和结构化字段有辨识度。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“The four-step flow … is intuitive.”/“Secrets are structured really well.”;RedFeathers:“especially not having to create JSON files!!” [截图2](反馈证据/创作者私信_2026-10-27/私信截图_02.png) |
| 角色与情绪 | 角色能保持人设,细节具体,动机和情绪回应有说服力。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“Bot stayed sharp and in character with concrete details.”/“a personal, grounded answer”;RedFeathers:“stay true to their personality.” [截图3](反馈证据/创作者私信_2026-10-27/私信截图_03.png) |
| 文字与节奏 | 有创意、氛围好;部分会话能按玩家要求放慢。 | ЧАЛЕЛ:“innovative and genuinely long and detailed.” [截图4](反馈证据/创作者私信_2026-10-27/私信截图_04.png);[Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“when I asked to slow down, it shifted the scene naturally.” |
| 所属侧/主题 | 问题与需求 | 创作者原文节选/来源 |
|---|---|---|
| 创作侧:保存可靠性 | Private Notes 丢失,甚至显示 Saved 后刷新为空;需要可靠保存。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“Adding a supporting character wiped the lead's Private notes.”;Nanjing:“Private notes dont get saved in character creator.” 频道原帖 |
| 创作侧:规则与可见性 | 报错不指明字段;不清楚哪些内容公开、哪些供 AI 使用,字段边界也难理解。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“(20001) with no field highlighted”/“Easy to accidentally leak AI-only notes or spoil reveals.”;RedFeathers:“didn't have much instruction on what was needed where.” [截图3](反馈证据/创作者私信_2026-10-27/私信截图_03.png) |
| 创作侧:导入与更新 | 小说解析失败、提取不全;跨平台迁移需手填大量字段,希望导入角色卡、用修订稿更新已有故事。 | Vega:“It only grabs a small amount of entries.” 原帖;[Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“pasting 15+ fields by hand”;Vega 更新稿件长帖 |
| 创作侧:编辑与试聊 | 新条目难找、备注与人物分离;希望发布前能私密试聊。 | RedFeathers:“you have to search for it.” [截图3](反馈证据/创作者私信_2026-10-27/私信截图_03.png);[Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“Add a private sandbox chat before publish.” |
| 消费侧:长度与玩家参与 | 多气泡、重复描写、剧情推进太快;希望控制长度和节奏,不被代替行动。创作工具需让作者的节奏约束生效。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“Replies are too long (4–5 bubbles per turn).”;ЧАЛЕЛ:“moved forward very quickly in the plot/actions.” [截图4](反馈证据/创作者私信_2026-10-27/私信截图_04.png);RedFeathers:“very little to do.” [截图3](反馈证据/创作者私信_2026-10-27/私信截图_03.png) |
| 消费侧:连贯性与自由度 | 偶有逻辑错位、偏离设定;希望局部重试,以及自定义玩家身份、语言。创作工具需区分固定设定与玩家可改部分。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“Minor spatial/logic slips”;RedFeathers:“no way to backtrack or try again.” [截图3](反馈证据/创作者私信_2026-10-27/私信截图_03.png);Darkneblade:“user can create their own character.” [截图6](反馈证据/创作者私信_2026-10-27/私信截图_06.png) |
| 平台治理:状态一致性 | 聊天页与个人页状态不同,难判断作品是否公开。 | [Nanjing](反馈证据/创作者私信_2026-10-29/Nanjing_创作与聊天反馈.png):“Chat header can say ‘Public’ while the Me page shows draft / ‘Needs attention’.” |
团队回复进展:Gabby 已向 Nanjing 回复“回复长度自定义已纳入计划”;卡片状态不一致将排查是否为 Bug。均未确认上线/解决。
已处理/澄清:默认名字与隐私已解决;待审可编辑;人审已有 Bot 通知运营;Discord 已有反馈指引。以上不列为待补功能。
<details>
<summary>展开:RedFeathers、ЧАЛЕЛ、Nanjing 私信原文截图</summary>
</details>
<details>
<summary>展开:完整原文摘录、历史反馈与逐条来源</summary>
| 主题 | 原文 |
|---|---|
| 数据丢失 | “Adding a supporting character wiped the lead's Private notes.” “Typing into a collapsed notes box silently ate the text.” “After reload, notes showed empty despite ‘Saved’” |
| 校验 | “‘Please check your input. (20001)’ with no field highlighted” “trigger words need one-per-line, not comma-separated” |
| 可见性 | “Story setup and Relationship fields are player-facing, but nothing says that.” “Easy to accidentally leak AI-only notes or spoil reveals” |
| 试聊 | “No test chat before publishing — you have to go public just to try your own bot” “Add a private sandbox chat before publish” |
| 字段重叠 | “Lorebook ‘Supporting character / NPC’ vs the Characters step, lorebook ‘Past event’ vs Secrets — unclear which takes priority” |
| 输入与标签 | “Add a public/AI-only indicator on every field + character counters on long text boxes” “Show trigger-word format in placeholder text, or just accept commas. Name the failing field in errors” “Explain ‘Default’ vs ‘Free’ narrative mode. More tropes/tags (School, Tsundere, Sports…)” |
| 迁移 | “Support JSON / character-card import — copying a card from another platform meant pasting 15+ fields by hand” |
| 聊天问题 | “Replies are too long (4–5 bubbles per turn). Narrator repeats details already shown” “Repetitive descriptive focus across turns” “Minor spatial/logic slips and occasional question-dodging on the first try” |
| 长度与状态 | “A reply-length setting or ‘shorter’ button would help a lot” “Chat header can say ‘Public’ while the Me page shows draft / ‘Needs attention’” |
| 创作好评 | “The four-step flow (Story → Characters → Opening → Preview) is intuitive, and drafts autosave” “Secrets are structured really well” “The Opening step's live preview with scene/character blocks is great” “Director's brief for flavors/tropes where order = priority is a nice touch” |
| 聊天好评 | “Bot stayed sharp and in character with concrete details” “Each turn ended with a clear hook” “the bot gave a personal, grounded answer instead of deflecting” “when I asked to slow down, it shifted the scene naturally without punishing me for it” |
以下用户反馈表中的“需求”是对用户目标的简洁归纳,非研发方案或排期;疑问、偏好与已发生的问题分别标明。每条附来源,英文引文均为节选。
| 功能/主题 | 用户反馈的问题 | 用户需求 | 反馈人及来源/关键原文 |
|---|---|---|---|
| 文件解析失败 | Darkneblade 的 DOCX 多次解析失败;其表示文件仅 378 KB,另一些 DOCX 可用,后来反复尝试成功。 | 稳定导入;明确文件大小、文本长度及内容结构限制,失败原因可理解。 | Darkneblade [私信·图8](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_08.png>)、[私信·图9](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_09.png>)、[私信·图10](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_10.png>)<br>“this is 378 kb”; “and it still fails”; “it eventually worked” |
| 提取不完整 | Vega 反馈只提取少量条目;Darkneblade 反馈多个地点只抓取主要地点。 | 更完整地保留原稿中的条目和地点。 | Vega 原帖;Darkneblade [私信·图10](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_10.png>)<br>“It only grabs a small amount of entries”; “it only grab the important one.” |
| 已有故事更新 | 修订稿件后,需要手动更新角色/故事或重建项目。 | ① 向已有故事重传 TXT/Markdown/DOCX 修订稿;② 自动识别变更并更新相关角色/故事资料;③ 先查看变更,再选择替换哪些部分;④ 未选部分保持不变,避免重复建项目和设定不一致。 | Vega 原帖<br>Tropii 代发完整长帖<br>“re-upload a revised TXT, Markdown, or DOCX manuscript to an existing story”<br>“review the detected changes and choose which sections to replace, while keeping everything else intact.” 团队已回复纳入计划,非上线确认。 |
| 导入素材与跨平台迁移 | HarjamuktiVreY 询问纯角色资料能否导入;Darkneblade 将 FictionLab JSON 转 DOCX 导入,过程不顺。 | 支持角色档案及已有平台设定的导入/迁移,清楚说明支持哪些素材。 | HarjamuktiVreY 原帖;Darkneblade [私信·图10](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_10.png>)<br>“export my scenerio in fictionlab as .json then convert .json to docx” |
| 功能/主题 | 用户反馈的问题 | 用户需求 | 反馈人及来源/关键原文 |
|---|---|---|---|
| 上手说明与旧提示词迁移 | RedFeathers 不知道各字段该填什么;ЧАЛЕЛ 习惯其他平台整段 prompts,逐字段拆填困难。 | 带示例的完整创作者指南;降低已有设定迁移到结构化字段的理解成本。 | RedFeathers [私信·图2](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_02.png>)、[私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>);ЧАЛЕЛ [私信·图4](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_04.png>)<br>“A comprehensive creator guide would be helpful, with examples.” |
| 新增条目的位置 | 新增 Lorebook/Secrets 后,空白卡片出现在页面下方,需要寻找。 | 新增后就在当前可见位置继续填写,减少找条目和滚动。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>)<br>“it moves it down on the page and you have to search for it.” |
| Private Notes 布局 | Private Notes 独立放在下方,与人物设置分离。 | 将 Private Notes 放在对应人物设置旁边。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>)<br>“Private Notes grouped right next to the character setup” <br>公开原帖;团队回复会考虑,未确认上线。 |
| Private Notes 保存 | 角色编辑器中的 Private notes 没有保存。 | 填写的备注能够保存并保留。 | Nanjing 原帖<br>“Private notes dont get saved in character creator” |
| 校验报错与上限提示 | 20001 不指出错误字段/数量;RedFeathers 后来确认触发词超过 6 个,Vega 删除条目绕过但原因未明。 | 知道哪里超限、限多少、如何改,不靠反复删除试错。 | RedFeathers 原帖;Vega 原帖;Colin 原帖<br>“not telling me where” |
| Lorebook 加载与触发规则 | 不理解 Include in card/Always available;询问 When mentioned 是否检测角色回复,以及长上下文中固定条目是否被摘要。 | 明确开关、触发范围与固定设定保留方式。 | RedFeathers 原帖、[私信·图1](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_01.png>)<br>“that stays verbatim, right, not summarized?” 私信中 Gabby 已答两侧消息均触发、卡片保留原文;属于当时答复,非独立技术验证。 |
| 复杂设定与表达自由 | 认为 tropes/story flavors 可能限制创作;未找到 trackers 等入口,担心难表达非标准人物动态;尚未实际尝试该类角色。 | 保留自定义、状态追踪及非标准角色动态的表达空间。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>)<br>“I haven’t seen that you can put in trackers anywhere” (可发现性/自由度诉求,非已证实不支持。) |
| Preview 入口与含义 | 找不到发布前试聊入口;另询问 Preview 是否先按输入“构建”故事或脚本。 | 能找到预览,并理解预览会做什么。 | RedFeathers 原帖、[私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>)<br>“what happens during the Preview process” |
| 功能/主题 | 用户反馈的问题 | 用户需求 | 反馈人及来源/关键原文 |
|---|---|---|---|
| 剧情推进与玩家行动权 | Vega、RedFeathers、tbma、ЧАЛЕЛ 均涉及跳过/代写玩家行动或推进过快;RedFeathers 表示 Narration 限制未奏效。 | 等待玩家选择与行动,不擅自替玩家推进;创作者设置的叙事约束能生效。 | Vega 原帖;tbma 原帖;RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>);ЧАЛЕЛ [私信·图4](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_04.png>)<br>“very little to do even if I didn’t want those things to happen” |
| 回复长度与互动节奏 | RedFeathers 不喜欢长回复、多气泡压缩参与空间;ЧАЛЕЛ 肯定长而详细、有创意的回复。 | 保留细节和氛围,同时给玩家插入行动的空间;长度偏好存在差异。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>);ЧАЛЕЛ [私信·图4](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_04.png>)<br>“Replies are VERY long”/“innovative and genuinely long and detailed” |
| 关系推进/慢热 | 角色很快强势、亲近;Jane 从零创作的角色又偏冷。 | 关系推进符合慢热设定,有自然的中间过程。 | RedFeathers 原帖;Jane 原帖<br>同居发生在故事内 14 小时为 RedFeathers 的个案描述。 |
| 回退或重试 | RedFeathers 表示遇到不想要的剧情后,未找到回退/重试方式,只能新开聊天。 | 能够回退或重试局部对话,避免完全重开。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>)<br>“There is no way to backtrack or try again” (用户所见,未独立核验功能。) |
| 剧情偏离、重复与固定设定 | RedFeathers 反馈新增原故事没有的人物/情节;tbma 反馈重复描写、NPC 打断;Seo Jun 团队测试出现固定引文漂移。 | 原创情节和固定信息能保留;减少重复、无关插入及精确内容漂移。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>);tbma 原帖;团队测试<br>“invent new characters and plot directions that were not in the original story” |
| 自定义玩家 Persona | Darkneblade 认为固定玩家名字、性格限制体验,希望自己带入身份;允许作者限定基本关系/角色位置。 | 开聊前可定义玩家名字、背景和个性,角色能适应;创作侧需区分故事必需身份与玩家可改字段。 | Darkneblade [私信·图5](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_05.png>)、[私信·图6](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_06.png>)、[私信·图7](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_07.png>)<br>“creator can place users role. But user can create their own character” (个人开放玩法偏好,含上线前讨论。) |
| 叙述视角偏好 | Van 想用第三人称,但回复仍使用 you;tbma 也偏好第三人称。当前视角由创作者的叙事引导决定,遵循作者规则,不能据此认定功能失效。 | 用户希望按个人偏好调整当前聊天的视角;OOC 调整属于下方运营新增需求,非用户原话或已支持能力。 | Van 原帖;tbma 原帖 |
| 语言与本地化 | Olivia 希望聊天语言切换/翻译;ЧАЛЕЛ 希望母语界面减轻制卡负担。 | 聊天语言选择与创作界面本地化;两者是不同诉求。 | Olivia 原帖;ЧАЛЕЛ [私信·图4](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_04.png>)<br>“available in my native language” (截图未明确语言名。) |
| 模型与 OOC 说明 | RedFeathers 询问后端模型、是否一直只用一种模型,以及 OOC 指令是否有效。 | 知道当前模型及可选范围、是否支持跳出角色进行指令沟通;多模型为询问,尚非明确必需需求。 | RedFeathers [私信·图1](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_01.png>)、[私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>)<br>“Is it just going to stay with one model?”/“do you know if they would work?” |
| 功能/主题 | 用户反馈的问题 | 用户需求 | 反馈人及来源/关键原文 |
|---|---|---|---|
| 作品分享 | 希望方便复制角色链接。 | 增加直接分享/复制角色链接的入口。 | RedFeathers 原帖;团队已回复纳入计划,未确认上线。 |
| 功能/主题 | 用户反馈的问题 | 用户需求 | 反馈人及来源/关键原文 |
|---|---|---|---|
| 结构化创作工具 | Vega 喜欢制卡流程;RedFeathers 认可字段拆分、无需手写 JSON、Secrets、图片生成和开场 Custom speakers。 | 已有正向反馈,不转写为新增功能要求。 | Vega 原帖;RedFeathers [私信·图2](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_02.png>)<br>“especially not having to create JSON files!!” <br>肖像生成好评原帖 |
| 聊天表现与界面 | RedFeathers 肯定界面清楚、人物性格与氛围;ЧАЛЕЛ 肯定创意和细节;tbma、Colin 肯定具体作品。 | 保留与负面反馈并存的好评,不推为平台整体满意。 | RedFeathers [私信·图3](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_03.png>);ЧАЛЕЛ [私信·图4](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_04.png>);tbma 原帖;Colin 原帖 |
以下三项由运营于 2026-10-27 在本任务提出,不计入创作者反馈样本;均为待实现/评估需求,不表示已经上线。
| 所属侧/功能 | 运营需求 | 说明与边界 | 来源 |
|---|---|---|---|
| 消费侧/OOC 调整叙述视角 | 允许玩家通过 OOC 指令调整当前会话的叙述视角,例如“请改用第三人称叙述”。 | 当前默认遵循作者的叙事引导;后续需明确视角指令与作者规则的优先级。仅改变当前会话的叙述方式,不改原角色卡,不扩展为覆盖人物设定或核心剧情规则;创作工具需明确向作者说明该边界。 | 运营提出,本任务 2026-10-27 确认。 |
| 平台治理/审核状态调整 | 已经审核通过的卡片,支持运营重新更改审核状态。 | 避免通过后状态无法调整;可切换的状态范围及对已发布卡片的影响待产品定义。 | 运营提出,本任务 2026-10-27。 |
| 平台治理/不通过理由 | 审核选择“不通过”时,可选择预设的理由大类。 | 统一记录不通过原因;具体分类待确认,本稿不擅自新增审核标准。 | 运营提出,本任务 2026-10-27。 |
以下保留历史来源,仅作状态回溯;不纳入上方未处理问题。状态依据用户本轮确认。
| 历史反馈 | 当前状态 | 历史来源 |
|---|---|---|
| 默认名字与隐私 | 已解决。 不再列为待处理产品问题。 | [私信·图9](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_09.png>) |
| 审核状态与结果 | 已有运营处理机制。 当前为人工审核;Bot 已及时通知运营审卡,避免过长等待。该措施不等同于新增用户端审核状态/拒绝理由功能,本文不将后者记为已上线。 | 原帖;原帖;[私信·图9](</Users/gaayik/Documents/Gemini/运营/tropii-运营/04_消费侧_Discord社区运营/上线后用户反馈简报与需求表/反馈证据/创作者私信_2026-10-27/私信截图_09.png>) |
| 审核期间编辑 | 已支持。 待审期间可以编辑,不再列为功能缺口。 | 原帖 |
| 反馈入口与自动答疑 | 社区指引已明确,非产品问题。 按用户确认移出产品问题表。 | 原帖;机器人回复 |
</details>