Mythos Interactive

That's a wrap · Epic AI MegaJam 2026 · Theme: Director's Cut

The dev log

A first-person comedy platformer on a B-movie soundstage, built in Unreal Engine 5.8 in four days. One developer directs; an AI crew writes the code, builds the levels, voices the director and plays every take before I do. These are short posts from the shoot, with the screenshots, clips and the options we threw away.

  • 17takes + a boss
  • 101voiced lines
  • 100+commits
  • 1human on the crew

31 posts · last updated

Day
4
Take
31
Shoot day 4
  • Playtest
  • Code
  • Art
  • Audio
  • Cutting room floor

Version 1.1: four more playtest rounds after launch

Launching didn't stop the playtesting. Overnight I played the shipped game four more times and handed Claude a list after each run. Version 1.1 is the result, and it's now the build on itch.io.

Deaths look like a film breaking. Dying turns the picture black and white, and the grain, hairs and scratches thicken until the film slips in the gate, the sprocket holes slide in and projector light floods the screen.

Things break properly. Breakaway platforms shed grit and haze the whole time you stand on them, then go in a cloud of dust and about sixty planks, slats and splinters, all falling with gravity. Vampires split into wooden shapes too, not cubes. Shot aliens are real ragdolls now: a body and two legs joined at the hips with physics constraints, thrown along the laser and off the nearest ledge. Explosions became dense, opaque fireballs that leave black smoke hanging in the corridor, and the gun's dud shot pours black smoke for as long as it stays jammed.

One new toy. In Take 10 a backyard trampoline replaces the first swinging boom mic. It's the only way up to the camera dolly: the build script proves the dolly can't be reached from the mat without the bounce, or jumped to from the light stand next to it. The boing cost 100 ElevenLabs credits.

The small stuff. A light filmic grade (deeper blacks, warm highlights, cool shadows) that costs nothing measurable in frame time. Set chatter between takes, after a transcription check caught a creepy laugh in the first loop. The intern's whispers get louder every take. The nurse in Take 14 now bows her head into her hands instead of shaking. And a little graffiti, as if teenagers once got onto the set: I made the two tags in ChatGPT because we'd run out of Artlist credits.

Every round ends the same way: the self-playing smoke test runs all 17 takes, the game is packaged, and the packaged build is launched before anything gets uploaded.

  • Trampolines in place of both swingsThe big lap shark swims right through the second swing's spot, so a trampoline there would sit in its path. Only the first one changed.
  • A red tint on deathThe first death look. Black and white film read much better as 'the take is ruined'.
  • Chatter loop AHad a laugh buried in it that sounded unhinged on repeat. Loop B shipped.
  • Exploding into cubesVampires and platforms used to burst into boxes. Planks, slats and splinters look like a set breaking.

ToolsUnreal Engine 5.8Chaos physicsElevenLabsChatGPT imagesClaude Code

Day
3
Take
30
Shoot day 3
  • Design
  • AI workflow

It's a wrap: the game is out

Men Falling Off Things is live on itch.io and submitted to the Epic AI MegaJam. It's free for Windows: play it here, or see the jam entry.

Three days ago it was a white box and a door. Now it's 17 takes of one scene, a director and six crew members with 101 voiced lines between them, five songs, 43 achievements and a finale I'm not going to spoil here. The trailer is on the itch page, cut from clips I recorded in the game, with the director's own lines carrying it.

The last stretch was less building and more packaging: a packaged build that passes the same self-playing smoke test as the editor, a README with the controls and an honest list of who made what, the itch page with its theme and an animated poster, and social cuts of the trailer. Claude cut the trailer with a script from my clips, so changing a shot is one line and a rerun, not an editing session.

What I'd tell myself on day one: the AI didn't replace the director, it made directing the whole job. Most of my time went into taste, tone and playtesting, and into writing every decision down so the next session didn't undo it. That turned out to be the plot of the game, too.

If you play it, tell me which take got you. A proper post-mortem, with the final costs, comes after the jam.

It's not cinema, but... I suppose it'll do.
Take 2, from the trailer.
Pyro. "Lovely."
Take 5: day one graybox, and what shipped.
Day
3
Take
29
Shoot day 3
  • Design
  • Audio
  • AI workflow
  • Cutting room floor

Easy wins for the judges, and a lunch-break song

With a day left I asked Claude for an honest opinion: what's missing if we want to win? It said the game is in good shape, and that what matters now is what a judge sees in their first five minutes and whether they reach the good parts. So we did the three cheapest things on its list.

The clapperboard now chalks the attempt number under the take, so every death says "TAKE 2, ATTEMPT 2" right on the slate. The credits open with the shoot in numbers: how many retakes, how many times a man fell off a thing, how many sharks, extras and missiles got you. And Take Select is now on the main menu from the start, so a judge who runs out of time can still jump to the director's crane. Hovering it moves the menu camera down to a clapboard leaning on a chair (the first try put it on the director's chair; I moved it to the other one). Settings also gained display mode and resolution.

The menu needed its own music, not a song from the game. None of the tracks in my library felt right, so ElevenLabs made four short pieces from Claude's prompts and I picked the lounge jazz. Claude found its tempo (exactly 100 BPM) and cut it into a 24-bar loop that fades out when you press Play. For the itch.io page, the parallax poster from last night became an animated cover. It took a few tries: a feathered cream edge I didn't like, and a GIF that some viewers showed cut off, because each frame after the first stored only the part that moved.

Lounge jazzPicked
Picked: vibraphone, brushes, a muted trumpet on their lunch break.
Theremin lounge
A cheap flying-saucer movie.
Studio swing
A pompous 1950s newsreel.
Bossa hold music
The director's phone on hold.
The itch.io cover, animated.

ToolsClaude CodeElevenLabs MusicffmpegUnreal Engine 5.8

Day
3
Take
28
Shoot day 3
  • Playtest
  • Code
  • Audio

The morning list: a choppy boss, holes in the roof, and a gun from the sky

I woke up, played the new boss, and it was choppy. Claude measured it before touching anything: about 70 ms a frame on the render thread, twice Take 16's. Turning features off one at a time pointed straight at dynamic shadows. The boss set has 14 shadow-casting lights over about 1,100 moving pieces, and every one of those lights was redrawing shadows for every moving piece. Now only the three lights nearest the hero cast shadows, re-picked a few times a second. The boss went from about 70 ms to 19 ms a frame, and Take 16 got faster too. You can't see the difference.

Then a stream of small notes while I played. Missiles punch holes in the roof, and now each hole shows bright sky with a faint shaft of daylight. Red and black power cables snake across the floor before the flood, so you can guess what's coming. When the director says "Give the boy a gun", the gun and its pedestal drop out of the rigging on the word gun. The first shot is a dud that now spits sparks as well as smoke. Footsteps keep a steady beat with a left and right foot, the stairs in Take 3 lost their rails and got a gentler slope, and a breakable platform that sat in a boom mic's swing moved out of its way.

Audio got the most care. Explosions and fireworks now drop to 30% while anyone is speaking, because the director's best line in the plane scene was getting buried. I asked for three director lines again with the stress moved ("a floor that's going places", "draw the faces on", and a pause before "I'm an artist"). We can't listen together, so Claude checked each new take by measuring how loud and how long each word was, and picked the one where the right word stood out.

ToolsClaude CodeElevenLabsUnreal Engine 5.8

Day
3
Take
27
Shoot day 3
  • Playtest
  • Design
  • AI workflow

The night shift: a bigger boss while I slept

Last night I gave Claude one more playtest list and a new brief for the final fight, then went to bed and told it to make the calls until morning. The old boss was one arena and a crane, and it was too easy: you could run to the platforms and shoot every target from there.

Now it's three sets in a row. In the first, extras drop out of the rigging the moment the take starts. Shoot them all and a panel bursts out of the wall ahead, showing a glowing weak spot. Hit it, two more holes open, and when those are hit the wall blows apart. The second set is a platforming gauntlet over a pit that ends at a steel column holding up a catwalk. Shoot the column's weak spot and the catwalk tips down into a ramp over the next wall. The third is a long plank under four swinging prop axes, sharks on both sides, and then the director's crane. Each set has a checkpoint, and the game remembers what you've already broken.

When you win now, the crane spins out of control in a chain of explosions and flings him out of his chair into the shark tank, yelling his new last line. Overnight Claude also rewired how music changes (an old tape deck being stopped, a second of silence, then the next song) and fixed a stutter where each song's intro handed over to its loop.

ToolsClaude CodeElevenLabsUnreal Engine 5.8

Day
3
Take
26
Shoot day 3
  • Playtest
  • Code
  • Audio

One session, one list, and a brace in the dark

Until last night about a dozen Claude sessions were building the game in parallel, each on its own corner. That got a lot done, but it left 300 uncommitted files and changes that stepped on each other. So we wound them all down into one development session. Its first job was sorting what was real work from what was just the editor re-saving files. It checked the binary assets against the last commit, found that every one of the 283 changed assets only differed in import metadata, and threw them away with my OK.

Then I handed over my playtest list, take by take: forty-odd notes. The best bug was the oldest one. Since Take 6 something had been standing in the way of the exit door. It turned out to be the wooden back-brace of a scenery flat, which the set-building script spaced evenly along the wall. On the big stage one landed dead centre on the doorway, leaning in the dark passage behind the door. Claude wrote a check that lists every object inside each exit passage, and the brace now steps aside.

The rest of the round: breakable platforms in knotty pine, standing on posts and shaking hard when you land; moving platforms on ropes with a squeaky pulley; a shark that laps the whole pool and another that leaps between platforms; record scratches whenever the music changes; and a much bigger plane crash, followed by a new director line taking credit for it. I also recorded the intern's whispers myself. Claude cut them up and sat them 12 dB under the director, so they sound like someone just off set.

ToolsClaude CodeElevenLabs (sound effects, voice design)Blender (scripted)

Day
3
Take
25
Shoot day 3
  • Art
  • AI workflow
  • Cutting room floor

Every B-movie needs a poster

The itch.io cover doubles as the jam thumbnail, so it has to read at 630 by 500 pixels. On day one we settled on a painted 1950s B-movie poster: a square-jawed hero mid-fall off an obviously fake plywood set, a laurel bragging about the director's fifteen awards, and the tagline in the director's own words.

We generated two versions with GPT Image through Artlist and picked B for the stronger fall and the clearly fake set. Both spelled every word right on the first try, which, if you've used older image models, is its own small miracle.

The cover, B.
Version A.

ToolsArtlist (GPT Image 2.6)

Day
2
Take
24
Shoot day 2
  • AI workflow

What two days of AI tools cost

Every paid generation goes in the ledger. Here's the running total at the end of day two. The biggest single item was voicing Takes 6 to 17: 44 lines, three takes each, plus a transcription check on every one.

  • ~23,400ElevenLabs characters (voice design, 84 lines x 3 takes, crew, SFX)
  • 2,410Artlist credits (18 wall decals, a crayon sky, 6 logos)
  • 5Suno songs, plus 1 extra download credit
  • 0for 30 library sound effects
Day
2
Take
23
Shoot day 2
  • Art
  • Design

Easter eggs on every set

Every take now hides one or two movie easter eggs: props you'll recognize from films the director would never admit to watching. Behind every exit door there's now a dark passage, and a furnished hallway with office props, so the soundstage feels like part of a real building.

Day
2
Take
22
Shoot day 2
  • Art
  • Playtest

The creature shop, and a set that falls apart

The third playtest replaced the grey-box monsters with proper B-movie props: an 80s alien with too many eyes, a shark on fishing line, a wooden Dracula. From Take 10 on, the set also starts falling apart around you: flats lean, rails come loose, walls flake, and the camera shakes on every impact.

Take 16, when things have gone badly.

ToolsBlender (headless)

Day
2
Take
21
Shoot day 2
  • Audio

Five songs, an intro and a seamless loop

The music is five songs I made in Suno from prompts Claude wrote for each part of the shoot: a pompous "epic triumph" theme, a pyro mix, a creature feature, the director's vision and the finale. Each take plays an intro and then loops seamlessly. The music ducks under the director's lines so you never miss a joke, and song five carries the boss fight and the credits.

ToolsSunoSound Mix ducking

Day
2
Take
19
Shoot day 2
  • Code
  • Art

Explosions without Niagara

Unreal's Niagara effects are authored in a node editor, and our pipeline is headless scripts. So the explosions, fireworks and splashes are a small particle system written in C++: a white-hot flash, a fireball that billows and cools, sooty smoke, sparks that bounce and charred chunks, all drawn with three instanced meshes and a few flash lights.

Take 15's finale firework is 96 stars on a sphere, white-hot, turning to color and crackling out.

ToolsC++Instanced static meshes

Day
2
Take
18
Shoot day 2
  • Design
  • Art

The main menu is a lunch break

My idea: the menu is a live shot of the set while the whole crew is at lunch. Hover over Play and the camera pushes in on the director's chair; Settings glides to the film camera; Quit looks past the coffee urn to the EXIT door.

Claude filled in the details: a donut box with one bitten, a chalkboard that says "LUNCH / BACK IN 30", and a clock that ticks in real time and reads 12:47.

The idle shot: a slow crab across the empty set (recorded without the menu text).
Day
2
Take
17
Shoot day 2
  • Design
  • Code
  • Art

A biplane through the roof

My note for Take 15: the plane should crash spectacularly, and you should have to run across it. So a 15-meter biplane (also modeled in headless Blender) sputters, dives through the warehouse roof, smashes through the painted sky wall and belly-flops into the shark tank. Its upper wing becomes the only bridge to the exit.

The roof tears open with a shaft of daylight, a truss snaps, the wall breaks into board-sized chunks, and every retry resets it all.

Take 15, captured during the automated run.
The crash, four frames.

ToolsBlender (headless)C++ keyed flight path

Day
2
Take
16
Shoot day 2
  • Art
  • AI workflow

Props from a Blender nobody opened

The hero props were modeled by Python scripts running Blender headless: director's chairs with DIRECTOR printed on the canvas, Fresnel lights with barn doors on wind-up stands, a monitor cart, road cases and a clapperboard. Each part exports as its own FBX and imports into Unreal with a script.

There are also film cameras on scaffold towers around every set. They pan and tilt to follow you.

ToolsBlender (headless, bpy)FBX import scripts

Day
2
Take
15
Shoot day 2
  • Art
  • Cutting room floor

Same takes, three looks: graybox, toon, grounded

Here's the whole art journey in one place. These old builds weren't saved as screenshots at the time, so for this post Claude checked out two old commits from git, built them, and let each one play itself through all 17 takes with the camera running.

Left: the graybox from day one, grey boxes under an open sky. Middle: about ten hours later, the warehouse soundstage with the toon shader (style C) and bright cartoon water. Right: the grounded look we kept.

Toolsgit worktreeAutomated smoke test

Day
2
Take
14
Shoot day 2
  • Art
  • AI workflow

Grounded: three lighting setups, picked overnight

I went to bed and told Claude to make the call itself. Overnight it turned the toon pass off, closed the warehouse roof, lit each set with soft boxes on rigs, gave every surface real materials (plywood with seams, painted canvas, concrete, velour) and added skirting and chair rails to the flats.

It lit the corridor three ways and picked warm: tungsten soft boxes, calm and readable. In the morning I agreed.

ToolsLumenProcedural PBR

Day
2
Take
13
Shoot day 2
  • Art
  • Cutting room floor

35 more looks, and none of them was right

In the game, style C's flat shading hid the platform edges, and in a platformer that's fatal. So Claude built a little diorama that looks like a level and rendered it 35 ways: blueprint, risograph, CRT, thermal cam, stained glass, chalkboard, low-res 32-bit...

Looking at all 35 made it clear: I didn't want a filter at all. I wanted something like The Stanley Parable: believable spaces in clean, soft light. Every one of these went on the cutting room floor.

Day
2
Take
12
Shoot day 2
  • Art
  • Cutting room floor

One lamp, eleven looks

Time to pick a look. Instead of describing styles in words, Claude rendered one prop (a studio light on a stand) eleven different ways with post-process shaders: bold comic, clean toon, ink and hatch, film noir, neon, sticker cutout, crayon... I picked C, Graphic No Lines: two hard tones, a cool rim light, no outlines.

Day
1
Take
11
Shoot day 1
  • Audio
  • Code

The megaphone isn't baked in

The director shouts at you through a megaphone, but every voice file is clean. The megaphone is a chain of effects on the director's voice in Unreal: a band-pass around 400 Hz to 3.5 kHz, a little distortion, and a short slapback echo.

The first version put the echo on each voice, and some lines came back twice in a row. The fix was to send the voice to a separate echo bus instead. Because it isn't baked into the files, we could tune it by ear in seconds instead of regenerating 84 lines.

ToolsUnreal source effectsSubmix send

Day
1
Take
10
Shoot day 1
  • Playtest
  • Design

First full playtest: twelve notes

My first full play-through turned up bugs no automated test would care about. WASD didn't work until you'd pressed an arrow key. The "you fell" line played before you fell. The sharks wandered out of the water.

It also gave the game new verbs: Shift to sprint past explosions, hold right click to shake the prop gun after it fizzles ("Shake it like it owes you money"), and click to skip the death line so retries are instant. Every platforming take got at least two routes, a low risky one and a high one over the rigging.

Take 5 after the layout pass: a low route across the tables, a high one over the scaffolds.
Day
1
Take
09
Shoot day 1
  • Design
  • Cutting room floor

The director named the game

Every MegaJam entry will echo "Director's Cut", so I wanted a name that stands out. Claude pitched ten options and checked each one against existing games. Its own pick was Cut! Again! I went with a line the director says in Take 14, so players hear the title in the game: "I make films about men falling off things."

  • Men Falling Off ThingsPickedThe director's own line. Describes the game and is a joke on its own.
  • Cut! Again!Claude's recommendation: the line you hear on every death.
  • Cut to the SharkA pun, and literally the ending.
  • The Absence of FloorFrom Take 3: "the absence of floor is the absence of God".
  • Jump the SharkTaken by a jam game, a mobile game and a tabletop RPG.
  • Director's CutOn theme, and that's the problem.
Day
1
Take
08
Shoot day 1
  • Code
  • Design

Seventeen takes in an afternoon

With the take system and the voice pipeline working, the rest of the script went in fast. Reusable hazards (explosions, moving platforms, water, sharks on fishing line, aliens, vampires, missiles), four stage sets, Takes 3 to 17 and a boss fight against the director himself, all with voiced lines.

It was rough grey-box, but the whole game ran start to finish, and the smoke test said so.

Take 8: the pyro takes out the platforms, and the camera dolly is the only way across.
Take 13: missiles, with a shadow that warns you where they'll land (today's build).

ToolsC++ hazardsEditor Python

Day
1
Take
07
Shoot day 1
  • AI workflow
  • Audio

Picking takes, then handing over the pen

Choosing between three takes of 80-plus lines is real work. Claude built a small web page where I could play the takes side by side and click the keeper, and the picks fed straight into the import script.

After two lines I could hear it was getting them right, so I handed it the job: Claude picks the takes from here on, and I review them in the game. That one decision probably saved me half a day.

ToolsClaude Artifacts

Day
1
Take
06
Shoot day 1
  • Audio
  • AI workflow

The "lead" bug

One death bark, "Somebody mop up the lead", came back three times in a row with lead as in the metal. The model guesses words that have two pronunciations. The fix: the prompt sends "leed", and the subtitle keeps the real spelling. It's now a rule in the voice script for every heteronym.

| GEN_DIR_DEATH_03 | DIR | [thick British accent] [contemptuous] Somebody mop up the leed. |

subtitle: "Somebody mop up the lead."
Day
1
Take
05
Shoot day 1
  • Audio
  • AI workflow

Casting a director who doesn't exist

The director delivers every joke and all of the plot, so his voice had to be great. We used ElevenLabs voice design to make 15 brand-new voices from text descriptions, then had each one perform the same tagged line from Take 1. Five rounds of my notes: "not British enough", "a pause before FIFTEEN", "more rasp, angry from the first word", "more sarcasm, more exasperation".

The direction was a celebrity-chef tirade: arrogant, British, self-aggrandizing. We designed a new voice rather than imitating anyone real. Listen to how far it moved:

Round 1: designed voice EUnused
A fine voice, but not our man.
Round 2: voice C, acting the lineUnused
"These aren't British enough."
Round 3: voice D1Unused
"Closest. Good timing. More rasp, more accent, angry from the get-go."
Round 4: D1, take BPicked
More sarcasm and exasperation. This became the benchmark for all 84 lines.

ToolsElevenLabs Voice Design v3ElevenLabs Scribe

Day
1
Take
04
Shoot day 1
  • Code
  • Design

Every take is a Data Asset

The whole game is one scene shot 17 times. So the core system is a TakeManager: each take is a Data Asset listing which layers of the set are switched on, which abilities you have (Take 2 takes your jump away), which voice lines play and on what cue.

Take 2 is the first joke: the director adds a hole "eleven inches deep" and then turns off your jump. In the first build the hole really was 28 cm deep. After the first playtest it became an endless pit, because the director being plainly wrong is funnier.

You fell into a hole that's eleven inches deep. My nan has a hip made of shortbread, and she could clear that.

The director, T02_DIR_FIRSTFALL

ToolsUDataAssetWorld Subsystem

Day
1
Take
03
Shoot day 1
  • Code

Menus first, on purpose

The very first thing built on day one was the boring stuff: main menu, settings (volumes, mouse and stick sensitivity, invert Y, all saved) and pause. Every widget is built in C++ code, not dragged together in the UMG designer, so the AI can read and change all of it as text.

From then on the game was playable from the main menu to the last take, at every commit.

Settings over a paused take. The film-slate styling came on day two; the bones are from the first hour.

ToolsC++ UMGUSaveGame

Day
1
Take
02
Shoot day 1
  • AI workflow

How this gets made: one director, an AI crew

I'm a solo developer. For this jam I'm working as the director, and an AI coding agent (Claude, in Claude Code) is the crew. Claude writes the C++ and builds most of the content by running Unreal's editor headless with Python scripts. I play the builds, give notes and make the calls on taste.

The trick that makes this work is a loop that checks itself. Every change gets compiled, the levels get rebuilt from scripts, and an automated smoke test plays the whole game by teleporting through every take and taking screenshots. If any take can't be finished, the build fails before I ever see it.

  1. I give notesPlain words, from playing the build: "WASD doesn't work until I press the arrows."
  2. Claude writes the codeC++ for systems, with every tuning value exposed to Data Assets.
  3. Scripts build the levelsHeadless editor Python places every platform, hazard and light. Nothing hand-placed is lost on a rebuild.
  4. The game plays itselfThe smoke test runs all 17 takes and the boss, logging every voice line and taking screenshots.
  5. I play itThen the loop starts again.

ToolsClaude CodeUnreal PythonAutomated smoke test

Day
0
Take
01
Setup night
  • AI workflow
  • Code

Setup night: no game yet, just the plumbing

The Epic AI MegaJam 2026 runs four days, the theme is Director's Cut, and the only hard rule is Unreal Engine. The night before the start I didn't build any game. I set up the pipes instead: an empty Unreal Engine 5.8 C++ project, Git with LFS for the big binary files, and a running ledger of every AI credit I spend.

The idea was ready: a first-person platformer on a cheap B-movie soundstage. You're the stunt lead, and a furious, unseen British director keeps rewriting the scene, the set and the rules every time you fall off something. I'd written the design doc and the voice script before the jam, so I declared both as pre-jam work.

The scene is simple. Elegant. Our hero walks to a door. That's it. That's the film.

The director's pitch to the player (the itch.io blurb)

ToolsUnreal Engine 5.8Git LFSClaude Code

That's a wrap (for now)

The shoot is still going. New posts land here as the game comes together. The finished game goes up on itch.io after the jam.