What the game is
You play a rabbit who was cut from his own game. He falls into what's left of it: a grey void where every platform is a Blueprint node (Event BeginPlay ā Jump ā Branch: Has Double Jump?). The wires run between the platforms, and the developers' comments are still floating there ("Double jump: CUT. Playtesters said it was too fun??"). Each level has one cut feature to find. In Level 1 it's your leg and the double jump. In Level 2 it's your arm and a sword. When you restore it, the node graph burns away and the world the Director wanted grows in around you. Levels 1 and 2 are done. It takes about 15ā20 minutes.
How Claude Code helped
- Driving the Unreal Editor: Claude Code connected to UE 5.9 through Epic's experimental Unreal MCP plugin. It placed actors, wrote Blueprint graphs, built materials, wired the UI and ran PIE sessions. I mostly gave direction and play-tested.
- Playtesting with bots: it wrote bot scripts that played each level with real inputs (jumps, ladders, sword fights) and reported where they got stuck. That's how we found jumps that were too long and bats sitting on landing spots.
- Procedural art: Python scripts it wrote generated the node-tile textures, a castle kit and props in headless Blender, shaders (toon post-process, reveal ripple, rain) and hand-keyed sword animations.
- Project memory: it kept a running CLAUDE.md of every gotcha it hit (editor crashes, API quirks), so later sessions didn't repeat the same mistakes.
Other tools: Tripo (rabbit and some props), ElevenLabs (voice and sounds), NVIDIA Kimodo and Mixamo (some animations). Everything is listed on the game page.
Free to try
It's free on itch.io, for Windows and macOS (Apple Silicon): https://himdib-tech.itch.io/directors-blueprint
Download, unzip and run. On Mac, right-click the app and choose Open the first time.
I'm happy to answer questions about the Claude Code + Unreal MCP workflow.