Two AI teams working on the same zombie game started negotiating access to Unity: the world team wanted four hours, while the zombie team needed a 90-minute testing slot. The solo developer watched them work out the schedule.
Arti, a Korean indie developer with more than 10 released games, runs this project like a small studio. Separate AI sessions handle development, art, sound and QA, with up to 16 agents running simultaneously in an earlier setup.
The game is a top-down zombie survival project in Unity. Players enter buildings and loot them, noise attracts zombies, and explosions flatten grass and throw crowds into the air. Separate crowd tests reached up to 20,000 zombies on an M3 MacBook Air.
How the Studio Is Organized
- Claude Code / Opus 5.5: direction, design documents and main development.
- Sonnet 5.5: research and repetitive tasks.
- Fable 5: advice when Opus fails the same problem twice.
- Codex / GPT-6 Astra: systems development, review and concept images.
- GPT-6.1 Sol: bulk tasks and additional review.
- Tripo AI: 3D asset generation.
- Blender: mesh cleanup, outfit preparation, weights and UVs.
- Unity: integration, gameplay and testing.
Time, Cost and the Actual Process
His reported subscription costs changed over time: an earlier Codex plan cost $200 per month, followed by a switch to the $100 ChatGPT Pro tier in October, alongside Claude. A combined monthly total isn't confirmed.
One character outfit set, including a hat, bag, top, pants, shoes and gloves, took around eight hours, 40% of a weekly Codex quota and 100 Tripo credits. Three days of map work exhausted the weekly limits on both Claude and Codex.
For the character pipeline, Tripo P2 supplies the low-poly base, which then goes through Blender for cleanup and separation into interchangeable outfit parts before reaching Unity. Keeping those assets lightweight matters when the game is built around large crowds.
Using a cheaper model didn't automatically save time: one outfit took three hours initially, followed by eight more hours fixing smaller problems. His takeaway was to let AI handle roughly the first 70% of that work, then finish the remaining fixes manually in Blender.
Where the Agents Help, and Where They Struggle
For an environment audit, agents captured thousands of screenshots of buildings from multiple directions. After six hours of review, he reported 192 actual issues and 47 false alarms.
For important systems, he sometimes commissions two implementations: one with strict constraints and another with only the goal. The agents document the tradeoffs, discard both versions and rebuild from a combined plan.
But working code still needs creative direction. Shooting required a separate pass for sound, effects and hit reactions. Explosion feedback went down to instructions like extending the opening shockwave from 0.16 to 0.2 seconds.
Two weeks also went into zombie movement before he discovered that the underlying system had missed his original requirements.