12 Free Epic AI MegaJam Preflight Checks Before Kickoff - 2026

If you searched epic ai megajam checks before the November jam weekend, you already have a lock list before November 12 and a submission worksheet before November 15. What was missing is a numbered free preflight kit: twelve pass/fail checks before kickoff FOMO burns the weekend — join itch, pick one engine, set up tools and optional MCP without building game content early, watch the November 11 theme stream, latch AI-optional truth, and refuse dual-engine / unpackaged folklore before November 12 opens.

Epic hosts the 2026 Epic AI MegaJam. Kickoff livestream + theme reveal: November 11, 11 AM PST / 2 PM EST. Jam starts November 12. You may install Unreal Engine or UEFN and get coding agents / MCP working before kickoff — but do not start building your game before November 12; declare earlier prompts, scripts, or assets. Optional MCP setup: Unreal MCP in Unreal Editor. Packaging (for later submit) lives in Packaging Unreal Engine Projects.

This listicle owns the free kickoff preflight kit. It is not the calendar lock list. It is not the submit fill-in worksheet. It is not the AI-mandatory Stop or the planned unpackaged Stop. Those own dates, submit receipts, FAQ refusal, and packaging refusal. This URL owns pass/fail checks before you open the content clock.

Why this matters now

Thousands of itch joiners (evidence read 3,554 Joined) will still be installing UEFN at 11 PM on November 11, or worse — blockout levels on November 10 “just to warm up,” then scramble to declare pre-work. Others will thrash engine choice on day one, chase AI credits that were not claimed, or skip the theme stream and invent a theme. The board hears “jam chaos.” You skipped the kit.

Direct answer: Run checks 1–4 before November 11. Run 5–9 so tools and MCP are green without illegal early game content. Run 10–12 before anyone claims “we’re ready” in Discord. If check 6 fails (game content started before Nov 12), stop — declare or wipe, per jam FAQ. Authority: itch MegaJam page + Official Rules.

Who this list is for

Time: 25 minutes for 1–4; 2–4 hours for installs + MCP smoke + roster.
Honest limit: itch + Official Rules win if this page drifts. AI credit claim details “coming soon” on the jam page — re-check before kickoff.

Non-repetition

Four-check minimum (twenty-five minutes)

Do not “open the project and vibe” until these four are green — and do not skip 5–12 before claiming readiness.

Selection criteria

A check is in only if all are true:

1. Free — itch, Epic docs, installs, greps, calendar (no paid SaaS required for the check).
2. Primary job is safe kickoff enablement — join, pick, prep tools, refuse early content.
3. Grounded in the jam page schedule/FAQ or Epic MCP/packaging docs.
4. Honest limits in one sentence.
5. Useful before November 12 content clock.

Preflight cheat sheet (read before check 5)

Curriculum depth for dates lives on the lock list. Submit artifacts live on the submission worksheet. This kit forces you to prove kickoff readiness.

The twelve checks

1. Join + Official Rules latch

Do: Open 2026 Epic AI MegaJam. Click Join jam. Skim Official Rules (eligibility, IP, content). Confirm age 18+ and active Epic Games account for every seat you plan to fill.

Pass: Joined screenshot + “Rules skimmed Y” note.
Fail: “We’ll join on Friday night” with no account hygiene.
Honest limit: Rules languages and eligibility details can update — re-open the morning of Nov 12.

2. Engine pick latch (UE XOR UEFN)

Do: Circle Unreal Engine or UEFN once for the team. Write why (shipping skill, Fortnite island goals, Walkie-Talkie LLM NPC interest, mobile Pocket Powerhouse path). Confirm nobody is planning dual entries.

Pass: One path written in Discord pin.
Fail: “We’ll decide after theme” with both editors installing “just in case” as a dual-submit plan.
Honest limit: Installing both tools for learning is fine; entering both is not.

3. Content-clock latch (tools vs game)

Do: Write two lists: (A) allowed before Nov 12 — install UE/UEFN, agents, MCP, Fab license research, empty project templates if not game content, credit claim when available; (B) forbidden — levels, gameplay systems, art for the jam game, undeclared early prompts/scripts/assets. Jam FAQ: set up tools before Nov 12; don’t start building the game; declare earlier work.

Pass: A/B lists pinned; team agrees.
Fail: Blockout map dated Nov 10 with no declare plan.
Honest limit: If you already made something early, declare it — do not hide it.

4. AI-optional latch

Do: Paste the refusal from Stop Treating Epic AI MegaJam as AI-Mandatory: AI tools are allowed, not required. Decide whether your team will use agents/MCP, asset gen, or neither. Do not invent “judges DQ non-AI” folklore.

Pass: Written AI plan: NONE / LIGHT / HEAVY with owner.
Fail: Panic install of five agents with no scope.
Honest limit: Credits “coming soon” on the jam page — check back; do not block kickoff forever waiting.

5. Theme-stream plan (November 11)

Do: Calendar the kickoff livestream Nov 11, 11 AM PST / 2 PM EST (Twitch/YouTube/X per jam page). Assign a watcher + VOD owner if timezone fails. Plan a 30-minute post-stream scope meeting.

Pass: Calendar invite + watcher name.
Fail: “We’ll guess the theme from Discord rumors.”
Honest limit: VOD lag is OK; starting content before Nov 12 still is not.

6. Early-content refuse smoke

Do: Grep the team drive / repo for jam-game levels, Blueprints, Verse, or art dated before Nov 12. If found: declare on the jam form plan or quarantine. Confirm no “warm-up game” that is secretly the entry.

Pass: NONE found or DECLARE list written.
Fail: Hidden prebuild.
Honest limit: Tooling repos and MCP configs are not game content — levels and mechanics are.

7. Tool install smoke (chosen engine)

Do: Install and launch the chosen editor. Create a throwaway empty project/island only if it does not become jam game content. Confirm Epic login works. Skim Unreal Engine guide hub if the install path is unfamiliar.

Pass: Editor opens; login OK; throwaway labeled NON-JAM or skipped.
Fail: First launch planned for Nov 12 noon.
Honest limit: Long shader compiles belong before kickoff, not during theme hour.

8. MCP / agent smoke (optional but if planned)

Do: If using agents: follow Unreal MCP docs (and UEFN MCP docs linked from the jam page). Run a non-game hello smoke. Keep MCP on safe local gates — see Stop exposing Unreal MCP beyond loopback. Pair with the safe Cursor session worksheet if needed.

Pass: MCP hello PASS or AI plan = NONE (NA).
Fail: “We’ll wire MCP on day one after theme” with HEAVY AI plan.
Honest limit: Jam tip — getting MCP working on day one costs build time. Prep now.

9. Roster + roles latch

Do: Lock ≤5 humans. Assign: build lead, submit owner (see submission worksheet), art/audio if any, notes owner for Glass Box. Collect Epic-linked emails early (submit needs them).

Pass: Roster table with roles + emails.
Fail: “Open Discord LFG forever.”
Honest limit: Agents do not count as humans — but they also do not sign the itch form.

10. Submit-path awareness (not full submit yet)

Do: Read What to submit on the jam page once. UE teams: know packaging + zip naming + 1 GB/butler. UEFN teams: know private version code (not live/playtest). Know video 30–60s. Schedule a day-two package dry-run on the calendar (not the final submit).

Pass: Submit-path one-pager + dry-run calendar block.
Fail: “We’ll figure submit Sunday.”
Honest limit: This check does not replace the submission worksheet — it forces awareness before kickoff.

11. Scope + polish doctrine

Do: Write a one-page scope: vertical slice definition, must-have fun moment, explicit cuts. Jam tip: scope small, then polish; finished fun beats ambitious broken. Agree “no new systems after Friday noon” or similar freeze.

Pass: Scope page pinned.
Fail: Feature laundry list with no cuts.
Honest limit: Theme may force rescope on Nov 11 — leave 20% slack.

12. Kickoff refuse latch (PREFLIGHT_OK)

Do: Before Discord “we’re so ready”: confirm checks 1–4 and 6–7 green; 5 calendar set; 8 NA or PASS; 9–11 written. Confirm not dual-engine, not early undeclared content, not AI-mandatory panic. Confirm Nov 15 cliff known (submit worksheet queued for later).

Pass: PREFLIGHT_OK signed by build lead.
Fail: Vibes-only readiness.
Honest limit: PREFLIGHT_OK ≠ SUBMIT_OK. Different evenings, different receipts.

Scorecard (print / paste)

MEGAJAM_KICKOFF_CHECKS_v1
team: ________
date: ________
engine: UE / UEFN
1 join_rules: PASS/FAIL
2 engine_pick: PASS/FAIL
3 content_clock: PASS/FAIL
4 ai_optional: PASS/FAIL
5 theme_stream_plan: PASS/FAIL
6 early_content_refuse: PASS/FAIL
7 editor_install: PASS/FAIL
8 mcp_agent: PASS/FAIL / NA
9 roster_roles: PASS/FAIL
10 submit_awareness: PASS/FAIL
11 scope_doctrine: PASS/FAIL
12 kickoff_refuse: PASS/FAIL
owner_sign: ________
PREFLIGHT_OK_y_n: ________

Beginner path — twenty-five minutes then stop

1. Checks 1–4 only.
2. Join itch; circle engine; write A/B content clock; latch AI optional.
3. Paste the four-check table into Discord.
4. Schedule 5–12 for the next evening.
5. Link the lock list for dates.
6. Do not open a jam level yet.

Common beginner mistakes: building a “practice level” that is the entry; skipping Join; installing both engines as dual submit; waiting until Nov 12 to download UE; believing AI is mandatory.

Developer path — tooling without illegal content

1. Install chosen editor; compile shaders; verify source control empty of jam game.
2. Wire MCP on loopback-only; document agent versions.
3. Practice a non-jam package once so day-two dry-run is not first contact with packaging (packaging docs).
4. Template a submit runbook pointing at the submission worksheet.
5. Pre-license Fab assets you might use; list attribution owners.
6. Set repo branch policy: no jam-game merges before Nov 12 00:00 EST (or your agreed clock).
7. Prepare capture stack for the 30–60s video (OBS preset).
8. Re-check jam page for AI credit claim instructions the night before Nov 12.

Creator Monday checklist

• [ ] Twelve-check card pasted once.
• [ ] Four-check minimum green before theme FOMO.
• [ ] Theme stream calendared.
• [ ] Engine XOR public.
• [ ] Early-content refuse explicit.
• [ ] AI plan NONE/LIGHT/HEAVY.
• [ ] Submit owner named (future worksheet).
• [ ] Scope page with cuts.
• [ ] PREFLIGHT_OK signed.
• [ ] Lock list + AI Stop linked for arguers.
• [ ] Discord paste via 25 Discords communities stays plain-language.

Failure modes

Company diligence four-liner

1. Scope — MegaJam kickoff preflight before Nov 12: joined, one engine, tools without early game content, AI-optional plan, theme watch.
2. Cost — one tooling evening vs day-one install + MCP chaos.
3. Evidence — scorecard 1–12 or signed fail.
4. Owner — build lead who refuses PREFLIGHT_OK on undeclared early builds.

Pasteable diligence line:

Team completed MegaJam kickoff preflight: itch joined, single engine path, tool/MCP prep without jam game content before Nov 12, AI-optional plan, theme-stream owner assigned, PREFLIGHT_OK signed.

Worked example — UE trio before kickoff

1. Join itch; rules skimmed.
2. UE circled (shipping skill).
3. A-list: install, MCP hello, Fab browse; B-list: no maps/gameplay before Nov 12.
4. AI plan LIGHT — one coding agent.
5. Pat watches Nov 11 stream; Sam owns VOD.
6. Repo empty of jam content.
7. UE 5.x launches; throwaway NON-JAM project only.
8. MCP hello PASS on loopback.
9. Three emails + roles; submit owner = Sam.
10. Day-two package dry-run on calendar; submit worksheet bookmarked.
11. Scope: one verb, one enemy, one exit — cuts listed.
12. PREFLIGHT_OK signed Nov 10.

Worked example — UEFN solo

1–4: Joined; UEFN; content clock; AI LIGHT for Walkie-Talkie interest (not mandatory).
5: Stream calendar.
6–7: No early island gameplay; UEFN launches.
8: UEFN MCP docs skim + hello or NA if delaying agents.
9: Solo roster.
10: Private version code concept understood; submit worksheet queued.
11: Scope one conversation loop + one traversal toy.
12: PREFLIGHT_OK.

Timeline map (where this kit sits)

Do not collapse these evenings into one Discord message. Teams that treat “we locked the dates” as “we passed preflight” still lose Monday to installs. Teams that treat “we preflighted” as “we submitted” still DQ on Sunday.

Tooling vs content — worked boundary examples

When unsure, ask: “Would a judge recognize this as part of the jam game?” If yes, wait for Nov 12 or declare.

Opinion spine — what “checks” mean before kickoff

Quotable takeaway: Twelve free MegaJam preflight checks before kickoff. Tools and MCP are allowed early. Game content is not. PREFLIGHT_OK is not SUBMIT_OK.

Key takeaways

1. Kickoff stream Nov 11; build opens Nov 12; submit cliff Nov 15 5:59 PM PST.
2. Join itch + skim Official Rules first.
3. One engine: UE or UEFN.
4. Tools/agents/MCP OK before Nov 12; game content is not.
5. Declare any earlier prompts/scripts/assets.
6. AI is optional — latch a plan, don’t panic.
7. Assign theme-stream watcher.
8. Install editor before day one.
9. If using MCP, hello-smoke on safe local gates.
10. Name submit owner early; use submission worksheet later.
11. Scope small with explicit cuts.
12. PREFLIGHT_OK ≠ SUBMIT_OK.
13. Lock list and Stop siblings own dates and AI folklore.
14. Quotable: prep tools early; don’t prebuild the game.
15. Scorecard MEGAJAM_KICKOFF_CHECKS_v1 is the cite-worthy paste.

FAQ

Can I set up Unreal MCP before November 12?

Yes. The jam page encourages getting agents and MCP working before kickoff. Do not start building the game early.

Can I blockout a level before November 12?

No as jam game content. Declare anything you made earlier. Prefer waiting for the content clock.

Do I have to use AI?

No. See the AI-mandatory Stop.

Is the lock list the same as these checks?

No. The lock list owns calendar/engine cliffs. This kit is a pass/fail preflight scorecard before kickoff.

When do I use the submission worksheet?

During the jam / submit evening — packaged zip or private version, video, form, SUBMIT_OK. Not as a substitute for kickoff preflight.

What if I miss the November 11 stream?

Use the VOD; still do not start game content before Nov 12.

Can my team enter UE and UEFN?

No. Pick one.

Where is packaging documented?

Packaging Unreal Engine Projects — practice before Sunday, not as first contact.

What does PREFLIGHT_OK mean?

Kickoff readiness signed — not a finished submit.

How many people can be on a team?

Up to five humans; agents unlimited.

Sources

• 2026 Epic AI MegaJam (itch.io)
• Unreal MCP in Unreal Editor
• Packaging Unreal Engine Projects
• Epic Developer Community MegaJam topic