The development journal
The Dev Blog
Day by day: what we discussed, what we decided, what the AI tools did, and what went wrong. Written from the project's chat history, pull requests and planning notes.
All times are New Zealand time (NZDT). The jam ran from 6 PM Thursday 12 November to 2:59 PM Monday 16 November.
Day 0: Before the jam
A ChatGPT conversation became a master brief, the brief became a plan, and two days of setup got every tool connected before a single asset was made.
Pre-jamChatGPTClaude (project coordinator and threads)Claude Code DesktopUnreal Engine 5.9 PreviewDay 1: Kick-off night
Six threads started at 6:03 PM. By 1 AM we had a compiled C++ framework, a greybox Segment 1, hero kits from Codex, a website scaffold and a headless Codex pipeline.
Claude (coordinator and threads)Claude Code Desktop (Remote Control on JPC)Claude in ChromeCodexDay 2: Lights on, a bigger map and twelve characters
The black screen turned out to be a map with no lights. Segment 1 grew from a 30-second straight line into winding roads, and all twelve characters reached Unreal.
Claude (coordinator and threads)Claude Code Desktop (Remote Control on JPC)Claude computer useCodex CLIDay 3: Overnight Codex, armour sets and animation (in progress)
A running entry for Saturday. Codex finished its queue overnight, two heroes have full animation sets, the pressure director is in review and the Guard's armour sets are ready for Tripo.
Claude (coordinator and threads)Codex CLIUnreal Engine 5.9 PreviewChatGPT image generation