Risks and what we do about them
Ranked by how likely they are to sink the entry. Owner in brackets.
1. Missing the deadline or the time zone (Producer)
- Risk: a late entry is disqualified. The clock is ET; daylight time ended Nov 1, so ET is UTC minus 5. itch lists the end as 01:59 UTC on Nov 16, which is the same moment and easy to misread.
- Do: our deadline is Sun 4 PM ET, five hours early. Alarms at noon, 2 PM and 4 PM. Hard stop: if not submitted by 6 PM, Don submits the last golden build as is. Golden builds exist from Thu 23:00 on. Every time in our docs is ET.
2. Packaging failure (Build and QA)
- Risk: the game runs in the editor but fails to package, crashes on a clean PC, needs the VC++ runtime, or goes over 1 GB.
-
Do:
- Package the empty project at hour 2 (M1), then every evening and every night. A failed package is a stop the line event.
- Turn on app local prerequisites so judges install nothing.
-
Clean machine check: launch each RC in Windows Sandbox on the laptop (a clean Windows with no Unreal or runtimes; a fresh user account still sees the installed runtimes, and tower 2 can't show a game window over ssh). Sandbox has no real GPU, so it proves the game starts with nothing missing, not its speed. Sandbox is a Windows feature, so Don turns it on (one checkbox) if he wants this check; without it,
smoke.ps1plus app local prerequisites is our cover. - Track zip size on every build; the alarm is at 700 MB.
- Pre jam: practice the full package, zip and upload path on a throwaway project and time the upload on Don's connection.
3. Scope creep (Producer)
- Risk: agents make adding things cheap, so the game grows and nothing gets polished. This is the classic jam killer, and agents make it worse.
-
Do: the cut list is written on theme day. At most 5 must ship items. Feature lock Fri 22:00, content lock Sat 20:00, code freeze Sun 10:00. After a lock, the producer says no; Don can overrule. Any new idea goes to
later.md, not the build.
4. MCP is slow or wrong (Editor driver)
- Risk: Unreal MCP in 5.8 is experimental. Puget's test saw 5 to 15 minute replies, broken player controls, fixes it claimed but didn't make, and no PCG. Niagara emitters can't be authored from Python in 5.8 (found on the Heist). 5.9 adds Niagara and MetaSound authoring through MCP but renames the MCP tools, and it is a preview build (MCP-RUNBOOK.md); the Wednesday gate decides which risk we take.
-
Do:
- One agent drives the editor; everyone else hands it tickets, so prompts never collide.
- Blueprint only. Logic is planned in text and built by Python editor scripts in git that the driver runs, so MCP does wiring, not thinking.
- Every MCP change is verified by a check (a test map, a screenshot, a value read back), never by the agent's word.
- Controls and camera are hand tuned against feel targets.
- Niagara: start from Unreal's built in emitter templates and set parameters; budget a GUI step for anything new.
- If MCP is down for more than 30 minutes, the driver switches to Python editor scripting and command line builds.
5. The laptop is a single point of failure (Producer, Build and QA)
- Risk: the 4090 laptop holds the editor and MCP. A dead drive, a Windows Update reboot, a thermal shutdown or a corrupted map could cost a day.
-
Do:
-
Push the project every hour to
origin, tower 1's bare mirror (set up 2026-11-09), withprep/scripts/push.ps1. That covers a dead laptop but not a house wide outage (item 15). - At each golden, tower 2 pulls the project from tower 1. It has the same engines as the laptop (5.8.4 and 5.9.0, checked 2026-11-10) and can open it as a hot spare.
- Rehearse the switch on Wed Nov 11 morning with ToolCheck (agents, no Don): clone from tower 1, open, package on tower 2, time it.
- Don pauses Windows Update on both Windows machines until Nov 16 (a system setting, so only he can).
- Keep the laptop on mains power, on a hard surface, with the fans clear.
-
Push the project every hour to
6. Don's sleep and time (Producer)
- Risk: a tired Don makes worse calls and the studio stalls waiting for him.
- Do: Don is needed about 5 hours across five days (SCHEDULE.md has the list), all between 9 AM and 7 PM. Nothing needs him between 11 PM and 8 AM. Every call he doesn't have to make, the studio makes (STANDARDS: Don judges taste, not basics). If he misses a slot, the producer's default stands and he hears about it in the next batch message.
7. Token budget runs out mid jam (Producer)
- Risk: four days of many agents can hit the Claude usage limits (Puget hit a Team plan's session limit before midday on a small test). In September Don paused all work for quota.
- Do: check usage before the jam and every morning. Don's plan limits reset Thu Nov 12 at 4 PM ET, inside the window. Fable 5.2 runs only Saturday's integration push, on Don's plan resets, with the second reset kept as Sunday insurance. Every agent runs at its job's tier (Haiku for searches and logs, Sonnet for scoped tickets, Opus for judgment; SCHEDULE.md). Night work goes to machines (generation, bakes, bots, packaging), not to Claude. Agents get short, specific tickets. If the budget looks tight by Friday noon, the producer cuts the nice list first and pauses the scribe's extras, never the build and QA agent.
8. Eligibility: content made before Nov 12 (Producer)
- Risk: rule 7h allows only tools, agent configs, MCP settings, prompt libraries and scripts before the jam, and Epic may ask for version history.
-
Do:
game/stays empty until midnight, and theme day stops at the pick (PLAYBOOK.md). The pre jam table in the dev log lists the studio-pipeline commit thatmj_gen.pydepends on, since it is tooling we use too. Machine clocks are checked against internet time on Wed so git dates are honest. Nothing from Heist, Late Checkout or other lab games goes in: no code (including the Heist choice engine), no art, no sounds. Theme day docs are plain text plans, declared in the dev log. Every commit has honest dates.
9. It looks or reads as AI (Art lead, writer, review panel)
- Risk: the jam thread is hostile to AI slop; glossy sheen, melted shapes, model lettering or tell heavy text will cost visuals, audio and fun scores.
- Do: canon first images from real engine renders, the critic models, a fresh reviewer side by side, no model lettering (all text in real fonts), WRITING.md tells linter plus a read aloud on every line. When an AI asset loses to a hand built one, the hand built one ships.
10. Trademark or teen content slip (Review panel)
- Risk: a generated texture shows a real logo or brand, or a scene goes past Teen. Either can disqualify the entry.
- Do: every generated image is checked for lettering and marks. Prompts say "no text, no logos". The final checklist has a line for each. No real people, brands or places.
11. Judges can't run it well (Build and QA)
- Risk: a 2025 thread asked whether 4080 class entries shut judges out. Lumen at high settings can crawl on mid range cards.
- Do: default settings must hold 60 fps at 1080p on tower 2's AMD GPU, with a scalability menu. Don't ship features that only run on RTX hardware.
12. Touch on a Windows build (Gameplay coder)
- Risk: our rule says every test build works on controller, touch and keyboard. Judges will use keys or a pad, but a touch laptop must work too, and Unreal's touch on Windows needs setup.
- Do: Enhanced Input with all three device maps from hour 0; on screen controls show when a touch arrives and hide on pad or key input; test on the touch laptop at M3, M6 and M8.
13. Tower 1 GPU contention (Art lead, audio lead)
- Risk: ComfyUI, the critic model and music generation share one 24 GB GPU; a stuck job blocks art and audio together.
- Do: the lab GPU lock queues jobs; jobs are resumable; the laptop's 4090 can take FLUX overflow at night when the editor is idle.
14. The upload or itch fails on Sunday (Don, Build and QA)
- Risk: a slow upload on Don's connection, an itch outage near the deadline, or a broken video link.
- Do: Don makes the itch game page as a Draft on Friday and uploads a golden build to it on Saturday, so Sunday is a swap, not a first upload. Upload at 2 PM, not 8 PM. Test the upload speed before the jam. butler (installed) is the fallback, run by Don himself under his own login; agents only prepare the command. Keep the zip, video file and dev log text on a USB stick too.
15. Power or network outage (Producer)
- Risk: a home outage takes all three machines.
- Do: nothing in the house is off site: tower 1's mirror and tower 2's goldens go down with the power. The off site copy is the golden on Don's Draft itch page from Saturday, so Don can submit from his phone if power is out on Sunday. The kit's text (fields, sourced list, dev log) goes on the USB stick with the zip and video (item 14).