40/41 · Part 7 · FAQ · AlterU Training

Part 7 · 散场前 · 常被问到的问题

最后这 6 个，
大家都会问。

我做完游戏怎么发布？

在平台内预览页打开看效果 → 满意了点"发布"按钮。入库自动完成，不用碰 UUID / meta.json / 部署脚本。你只负责到"满意"为止。

我必须用 AI 吗？

不一定。Sensory toy 完全靠手做也很棒（Bubble Wrap / Marbles / Wind Chime）。但身份层 + 社交动词几乎不能少——否则不算 AlterU 游戏。

5-8s 生图等待怎么办？

等待变成玩法，不要 spinner 糊过去。化学浴显影 / 拆封 / 显形 / 翻档案的视觉仪式。Kiss Wall canonical 范式 ⑥。

新手教程要不要做？

不要。任何教程都假设玩家有耐心读 → 划走。第一次失败本身就是教程。Sky Leap 把充能环教学砍成 1 个共用手指 icon。

用户反馈短语对应改什么？

"太复杂" → 砍规则
"social 太弱" → 加 verb + notify
"看不下去" → 砍卡通脸贴纸
"没耐心" → 砍引导 setup
"太平淡" → 加 visceral 感官冲击

不会编程能做吗？

可以。AlterU 给 maker 两种零代码模式：
① One sentence — 一句话描述,AI 补完美术 / 代码 / 声音 / 台词。
② Remix — 从 feed 挑一个游戏,改规则 / 换世界,发布你的版本。

Part 7 · Before we wrap · the recurring questions

Six things
everyone asks.

How do I ship?

Open the preview inside the platform → check the result → tap the Publish button. Registration is automated. You're done at "happy" — no UUIDs, no meta.json, no deploy scripts.

Do I have to use AI?

No. Sensory toys are pure hand-craft (Bubble Wrap / Marbles / Wind Chime). But the identity layer + social verb are nearly always required — otherwise it isn't really an AlterU game.

What about the 5-8s gen-image wait?

Turn the wait into the play — never a spinner. Darkroom develop / sealing / form / archive flip. Kiss Wall is the canon (paradigm ⑥).

Should I add a tutorial?

No. Tutorials assume patience → swipe. The first failure is the tutorial. Sky Leap cut its charge-ring animation down to one shared finger icon.

Mapping player feedback?

"too complex" → cut rules
"social weak" → add verb + notify
"can't watch this" → drop sticker face
"no patience" → drop setup / tutorial
"too flat" → add visceral hits

Can I build without coding?

Yes. AlterU gives makers two zero-code modes:
① One sentence — describe the game in one line, AI fills in art / code / sound / voice.
② Remix — pick a game from the feed, twist the rules, swap the world, ship your version.

备忘 · 按 S 关闭Notes · S to close

这一节给学员"散场前确认"的机会。每个问题都是新人最常踩的疑虑。如果时间够，可以让每个 Q 让一两个学员说自己的理解，再给标准答案。

Q1 是平台简化后的关键消息——很多老 deck 还在讲 UUID / meta.json / 部署脚本，实际上平台已经把这些自动化了。设计师/产品只负责到"满意"为止，点发布即入库。所以用粉色描边突出这一格。

Q5 反馈语言模板是这套 deck 最实用的"日常工具"。建议同学保存进自己的 system prompt 模板，下次开 idea 时直接套。

Q6 对应 landing 的 Makers 3-card（One sentence / Remix / Soon）。这是 maker 最大顾虑的问题——给他们"零门槛"心理安全感。如果讲师被问 "AlterU 和 Aigram 什么关系"：AlterU = 独立新品牌（试美国市场，App Store 端）；Aigram = 底层技术 infra（iframe 桥 + API）。对外只说 AlterU，Aigram 只在 endpoint 表里出现。这个不放进幻灯片，对外 maker 不需要知道。

The wrap-up Q&A. Each question is something newcomers stumble on. If you have time, let one or two attendees take a crack at each Q before you give the canonical answer.

Q1 is the key updated message — older versions of this deck still walked people through UUID / meta.json / deploy scripts. The platform automated all of that. Designers and PMs are done at "happy", then tap Publish. Q1 is pink-bordered for a reason.

Q5 is the most useful daily tool in the whole deck. Have students paste these mappings into their personal system-prompt template — next time an idea comes in, they can route by phrase.

Q6 lines up with the landing Makers 3-card (One sentence / Remix / Soon). This is the question that gives makers the "no barrier" psychological green light. If anyone asks "what's the relationship between AlterU and Aigram": AlterU = standalone new brand (US market, App Store). Aigram = underlying tech infra (iframe bridge + API). Externally always say AlterU; Aigram only shows up in the endpoint table. Don't put this on the slide — outside makers don't need to know.

最后这 6 个，大家都会问。