Chapter 23 — Quiz

Eighteen questions testing your grasp of cutscene craft, history, and decision-making. Answer before checking the answer key at the bottom.

Questions

1. According to the chapter's framing, which of the following is a legitimate reason to use a cutscene?

a) To explain the control scheme at the start of the game. b) To deliver exposition about the world's lore before the player cares. c) To land a narrative payoff the gameplay cannot stage. d) To reward the player by making them watch their victory.

2. The chapter calls one of these the "original sin of cutscene design." Which?

a) Using pre-rendered cutscenes instead of in-engine. b) Confusing games with the medium (film) you grew up on. c) Making cutscenes skippable. d) Using music that is too loud during dialogue.

3. What is the primary advantage of in-engine cutscenes over pre-rendered?

a) Higher visual fidelity. b) Smaller file size on disc. c) Continuity between the gameplay world and the cutscene world. d) Faster production time.

4. Which game is cited in the chapter as the canonical example of pre-rendered cutscenes delivering photographic (for their era) cinema?

a) The Last of Us. b) Final Fantasy VII (1997). c) Uncharted 4. d) Red Dead Redemption 2.

5. The chapter identifies four legitimate reasons to use a cutscene. Which of these is NOT one of them?

a) Narrative payoff. b) Character moment. c) Tutorial instruction. d) Showing the impossible.

6. According to the chapter, what is the correct default stance on cutscene skippability?

a) Story cutscenes should be unskippable; only transitional cutscenes should be skippable. b) All cutscenes should be skippable, with no exceptions. c) Cutscenes should be skippable only on second playthrough. d) Only cutscenes over five minutes should be skippable.

7. The chapter targets a specific default length range as "the sweet spot for most in-game cutscenes." What is it?

a) 3-10 seconds. b) 10-30 seconds. c) 45-90 seconds. d) 2-5 minutes.

8. What is the chapter's stance on cutscenes as rewards for player achievement?

a) They are the purest form of reward; use them generously. b) They are appropriate only after final bosses. c) They are a design trap; rewards for play should be more play, not the cessation of play. d) They are fine if they unlock after the credits.

9. Which game is Case Study 23.1 focused on?

a) Metal Gear Solid 4. b) The Last of Us Part II. c) God of War (2018). d) Final Fantasy XVI.

10. Which game's 71-minute cutscene is treated as a cautionary tale in the chapter?

a) Metal Gear Solid 4. b) Xenogears. c) Death Stranding. d) Kingdom Hearts III.

11. What does the term "QTE" stand for?

a) Quick Tactical Event. b) Quick Time Event. c) Quest Transition Event. d) Queued Timing Element.

12. The chapter identifies three conditions under which QTEs tend to work. Which of the following is NOT one of those conditions?

a) The button thematically corresponds to the action. b) The timing window is generous (at least ~1 second). c) Failure is interesting rather than merely punitive. d) The QTE appears during every major cutscene for consistency.

13. What is the "paraphrase gap" that the chapter mentions (originally from Chapter 21 but referenced here)?

a) The space between two characters on screen. b) The difference between what a dialogue wheel summary suggests and what the character actually says. c) The time between cuts in a cutscene. d) The loss of meaning when translating across languages.

14. Which studio is cited in the chapter as the contemporary gold standard for in-engine cutscenes?

a) Rockstar Games. b) Naughty Dog. c) Square Enix. d) Kojima Productions.

15. What technique is the chapter's "seamless one-shot" section specifically associated with?

a) Red Dead Redemption 2. b) The Last of Us Part II. c) God of War (2018). d) Uncharted 4.

16. According to the chapter's camera-language guidance, what is the "180-degree rule"?

a) Characters should face the camera at a 180-degree angle. b) The camera should rotate 180 degrees during conversation scenes. c) The camera should stay on one side of an imaginary line between two characters. d) Cuts should occur every 180 degrees of camera rotation.

17. What is the chapter's recommended length budget for the cutscenes in a prototype?

a) At least 2 minutes per cutscene to deliver emotional impact. b) Under 30 seconds per cutscene. c) As long as necessary to deliver the beat. d) Under 10 seconds per cutscene, no exceptions.

18. The chapter's five-question framework for deciding whether to use a cutscene includes all but one of the following. Which is NOT in the framework?

a) What specific beat does this cutscene land? b) Could gameplay deliver this beat? c) Will this cutscene be skippable? d) How much will this cutscene cost to produce?

Answer Key

1. c) To land a narrative payoff the gameplay cannot stage. (The other three are specifically called out in the chapter as wrong reasons to use cutscenes.)

2. b) Confusing games with the medium (film) you grew up on. (This is the chapter's framing in the opening section — the "original sin" of reaching for a film-grammar tool without asking whether the game-grammar alternative would serve better.)

3. c) Continuity between the gameplay world and the cutscene world. (In-engine cutscenes use the same character models, lighting, and rendering as gameplay, so the world remains visually coherent.)

4. b) Final Fantasy VII (1997). (The canonical PS1-era example of pre-rendered cutscenes that defined the era.)

5. c) Tutorial instruction. (The other three — narrative payoff, character moment, showing the impossible — are all legitimate. Tutorials should almost always be taught through gameplay, not cutscenes.)

6. b) All cutscenes should be skippable, with no exceptions. (The chapter is emphatic on this point. Every cutscene, every time, skippable.)

7. b) 10-30 seconds. (This is the chapter's "default range for most scenes." Under 10s is free to use; 30s-90s reserved for major beats; beyond that, used very sparingly.)

8. c) They are a design trap; rewards for play should be more play, not the cessation of play. (The chapter argues that cutscene-as-reward treats the player as audience rather than player.)

9. c) God of War (2018). (The case study on Cory Barlog's one-shot camera and the "no cuts" philosophy.)

10. a) Metal Gear Solid 4. (Case Study 23.2 and the Design Autopsy block reference the 71-minute cutscene.)

11. b) Quick Time Event.

12. d) The QTE appears during every major cutscene for consistency. (This is not a condition for success; in fact, it is close to the failure mode the chapter warns against. The three conditions are: thematic button mapping, generous timing, interesting failure.)

13. b) The difference between what a dialogue wheel summary suggests and what the character actually says. (Referenced as connecting to Chapter 21; mentioned here as context.)

14. b) Naughty Dog. (Uncharted and The Last of Us series are explicitly cited as the contemporary gold standard for in-engine cutscenes.)

15. c) God of War (2018). (The "no cuts" philosophy was implemented across the entire game — Cory Barlog's signature achievement.)

16. c) The camera should stay on one side of an imaginary line between two characters. (Crossing the line disorients the viewer; characters appear to swap positions.)

17. b) Under 30 seconds per cutscene. (This is the Project Checkpoint target — brief in-engine cutscenes, each under 30 seconds.)

18. d) How much will this cutscene cost to produce? (Not in the framework. The five questions are: what beat does it land, could gameplay deliver it, could environmental storytelling deliver it, how long, and will it be skippable.)

Scoring

• 17-18 correct: You are ready to design cutscenes. Move on to the case studies with confidence.
• 14-16 correct: Solid grasp; skim the questions you missed and re-read the related sections before the case studies.
• 10-13 correct: You have the main ideas but have missed some specifics. Re-read the "When to Use" / "When NOT to Use" sections and the length guidelines before continuing.
• Under 10: The chapter deserves another pass. Re-read, then retake. The concepts matter; do not move on until they have landed.

A Note on These Questions

Several questions have "obviously correct" answers — the chapter telegraphs strongly that cutscenes should be skippable, that tutorials are not a cutscene job, that 71 minutes is too long. These are the chapter's central commitments; the quiz is partly a check that you have internalized them.

A few questions test specific content (which case study, which studio, which length range). Miss these without alarm; look them up and move on. They matter less than the commitments.

The most important question on this quiz is question 18 — the framework question. When you design, you will not carry specifics in memory; you will carry the framework. Make sure the five questions are in your head, even if the exact wording drifts. The framework is the chapter's gift to your practice.