Context switch
The week 7 checkpoint — one prototype that puts at least three earlier primitives behind a single button, switched by state
Make one button mean three different things, and make it obvious which one applies right now.
Week 7’s session had you switch between two mechanics behind one piece of state — enough to prove the switch itself was legible. This assessment asks for the same technique again, on your own, extended to three mechanics or more. The brief is still not about inventing anything new: it’s about combining vocabulary you already have without confusing the player about which mode is currently active, now that there’s more for a player to keep straight than there was in the session. A prototype that works but leaves a first-time player guessing has not met the brief, whatever else it does well.
What you submit#
A single runnable prototype, plus a one-paragraph note naming the three (or more) primitives it combines and the state that switches between them.
The spec
The brief poses the problem and leaves room for a response. The spec is the fixed part: what a marker checks. Some lines can be checked mechanically; the rest call for judgement.
- a working prototype combines at least three primitives from weeks 1 through 6 behind one button
- a piece of state, visible to the player, decides which meaning currently applies
How it is marked
| Criterion | Weight |
|---|---|
| Correct use of three or more earlier primitives | 40% |
| The mode switch is legible to a first-time player | 60% |