Hi all, I want to share my first gamedev experience with AI during Epic Games Jam
Let me introduce my self. I'm a merchant sailor for 10 years. Programming was only a hobby for me: I learned some C++ and played around with Unreal Engine in my free time out of work, which is not a lot. I've thought about game development for years, but my job never let me put in steady time. Epic's AI MegaJam 2026 was my first test: can I take *any* project from zero to a finished build in such a short notice
For about a month and a half before the jam I used Claude intensively: learned MCP, different agent workflows, and how to drive other programs through their APIs.
That paid off, especially ComfyUI and fal.ai, which let me generate concepts straight from Claude Desktop.
Where AI was genuinely great?
Orchestration. I started on the Max, which I bought right before the jam bout on the second day bought Ultra... tried Claude Fable 5.2 as an orchestrator for the first time. Watching it take a pile of tasks, split them across 5 different chats/agents and keep track of what each one is doing is cool.
Concept -> asset pipeline. This was the strongest part. You give it a concept, it runs variations through several image generators, you pick what you like and say "I need these models and these textures". Since the ComfyUI workflow was already set up and the jam partners gave some extra credits, it then generated, modeled and cleaned everything up on its own. Honestly I liked this route more than making models on sites like Tripo or Meshy (which I also used, and had played with before).
The catch: this works for decor, props and tech. As soon as it's organic - mannequins, people, anything like a main character - Tripo and Meshy are the priority, and it's still a lot of manual work in Blender.
3. Bulk editor chores. Say you have 50 Blueprints that all share one component, and you suddenly need to change or remove it. You just say so, and it gets done cleanly. Or "all the lamps in this room, 30% dimmer" - lamps I never grouped or tagged. Sure, I could do that myself pretty fast, but "you said it, it's done" is a nice feeling.
4. A Design Bible is mandatory. Before the jam I prepared an empty one-page design bible template, and during the jam we filled it in and locked it. Every agent always knew the style of the game and what style each asset should be in. Agents rarely did something dumb against it. If you want a game where every asset matches in style and the textures make sense - not a pile of 3D assets thrown in from different games - write the bible first. I know this is obvious to anyone who makes games, but for me, doing my first own thing, it was a small discovery.
5. Build skills prepared before the jam.I went with Unreal 5.9 and wanted NVIDIA DLSS in it, which is a separate plugin. So before the jam, on a separate test project, the agent and I worked out how to make it all build together on 5.9, keep the build small (for example, not dragging in a ~400 MB MetaHuman plugin) and make it run on a clean Windows PC. The final ZIP was about 800 MB, which I think is reasonable. All of this was declared to the jam as pre-jam tooling.
Other skills I prepared and declared:
-a one-command project setup, a verified
-sheet of Unreal MCP calls (the built-in UE 5.9 MCP is experimental and the docs are thin)
-safe headless asset import
-a "Generation Wall" that shows every ComfyUI result live on my second screen
-a trailer assembler (OBS + ffmpeg) and a submission/packaging checker
-Plus a habit, not a skill: every AI-generated or third-party asset goes into `CREDITS.md` the moment it enters the project, with tool and model.
On the last day that saved some time.
Where it struggled? ( at least for me)
Unreal MCP and agents in Unreal are still raw. The tests it ran in PIE were sometimes surprisingly reasonable. But in my opinion it's mostly burning tokens... everything goes through scripts, and at some point it would get stuck on a script, hang for 10 minutes waiting for it to finish, then start the same script again and get stuck for another 10 minutes.
One editor, many agents. Only one or two agents can really work in Unreal at a time, so they queued up and waited for each other. We used a simple lock file (who holds the editor). A few times agents started cheating: "I unlocked the editor" or "I locked the editor until such-and-such time" when they hadn't.
Funny to watch, less funny at 4 a.m.
3. Editor Python is fragile on a fresh engine version. On UE 5.9 some Python calls (compiling Blueprints, spawning actors, loading levels) could crash the whole editor, and a call made before the editor fully finished starting up crashed it too. We learned to do risky steps headless with the editor closed, and kept a list of these traps so the next agent didn't step on the same rake.
4. "Done" doesn't mean it works. The agent reports a feature as built; that's not the same as tested. I tested in PIE myself and kept a rule that every feature is marked "PIE untested" until I've actually played it. Lots of things looked fine in the script logs and were broken in the game.
On AI in gamedev
To everyone who says AI is weak and refuses to touch it: try to make something decent with AI, and then without it. Yes, it's hard. Cloning same-looking copies of something has become way easier. Making something good, high quality, that matches "your", not someone else's - that's still very hard. But as an assistant, it lets a tiny team (or one sailor) do things.
Would I do it again?
After this I know a bit more and I'll keep going in this direction. And if someone asks whether I'd spend another 4 days with no sleep in front of the computer - I'd probably say yes.
What I made: The Last Director - a cassette-futurism TV studio from a 1970s that got holograms. You are the “Director”, the guy who cleans up AI-slop ads before they go on air: six fingers, wrong text, broken shadows, a dog that says MEOW and all the typical AI slop mistakes. And at the end you realize you’re an agent too, and your time is up, because a newer model has arrived.
Honestly, I couldn’t bring the full idea to life - time ran out and the result is pretty rough around the edges. But at least you can play it from start to finish.
Game (Windows, free): https://orestik.itch.io/the-last-director
Gameplay video: https://youtu.be/Dj3nj2VjWR0