10.1b — 2-Button Jam: Build Day 1
Build Day 1 rule: end the day with the core loop — BOTH verbs working, something to act on, a lose state. Ugly is fine; non-playable is not. A jam that leaves Day 1 without its loop spends Day 3 building the loop instead of the game.
Build Day
~50 min
Build order (the loop skeleton):
- Read both inputs — one line each, GetKeyDown. Print to console on press. Nothing else works until this does:
if (Input.GetKeyDown(KeyCode.LeftArrow)) Debug.Log("A");
if (Input.GetKeyDown(KeyCode.RightArrow)) Debug.Log("B");
- Verb 1 with a placeholder — say DUCK: scale the player sprite to 0.5 height. One line of code, instantly testable, already FUN to spam.
- Verb 2 with a placeholder — DASH: a 0.15s Translate burst in facing direction. Your 3.3 cooldown pattern IS the dash (it is a fire rate on a movement).
- Something to act on — one obstacle, one pickup, one enemy. ANY one. Borrow the starter's spike or coin prefab wholesale.
- One lose state — the death loop you have written twice (2.2); here it can just be "restart the scene."
Checkpoint ritual (last 10 minutes): pass the keyboard around the team — each member plays the loop for 30 seconds. Anyone who cannot play it cannot build on it.
Close of Day
~5 min
Socratic: Core Loop First
- You built both verbs as placeholders before building anything else. What did the placeholder let you find out today that finished art and tuned numbers would have hidden?
- The rule was make it run ugly first. Which of your ugly things is genuinely unfinished, and which one is a design problem wearing ugly clothes?
- Your loop is playable but every number in it is a guess. Which single number do you tune first tomorrow, and what will you watch to decide it?
Checkpoint — before moving on, you must be able to:
- Play your own loop: both verbs, one obstacle, one lose state
- Explain the build order and why inputs print before mechanics
- Name your riskiest task for Day 2
Reference Docs
Need a deeper explanation? These pages cover the same concepts:
- Unit 10: Jam Season — jam build orders
- 10.1a — Kickoff — your pitch card
Saved on this device only — the Dashboard tracks your progress.