https://www.youtube.com/@LunaticDiceGames

这是我的 YouTube 频道，如果你想观看未来的开发日志和更新。

NOTE: I had my Claude Code make a short summary of what my workflow is since it knows it better than I do, but I curated it and made sure it was useful and, well, my edits!

注意：我让我的 Claude Code 为我写了一个关于工作流程的简短总结，因为它比我更了解，但我筛选了内容并确保它有用，好吧，我的修改！

嗨，大家。我全职经营 Pathfinder 2e 游戏，且不会编程。自五月以来，我一直在构建 The Shattered Isles，一款运行真实 PF2e 规则的回合制战术游戏，几乎全部使用 AI 实现。上面的视频展示了我做的成果。下面是我的工作方式。

Code

  • Godot 4.6 with C#. I don’t read the code. I describe what I want in plain English and judge it by playing it.

  • Godot 4.6 与 C#。我不阅读代码，而是用简洁的英文描述我想要的，并通过玩游戏来判断。

  • Claude Code (Opus 5.5) is the director. It plans, asks me questions, writes the briefs for the workers and reads the finished code.

  • Claude Code (Opus 5.5) 是导演。它制定计划，向我提问，为工人编写任务说明，并阅读完成的代码。

  • Codex (GPT) workers do most of the building. The model that wrote something never reviews it; a different one always checks it.

  • Codex (GPT) 工人负责大部分构建。写了东西的模型永不审查它；另一个模型总是进行检查。

  • The project’s rulebook file is the most important file in the repo. When the AI makes the same mistake twice, the mistake gets a rule or a little guard script that blocks it.

  • 项目的规则书文件是仓库中最重要的文件。当 AI 连续两次犯同一个错误时，该错误会得到一个规则或一个小型守卫脚本来阻止它。

  • Every rule is checked against the live Archives of Nethys (the rulebook) page before it ships. Nothing from memory.

  • 每条规则在发布前都会与 Nethys 实时存档（规则书）页面进行核对。不凭记忆。

  • Tests run every night, so the day is just building and playing.

  • 测试每晚运行，因此白天仅用于构建和游玩。

Art and sound

  • Sprites and animations: PixelLab

  • 精灵和动画：PixelLab

  • Music: Suno

  • 音乐：Suno

  • Voices: ElevenLabs

  • 配音：ElevenLabs

What I’ve learned

  • The AI doesn’t have taste. You do. I make every looks, gameplay, design, and feel call myself.

  • AI 没有品味。你有。我对外观、游戏体验、设计以及整体感觉全部自行决定。

  • Make it ask you questions before it builds. Most of my bad builds came from it guessing what I meant. Seriously, Claude is an idiot if you let it make decisions.

  • 在构建前让它先向你提问。我的大多数糟糕构建都源于它猜测我的意图。认真说，如果让 Claude 做决定，它就是个傻瓜。

  • Build in small chunks you can play in one sitting. ALWAYS playtest a change, no matter how minor, before implementing, or it WILL bite you.

  • 以小块方式构建，每块都能在一次游玩中完成。无论改动多小，在实施前务必进行游戏测试，否则它一定会咬你。

  • Write your decisions down in files, so the next chat doesn’t re-ask them or undo them. I have an extensive document tree, almost like the bones of this project.

  • 将你的决定写入文件，以便下次聊天不会重新提问或撤销它们。我拥有广泛的文档树，几乎像是本项目的骨架。

大约 4,800 次提交后，仍有大量工作待完成。很乐意回答关于任何内容的问题。我并不超级技术化，所以 Claude 可能会替我回答，随后我会进行编辑。

Steam: https://store.steampowered.com/app/4941850/?utm_source=reddit&utm_medium=video&utm_campaign=reveal