Stop Submitting Unpackaged Unreal Projects to Epic AI MegaJam - 2026

If you searched epic ai megajam unpackaged in the week before submit, you do not need another “package tips” thread buried under hype. You need a refusal.

Stop submitting unpackaged Unreal projects to Epic AI MegaJam. The 2026 Epic AI MegaJam page says it plainly in the don’ts: don’t submit unpackaged Unreal Engine projects; don’t enter with both Unreal Engine and UEFN; late submissions will be disqualified. Unreal Engine teams must package a playable Windows development build, zip as TeamName_GameName, keep under 1 GB or use butler / Blendo Itch Uploader, upload to their itch account, then submit to the jam. UEFN teams submit a private version code — not a live island or playtest code. Official packaging guidance: Packaging Unreal Engine Projects.

This is not the calendar lock — use Epic AI MegaJam Lock List Before November 12. It is not the fill-in submit lab — use Submission Worksheet Before November 15. It is not the kickoff preflight scorecard — use 12 Free Preflight Checks Before Kickoff. It is not the AI-mandatory Stop. This URL owns the unpackaged-folder / dual-engine / late-folder folklore refusal.

Why this matters now

Jam week produces a predictable failure: the game “runs in editor,” someone zips the .uproject tree at 5:50 PM PST, itch accepts the file, judges cannot play it, and the team argues “we submitted.” Or a team hedges with UE and UEFN “for prize coverage.” Or the upload starts after November 15, 5:59 PM PST / 8:59 PM EST and late DQ hits. With thousands joined (evidence read 3,554), that folklore scales.

Direct answer: For Unreal Engine entries, only a packaged playable build counts. For UEFN, only a private version code minted before the cliff. Never dual-enter. Never treat “upload started” as on-time if the cliff passed. Pair this refusal with the submission worksheet for the fill-in receipt.

Who this refusal is for

Time: 20 minutes to read. First package dry-run: 1–3 hours depending on project size.
Honest limit: itch jam page + Official Rules are authorities. Packaging cook times vary — schedule buffer; do not invent “Epic will unzip our source” mercy.

Non-repetition

The claim I am refusing

Claim (false): “If it opens in the Unreal Editor on my machine, zipping the project folder is a valid MegaJam submission. Dual UE + UEFN entries maximize prize odds. Starting the itch upload at 5:58 PM PST counts if the browser spinner is spinning. Judges will figure it out.”

Counter-claim: The jam forbids unpackaged Unreal Engine projects, forbids dual engine entries, and disqualifies late submissions. A folder is a development workspace, not a playable packaged build. A live UEFN island code is mutable after the jam — private version codes exist for that reason. That folklore is UNPACKAGED_AS_SUBMIT (and its cousins DUAL_ENGINE_HEDGE and LATE_SPINNER_OK).

Same disease family as other Stops: AI-mandatory theater, funnel-as-journey, Meshy-7-forever. This one is editor comfort stuffed into a judge-facing artifact.

What Epic’s jam page actually says (read before you argue)

From 2026 Epic AI MegaJam:

If your standup is “source zip is fine because we use AI agents,” you skipped the product’s own submit rules — and the AI-mandatory Stop already refused that theater.

When-to-use table (cite-worthy core)

Quotable: If judges need the Unreal Editor to open your MegaJam entry, you did not submit a packaged game — you submitted a homework folder.

Excuse ladder

Honesty ladder (run before any “we submitted” claim)

Fail H2–H6 and you do not get to tweet a trophy emoji.

CapEx four-liner (diligence zip cover)

1. Scope — MegaJam Unreal entries ship packaged playable builds only; UEFN entries ship private version codes only; no dual-engine; no late submits.
2. Cost — day-two package dry-run vs Sunday DQ / unplayable folder.
3. Evidence — H1–H8 + package log or private version id + itch confirmation.
4. Owner — submit lead who refuses folder zips in the diligence deck.

Pasteable diligence line:

MegaJam Unreal submissions are packaged playable builds (not project folders). UEFN submissions use private version codes. We refuse dual-engine hedges and late-spinner folklore. SUBMIT_OK requires package/code smoke before the Nov 15 5:59 PM PST cliff.

Refusal receipt (print / paste)

RECEIPT: UNPACKAGED_AS_SUBMIT_REFUSAL_v1
date: ________
team: ________
engine: UE / UEFN
artifact_type: packaged_zip / private_version / FOLDER_REJECT / LIVE_CODE_REJECT
clean_smoke_y_n: ________
dual_engine_attempt_y_n: ________
itch_confirm_before_cliff_y_n: ________
decision: PACKAGE_OK / PRIVATE_VERSION_OK / HOLD / DQ_LATE
h_ladder_pass_y_n: ________
owner_sign: ________
notes: ________

Latch PACKAGE_OK / PRIVATE_VERSION_OK only with H2–H6 green. Latch HOLD if packaging fails before cliff with a named retry. Latch DQ_LATE honestly if the cliff passed — do not launder it as SUBMIT_OK.

Beginner path — one evening refuse + package smoke

Prerequisites: UE entry (if UEFN, jump to private version mint instead). Skim Packaging Unreal Engine Projects. Use Unreal Engine guide hub for orientation. Paste Discord via 25 Discords.

1. Read jam don’ts aloud to the team.
2. Circle UE (this path) — confirm not dual.
3. Package Development Windows build.
4. Copy build to a clean folder/machine without opening the .uproject.
5. Launch the packaged executable; smoke 3 minutes.
6. Zip as TeamName_GameName; check size.
7. If >1 GB, configure butler/Blendo — don’t discover this at 5:40 PM.
8. Dry-run itch project upload on day two.
9. Fill submission worksheet sections for video/roster.
10. Final submit with ≥90 minutes buffer; screenshot confirmation.
11. Sign refusal receipt PACKAGE_OK.
12. Paste Discord: “Stop submitting unpackaged Unreal projects to MegaJam — we packaged.”

Common beginner mistakes: zipping Saved/ + Intermediate/ chaos; first-ever package on Sunday; shipping Debug Editor targets; assuming itch file accept = rules pass; UEFN live code “for now.”

Developer path — make packaging boring before Sunday

1. Automate or checklist: cook → stage → zip → size gate → upload.
2. Day-two dry-run with a throwaway map if needed — prove the pipeline.
3. Pin package configuration (Development) and target platform notes from the jam page.
4. Exclude editor-only plugins that break cooked builds; fix before freeze.
5. Log cook errors with owners; do not “retry blind” during cliff hour.
6. For large builds: butler credentials tested mid-week.
7. UEFN track: practice minting a private version mid-jam; final mint after content freeze.
8. Never dual-branch “UE backup + UEFN backup” as two jam submits.
9. Treat MCP/agent success as unrelated to submit legality (MCP docs).
10. After SUBMIT_OK, archive the exact zip hash / private version id for continuation-grant storytelling.

Creator Monday (Sunday) checklist

• [ ] Discord Stop pasted once (folder ≠ submit).
• [ ] Engine XOR public.
• [ ] Packaged smoke or private version minted.
• [ ] No live UEFN code in the form.
• [ ] Size/butler plan written.
• [ ] itch confirmation screenshot before cliff.
• [ ] Submission worksheet filled.
• [ ] Refusal receipt signed.
• [ ] Dual-engine hedge refused aloud.
• [ ] Late-spinner folklore refused aloud.
• [ ] Preflight sibling linked for anyone still installing tools.
• [ ] AI-mandatory Stop linked if agents are blamed for skipping package.

Failure modes

Opinion spine — what “stop” means in practice

Quotable takeaway: Stop submitting unpackaged Unreal projects to Epic AI MegaJam. Package the game. Mint the private version. One engine. Before the cliff.

Company diligence extras

• Ban “source drop” language in jam postmortems for MegaJam UE entries.
• Require package log or private version id in the compliance zip.
• Separate AI-tooling spend from packaging competence in CapEx notes.
• Treat late DQ as a process failure, not a platform conspiracy.
• If a contractor delivers “jam ready,” define ready as packaged smoke + itch confirmation — not editor demo day.

Packaging receipt table (cite beside the Stop)

Print G1–G10 next to UNPACKAGED_AS_SUBMIT_REFUSAL_v1. If G3 is missing, you are still in editor folklore.

What “packaged” is not

Buffer math (Sunday reality)

Assume cook can fail once. Plan:

1. Content freeze T−4 hours.
2. Package attempt 1 at T−3.5 hours.
3. Smoke + fix window 60–90 minutes.
4. Package attempt 2 if needed.
5. Zip + upload start by T−90 minutes.
6. Form fields + screenshot by T−30 minutes.
7. Hands off Discord arguments after SUBMIT_OK.

Teams that start packaging at T−20 minutes are choosing UNPACKAGED_AS_SUBMIT pressure. The submission worksheet already asks for buffer — this Stop explains why folding that buffer into “one more feature” is a diligence fail.

Worked example — UE team almost folders

Sunday 4 PM: game runs in editor; someone starts zipping the repo. Lead runs this Stop. Team packages Development build (90 minutes), smokes on a second PC, zips FoxDash_Jam.zip at 700 MB, uploads at 5:00 PM PST, confirms itch jam submit, signs PACKAGE_OK. The folder zip is deleted from the itch draft.

Worked example — UEFN live-code temptation

Solo dev has a public island code for friends. Jam page rejects live/playtest codes. They mint a private version after freeze, paste that code into itch, shoot video from that snapshot, SUBMIT_OK. Post-jam island edits do not mutate the judged snapshot.

Worked example — dual-engine hedge refused

Team argues Best Overall UE and UEFN both look juicy. Jam don’ts forbid both. They pick UE, package once, and stop the UEFN “backup island.” Odds are not increased by a rule break.

Key takeaways

1. Jam don’ts: no unpackaged Unreal projects.
2. Package a playable build; smoke without the editor.
3. Zip naming + size/butler plan matter.
4. UEFN: private version code only.
5. No dual UE+UEFN entries.
6. Late = DQ — cliff is Nov 15, 5:59 PM PST.
7. Itch file accept ≠ rule compliance.
8. Day-two package dry-run beats Sunday first cook.
9. Use the submission worksheet for form fields.
10. AI optional — packaging still required.
11. Sign UNPACKAGED_AS_SUBMIT_REFUSAL_v1.
12. CapEx four-liner belongs in the diligence zip.
13. Quotable: folder ≠ submission.
14. Preflight checks ≠ packaged submit.
15. Archive artifact ids for continuation-grant stories.

FAQ

Can judges open my .uproject if I include instructions?

The jam forbids unpackaged Unreal Engine projects. Do not rely on editor workflows as the submit artifact.

What should I upload for Unreal Engine?

A packaged playable build, zipped per jam naming/size rules, on your itch project, submitted to the jam. See packaging docs.

What about UEFN?

Submit a private version code created before the deadline — not live island or playtest codes.

Can we enter Unreal and UEFN?

No. Pick one.

Does starting the upload before 5:59 PM PST count if it finishes late?

Treat the cliff as hard. Leave time; late submissions are disqualified per the jam page. Do not launder late finishes as on-time.

Is this the same as the AI-mandatory Stop?

No. That refuses AI theater. This refuses unpackaged/dual/late submit folklore.

Where is the fill-in submit lab?

Epic AI MegaJam Submission Worksheet Before November 15 - 2026.

When should we first package?

Jam tip energy: test build on day two. Do not make Sunday the first cook.

Does butler change the unpackaged rule?

No. Butler helps large packaged uploads. It does not legalize project folders.

What if packaging fails an hour before the cliff?

HOLD with honesty, keep trying inside the cliff, or accept you may not make a legal submit — do not folder-zip as a fake pass.

Sources

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