Epic AI MegaJam Lock List Before November 12 - 2026
If you searched epic ai megajam after the October 22 announcement, you do not need another “vibe to $50k” headline paste. You need a lock list before November 12.
Epic’s 2026 AI MegaJam runs a November 12–15 build window with submission due November 15, 5:59 PM PST / 8:59 PM EST. Teams are solo or up to five humans, with as many AI agents as you want. Build a playable game in Unreal Engine or UEFN (one engine path for the entry). Prize framing on the jam page includes cash prizes (itch lists $65,000 in cash prizes) plus Development Continuation Grants of up to $50,000 per team and sponsor prizes. Join and rules live on the itch.io jam page. Community mirror: Epic Developer Community topic. Official news URL: unrealengine.com/news/2026-epic-ai-megajam (re-check if your network blocks it).
Early press sometimes framed the jam as AI-mandatory; Epic’s jam materials and FAQ framing treat AI tools as optional — you may use any AI tools, including connecting agents via Unreal MCP, but you are not required to “AI-wash” a game that does not need it. Lock that truth before Discord argues you into a bad architecture.
This URL owns the deadline lock list: dates, engine pick, submit artifacts, UEFN private version code, and what not to promise. It is not a tutorial for Unreal MCP, not a Fortnite creative course, and not a prize-odds calculator.
Why this matters now
Thousands of itch joiners (the jam page showed 2,000+ joined when rechecked) will open empty projects on November 12 without a submit plan. The failure mode is classic: theme day excitement, engine thrash, missing private version code, upload at 5:58 PM PST.
Direct answer: Before November 12, lock engine (UE vs UEFN), team size ≤5, submit checklist owner, kickoff watch plan (November 11), and a no-scope-creep one-pager. Treat November 15 5:59 PM PST as a hard cliff — not a soft “sometime Sunday.”
Who this lock list is for
| Audience | Use it to… |
|---|---|
| Beginners | Know dates, engine choice, and AI-optional truth |
| Developers | Build a submit receipt before theme day |
| Creators | Paste a team Discord pin with cliffs |
| Companies | Diligence — jam entry ≠ product launch promise |
Time: 35–50 minutes to lock; longer if you install UEFN/UE fresh.
Honest limit: itch + Epic forum/news are authorities. Prize tables and eligibility can update — re-read the jam page the morning of November 12.
Non-repetition
| URL | Job |
|---|---|
| itch — 2026 Epic AI MegaJam | Dates, join, submit rules |
| Epic Dev Community announcement thread | Kickoff / prize framing mirror |
| Unreal Engine news post | Official announcement |
| Unreal MCP safe Cursor session worksheet | MCP lab — not the jam lock |
| Stop exposing Unreal MCP beyond loopback | Security refusal |
| Epic Games Launcher preview checks | Launcher hygiene cousin |
| Help hub | Error fixes |
| Discord resources | Team find (carefully) |
| This URL | Lock list before November 12 |
The one-paragraph version
Epic AI MegaJam 2026 is a four-day Unreal Engine or UEFN jam (November 12–15) with a November 15, 5:59 PM PST submit cliff, optional AI tooling, teams up to five, and cash plus continuation-grant prize framing. Indies should lock engine, team roster, kickoff attendance, and submit artifacts (including UEFN private version code when applicable) before theme reveal — not after the first all-nighter.
Date table (print this)
| Event | When (as listed on jam / forum) | Owner |
|---|---|---|
| In-person SF registration opens | Nov 1, 7 AM PST / 10 AM EST (Eventbrite; space limited) | Logistics |
| Kickoff + theme reveal livestream | Nov 11, 7:00 PM (Unreal channels per forum) | Whole team watch or VOD owner |
| Build window | Nov 12–15, 2026 | Build lead |
| Submit deadline | Nov 15, 5:59 PM PST / 8:59 PM EST | Submit owner |
| In-person SF jam days | Nov 14–15 (Digital Jungle framing) | Travel lead |
| Winners announced | By January 29, 2027 (itch framing) | Expectation setting |
Convert the submit cliff to your local TZ now. Put two calendar alarms: T−3 hours and T−30 minutes.
AI optional — kill the myth early
| Myth | Lock |
|---|---|
| “You must use AI or you are disqualified” | Jam materials allow any AI tools; they do not require AI cosplay |
| “More agents = higher score” | Playable craft and rules compliance beat agent spam |
| “MCP is mandatory” | Optional connector for editor agents — lab safely first |
| “We can skip Unreal and ship Godot” | Engine path is Unreal Engine or UEFN |
If early headlines said “must use AI,” treat that as a walkback risk and re-read the jam page. Your architecture should survive an AI-optional judging reality.
Engine lock — UE vs UEFN (pick one)
| Path | Pick if… | Lock before Nov 12 |
|---|---|---|
| Unreal Engine | You want a packaged game upload path you already know | Install version pinned; packaging smoke on a blank project |
| UEFN | You want Fortnite editor workflow / island-style delivery | Private version code process understood; submit artifact list owned |
Hard rule: One engine per team entry. Do not “maybe both” into Thursday.
UEFN private version code (do not discover at 5:50 PM)
itch framing: submit your game (Unreal Engine) or private version code (UEFN) before the deadline, plus gameplay video and listed details. Assign a human who has successfully created/shared a private version code before November 12 on a throwaway project.
Team lock (≤5 humans)
| Role | Name | Backup |
|---|---|---|
| Build lead | ||
| Submit owner | ||
| Capture / trailer | ||
| Design / scope guardian | ||
| Optional fifth |
No sixth “advisor who might help.” Five is the ceiling.
Beginner path — this weekend before Nov 12
- Join the itch jam.
- Read Rules + What to submit end to end.
- Pick UE or UEFN in writing in Discord.
- Install and open a blank project; record version string.
- If UEFN: practice private version code once.
- If using agents/MCP: lab on loopback only — see MCP Stop.
- Write a one-page scope: verb + player fantasy + lose condition + 3 vertical-slice musts.
- Set submit alarms.
Developer lock checklist (M1–M12)
| ID | Lock | Pass if… |
|---|---|---|
| M1 | Join confirmed | itch membership visible |
| M2 | Engine chosen | UE or UEFN written |
| M3 | Version pinned | Exact editor build noted |
| M4 | Team ≤5 | Roster frozen |
| M5 | Submit owner named | One human owns upload |
| M6 | Artifact list | Game/code + video + required fields drafted |
| M7 | UEFN code drill | Private version code practiced |
| M8 | Kickoff plan | Nov 11 watch or VOD assignee |
| M9 | Scope one-pager | Cuts listed before theme |
| M10 | AI policy | Optional tools listed; no mandatory agent stack |
| M11 | Security | MCP not exposed beyond loopback |
| M12 | Local TZ cliff | 5:59 PM PST converted + dual alarms |
Scope one-pager (template)
Player verb:
Fantasy in one sentence:
Lose / win condition: ___
Must ship (3): 1) 2) 3)
Nice-to-have (ban until musts done):
Engine: UE / UEFN
AI tools we might use: (or none)
Submit owner:
Hard stop for features: Nov 15, 12:00 PM PST (example — set yours hours before cliff)
Theme reveal will tempt you to rewrite the fantasy. Keep the must-ship count at three.
Prize framing — hope without delusion
itch lists cash prizes and continuation grants up to $50k per team plus sponsor prizes. Forum copy mirrors “vibe your way to $50k.” For companies and leads:
| Do | Don’t |
|---|---|
| Treat grants as upside | Book $50k into the Q4 forecast |
| Read eligibility fine print on jam day | Assume every prototype qualifies |
| Plan a post-jam archive either way | Leave the only build on one laptop |
In-person SF vs online
| Mode | Lock |
|---|---|
| Online only | Bandwidth, capture mic, sleep shifts |
| SF in-person (Nov 14–15) | Eventbrite from Nov 1; travel buffer; still hit online submit cliff |
| Hybrid | Who submits if venue Wi-Fi dies? |
Space is limited for in-person — decide by early November, not November 13.
Creator Discord pin
Epic AI MegaJam: build Nov 12–15, submit Nov 15 5:59 PM PST. Engine: UE or UEFN (we picked ). AI optional. Team ≤5. Submit owner: . UEFN private version code drill: DONE/TODO. Kickoff watch Nov 11. Scope one-pager in #jam-docs. No sixth teammate, no second engine.
Monday–Friday schedule (pre-jam week)
Assume today is late October; adjust.
| Day | Outcome |
|---|---|
| Mon | M1–M4 locked |
| Tue | M7 UEFN drill or UE package smoke |
| Wed | M6 artifact template + capture test |
| Thu | M8 kickoff calendar + M9 scope |
| Fri | Full M1–M12 review; freeze roster |
Company diligence
| Question | Answer shape |
|---|---|
| Are employees entering? | Yes/No; on own time vs sponsored |
| IP assignment | Jam rules + employment agreement reviewed |
| AI tool licenses | Approved list if company-sponsored |
| Prize tax / grant handling | Finance owns if you win — do not improvise |
Theme-night protocol (November 11–12)
Kickoff reveals the theme. Most teams lose the first six hours rewriting fantasy documents. Use this script instead:
- Watch together (or assign one notetaker for the VOD).
- 15-minute silent notes — each person writes one verb that fits the theme and the pre-locked must-ship list.
- 20-minute vote — pick the verb that fits M9 musts; kill the clever idea that needs new systems.
- Freeze fantasy sentence — write it in Discord; only the scope guardian can edit it.
- Sleep rule — at least one human sleeps before the first full build day if you are not already in crisis.
If the theme fights your pre-scoped fantasy, cut features — do not change engines.
Day-of submit runbook (November 15)
Assign clock times in Pacific first, then paste local conversions.
| Pacific time | Action |
|---|---|
| 12:00 PM | Feature freeze — only crash fixes |
| 2:00 PM | Package / private version code attempt #1 |
| 3:00 PM | Gameplay video capture (1080p, 60–90 seconds, show the verb) |
| 4:00 PM | Upload attempt #1 to itch + fill required fields |
| 4:45 PM | Second human verifies the public/jam submission view |
| 5:00 PM | Buffer for retries — no new content |
| 5:59 PM | Cliff — if upload fails, you needed the 4:00 attempt |
UEFN teams: private version code generation belongs in the 2:00 PM block, not the 5:30 PM block. If code creation is slow, start at 1:00 PM.
Packaging and capture smoke (do before November 12)
| Smoke | Unreal Engine | UEFN |
|---|---|---|
| Blank project opens | Required | Required |
| Cook/package or equivalent you will use | One successful smoke zip/folder | N/A — follow UEFN publish path |
| Private version code | N/A | Create + open as second account/machine if possible |
| 30-second capture of a moving pawn | Required | Required |
| Upload bandwidth test to itch | Required | Required |
Record the smoke results in the same doc as M1–M12. “We will figure packaging out during the jam” is how Sunday dies.
Agent / MCP hygiene during the jam
If you use editor agents:
- Keep Unreal MCP on loopback only (Stop exposing MCP).
- One human owns the agent session — no four people pasting conflicting prompts into the same level.
- Log which assets were agent-touched if prize/eligibility asks for disclosure later.
- Have a manual fallback for the must-ship trio so an API outage does not erase the weekend.
Agents are optional accelerators. They are not a substitute for a submit owner.
After submit — archive in one hour
Whether you feel proud or wrecked:
- Zip the project + video + submission screenshots.
- Export a text file of itch field answers.
- Tag git (even a zip hash if you were not using git well).
- Write five bullets: what worked, what burned hours, what you would pre-lock next jam.
- Take a calendar break — do not immediately announce a commercial reboot of the jam prototype without IP/employment clearances.
Failure modes
| Failure | Symptom | Fix |
|---|---|---|
| Engine thrash | UE Wednesday, UEFN Thursday | M2 freeze |
| Code at 5:58 | UEFN private version unknown | M7 before jam |
| AI mandatory myth | Forced agent stack | M10 |
| Six humans | “Just one more designer” | M4 |
| No video | Submit incomplete | Capture owner + rehearsal |
| MCP on public IP | Security incident | MCP Stop |
| Theme rewrite spiral | Must-ship list becomes twelve | Scope guardian |
Solo entrant variant
If you are one human:
| Still lock | How |
|---|---|
| Engine | Same M2 — pick before Nov 12 |
| Submit owner | You — still write the runbook times |
| Scope | Cut must-ship to two items, not three |
| Sleep | Pre-schedule a four-hour block; agents do not replace rest |
| Video | Record a rehearsal capture on Nov 14 even if art is ugly |
Solo teams die on packaging and video more often than on design. Your pre-jam smokes matter more, not less.
If you already know you tire after midnight, schedule the November 15 package attempt even earlier — move the runbook’s 2:00 PM Pacific block to noon. The cliff does not care that you are solo.
Communication with sponsors / friends who “might join”
Freeze roster November 10. After that, late joiners become playtesters or Discord cheerleaders — not eleventh-hour owners of systems you did not scope. “Maybe my friend who knows Niagara” is how M4 fails. Put the freeze date in the Discord pin so nobody negotiates it in the group chat at midnight. Cheerleaders are welcome; late system owners are not. Hold the line.
Opinion spine (quotable)
Stop opening a MegaJam project without a submit owner and a local-time cliff.
Stop thrashing between Unreal Engine and UEFN after November 12.
Stop treating “AI jam” as “AI mandatory.”
Do lock engine, roster, private version code drill, and dual alarms before kickoff.
Relationship to other Epic / Unreal posts
| Need | URL |
|---|---|
| Safe Unreal MCP lab | MCP worksheet |
| MCP exposure refusal | Stop exposing MCP |
| Launcher preview hygiene | 12 free checks |
| MegaJam date/submit lock | This URL |
Key takeaways
- MegaJam build window: November 12–15, 2026.
- Submit cliff: November 15, 5:59 PM PST / 8:59 PM EST.
- Engine: Unreal Engine or UEFN — pick one.
- Team: solo or up to five humans; AI agents allowed.
- AI is optional — tools welcome, not a costume requirement.
- UEFN path needs a practiced private version code.
- Kickoff/theme: November 11 livestream plan.
- Prizes include cash pool framing and continuation grants up to $50k — upside, not a budget line.
- In-person SF registration opens November 1 — limited space.
- Name a submit owner before theme day.
- Lab MCP on loopback only if you use agents.
- This page is a lock list, not a jam strategy guide for winning.
FAQ
When is Epic AI MegaJam 2026?
Build November 12–15, 2026, with submit by November 15, 5:59 PM PST. Confirm on the itch jam page.
Do I have to use AI?
Jam materials allow any AI tools; they do not require you to force AI into a project that does not need it. Re-read rules on jam morning.
Unreal Engine or UEFN?
Either path is listed — lock one before November 12.
What is the private version code?
A UEFN submit artifact called out on the jam page. Practice generating/sharing it before the deadline week.
How big can the team be?
Solo or up to five people (itch framing).
What are the prizes?
itch lists cash prizes (including a $65,000 cash prizes line) plus Development Continuation Grants of up to $50,000 per team and sponsor prizes. Verify live tables before citing exact category amounts.
Is there an in-person option?
Forum/jam framing includes Digital Jungle in San Francisco November 14–15, with registration opening November 1. Space limited.
Where do I join?
itch.io/jam/2026-epic-ai-megajam.
Can we use Godot or Unity?
Not for this jam’s engine rule — Unreal Engine or UEFN.
Is this a guarantee we win a grant?
No. It is a deadline lock list so you can submit a valid playable entry on time.