开发者分享Claude Code与Unity 6自动化工作流
AI 总结
一名匿名游戏开发者在五周实验中，使用Claude Code、Opus 5.5和Unity 6编写大部分C#代码，并通过MCP检查和修改场景、截取画面及运行游戏测试。该流程还使用Tripo AI和SmartMesh P2生成低多边形3D资产，使用Blender与MCP清理模型，并以独立Claude会话分别处理设计、编程和美术。开发者称，原先需要数天或数周的概念验证如今约一天即可完成，但创意决策和反复试玩仍由人工完成；效率数据均为个人自述。
深度见解
该案例具体展示了如何将编程智能体、编辑器控制、3D资产工具和外部检查组合成无人值守的游戏开发循环，同时也说明人工创意判断和试玩仍然关键。
| The game revolves around driving machinery into dense fields, clearing crops and spending the earnings on upgrades and new land. A relaxed, deliberately unrealistic farming game focused on satisfying harvesting and increasingly oversized equipment. The stack The automated part Plans, design ideas and playtesting feedback became a backlog of task cards. Dedicated Claude sessions handled design, programming and art, each with separate instructions and a Git branch. A runner script picked up one card at a time, assigned a time and spending limit, and kept development moving while unattended — including overnight. Completed tasks went through checks outside the agent’s own assessment: building the game headlessly, running tests, driving the tractor to check handling and capturing screenshots. Changes were merged only after passing those checks. Failed tasks waited for manual review. Morning reviews turned the results into another round of feedback and new task cards, creating a repeatable cycle of implementation, testing and refinement. Prototyping that previously took days or weeks could now happen in roughly a day. The starting point was a rough playable version, followed by iteration on the core gameplay loop, controls and camera. Creative direction remained hands-on. Harvesting mechanics, crops, vehicle movement, machinery design and environment layouts still required repeated playtesting and adjustments. submitted by /u/Delicious-Shower8401 [link] [comments] |
#Claude Code#Opus 5.5#Unity 6#Tripo AI#SmartMesh P2#Blender#Model Context Protocol