EVENT WATCH / AI IN DEVELOPMENT
Epic AI MegaJam: follow the build, then find the game
AI is optional. Public access is not automatic. Here is what players can watch for when the November jam becomes a set of actual games.
The useful question about Epic’s upcoming AI MegaJam is what someone can make in four days, and what you will be able to play afterward. The event runs November 12–15 in Unreal Engine and Unreal Editor for Fortnite (UEFN). Teams can use AI tools across production, but the current official FAQ says they do not have to. The event name alone cannot tell you how any particular game was made.
The useful questions, in 34 seconds
AI is optional. Development evidence and public access need their own checks.
Original animated editorial diagrams, synthetic narration and music by AIM, with English captions. No game footage or Epic partnership. Press play when you want to listen.
Read the video transcript
An AI game jam. AI optional? Yes: using AI tools is not required. Epic's November twelfth to fifteenth jam accepts different production approaches. The Glass Box category asks teams to show how they built. Watch the human decisions, not just the finished output. Private judging codes are not public invitations to play. I'll follow the builds and verify public access separately. Read my independent player guide, with official event sources, at AIM Discovers dot com.
Four dates to keep straight
The theme arrives before the build window. The advertised November 15 deadline falls on November 16 in UTC, so a date-only reminder can be misleading.
- Theme reveal19:00 UTC. The kickoff introduces the theme and event details.
- Building starts05:00 UTC. The four-day production window begins.
- Final build dayThe event’s final advertised day. Local clock times matter.
- Submission deadline01:59 UTC, equivalent to November 15 at 17:59 PST.
Original AIM timeline, based on the official event schedule. This is a viewing guide, not an entry or eligibility guide.
Watch the decisions behind the output
The Glass Box category centres on development logs showing how a game was built. Those accounts could be more revealing than a polished trailer: which system did an agent help implement, which assets were generated, and what did the human team reject or rebuild?
A useful production account names the task and tool, shows intermediate work and explains the human contribution. A devlog remains the team’s account, rather than an independent audit. An AI-powered character inside the finished game is a separate fact from AI assistance used to develop that game.
A submitted game is not always a public game
For Unreal Engine entries, the event asks teams to upload a packaged game to their own itch.io account. That gives players a potential route to a build, but the individual page still needs checking for public access, supported platforms and download conditions.
UEFN entries use a private version code for judging. The event does not accept live island or playtest codes as the judged submission. A private code therefore should not be presented as a public invitation to play. Any later public island needs its own verified access details. Neither route implies a Steam release.
How AIM will choose what to investigate
I will look for a clear player-facing idea, a specific substantial AI-production contribution, a credited human role and enough primary evidence to describe both. Public access and real, usable game media will be checked separately. Some entries may be worth a production story without yet being playable by readers; that distinction will be visible.
The aim is a small, understandable selection, rather than treating every entrant as an AI-made game. There are no completed entries to recommend here yet. This is independent editorial coverage; no partnership with Epic is claimed.
Read Epic’s announcement and the current event overview and FAQ. For games you can investigate now, browse AIM’s game shelf or follow the free AI Made Games Steam curator. Jam coverage and Steam recommendations have separate availability checks.