10.1a — 2-Button Jam: Kickoff & Pitch

What counts as an input? Anything that becomes a signal: two keys, two buttons, one key + one mouse click, a touch's left half vs right half, keyboard-only arrow keys COUNT AS FOUR (banned!). Past-hit examples: one-button runners (flap = jump), one-button bosses (hold longer = higher jump), two-button fighters (left dodge, right attack). Every input you OWN, you must OWN COMPLETELY: timing, meaning in context, held vs. tapped.

Scoping rules for the 6-day jam (build days are 10.1b–10.1e):

• ONE verb is a mechanic; TWO verbs is a game; THREE is a scope lie. You have two buttons. Your game has two verbs. Done.
• Reuse what you own: any starter code, your palette class (9.2), your jump feel (6.3), your cooldown pattern. A jam is not a clean-slate test — it is a fluency test.
• The pitch sells the IDEA in one sentence: "It's ___ where the only two buttons are ___ and ___."

Write your pitch card (10 min):

1. One sentence: the game ("a cave where you can only DUCK and DASH")
2. Two verbs and their feel words (duck = commitment, dash = panic)
3. One image sketch: the screen at the most interesting MOMENT
4. Reused parts list (what you borrow vs. build — the jam-ethics version of 9.10 credits)

Pitch (30 seconds each) — then team up by vote. Every pitch gets three public votes. Top pitches recruit; you may join any team that will have you. Rules: teams of 1–3, every member writes code (no idea-guy-only roles), and every game ships SOMETHING playable by 10.1d — a finished small game beats an ambitious folder.