Chapter 28 — Quiz

Answers with explanations are at the end. Try to answer before checking.

1. The chapter argues that multiplayer design differs from single-player design because:

A. Multiplayer games have larger budgets. B. In multiplayer, you author the preconditions for player-generated moments rather than authoring the moments themselves. C. Multiplayer games require more polish. D. Multiplayer games have longer development cycles.

2. The "player is the content" idea means:

A. Players should be able to create game content like maps and mods. B. The memorable moments in multiplayer games are generated by other players' actions, not by the designer's scripted content. C. Every player should have their own character. D. Players should playtest the game before shipping.

3. Which of the following is not a failure mode of cooperative design?

A. The solo-carry problem, where one player dominates and the others spectate. B. The skill cliff, where new players cannot get a foothold and the population thins into a top layer. C. Scripted beats being blitzed past by fast teams at three times the speed of a single player. D. Players standing behind the strongest team member while they handle all threats.

4. Why is a hybrid multiplayer game (like Destiny 2 or Sea of Thieves) harder to design than a pure cooperative or pure competitive game?

A. The two logics have opposite demands — cooperation wants you to help your teammates, competition wants you to not help your opponents, and the boundary between them becomes a design variable. B. Hybrid games require more content. C. Hybrid games have longer matches. D. Hybrid games use more server bandwidth.

5. The chapter argues async-leaderboard design (games like Trials Rising) is underused because:

A. It is too expensive to implement. B. It solves the population problem, eliminates latency issues, and lets players pause the game — for a fraction of the engineering cost of synchronous multiplayer — but most studios default to synchronous PvP instead. C. Players prefer synchronous games. D. It does not produce enough player engagement.

6. In matchmaking, the "fairness vs. queue time tradeoff" means:

A. Fair matches are slower to assemble than unfair ones. B. Studios have to choose whether to be fair or fast. C. Tighter skill matching produces longer queue times because the search criteria exclude more potential matches; looser matching produces faster queues but more lopsided matches. D. Queue time is the most important metric in matchmaking.

7. What is "lag compensation" and why is it controversial?

(Short answer, 100-200 words.)

8. Why does the chapter argue that toxicity is "a design output, not a community failing"?

A. Game designers are responsible for preventing all negative player behavior. B. The communication affordances shipped (voice, text, pings, emotes, report systems) directly shape the distribution of player behavior, so toxicity is the predictable consequence of channel-design decisions rather than an organic property of players. C. Communities should not be blamed for anything. D. Toxicity only happens in games with bad design.

9. Apex Legends's ping-only communication system is described in the chapter as:

A. A technical workaround for broken voice chat. B. A market-access strategy that expanded the audience by removing friction for players who cannot or will not voice-chat with strangers. C. A cost-cutting measure. D. A response to regulatory pressure.

10. What is "rollback netcode" and in which genre was it first widely deployed?

(Short answer, 100-200 words.)

11. A healthy competitive meta, according to the chapter, has:

A. One dominant strategy that everyone uses. B. Rock-paper-scissors between three strategies with no skill expression inside the choice. C. Three to five dominant strategies, each with counters, each requiring different skills, rotating as patches evolve. D. Identical win rates across all options.

12. Why is asymmetric multiplayer (like Dead by Daylight or Evolve) the hardest of all multiplayer disciplines?

A. It requires more content than symmetric multiplayer. B. The balancing problem is multi-dimensional — you are balancing across role, map, team composition, and player count simultaneously, with nearly-disjoint player experiences that must remain equally satisfying. C. The netcode requirements are higher. D. Asymmetric games have smaller audiences.

13. The "death of the honeymoon" in the multiplayer lifecycle typically happens:

A. In the first week after launch. B. Around months three to six, when the initial audience has exhausted launch content and the social meta has stabilized. C. At the game's one-year anniversary. D. When a sequel releases.

14. In the Godot example code, why is _sync_position annotated as unreliable_ordered while take_damage is annotated as reliable?

A. Because damage events are more expensive than position updates. B. Because position is continuous state that gets overwritten every tick (a dropped packet is fine, the next one will correct it), while damage is a one-shot event whose delivery must not be dropped. C. Because of Godot syntax requirements. D. Because reliable RPCs are faster.

Answers & Explanations

1. B. The core claim of the chapter's opening. In single-player you author the content; in multiplayer you author the preconditions. This framing shift is the whole point. Budget, polish, and cycle length may differ empirically, but they are not the reason multiplayer is a different discipline.

2. B. The memorable moments in any multiplayer game are almost always "remember when [other player] did [thing]" — not "that scripted scene in mission 3." The designer's job is to create clearings where those moments can happen; the players fill them in.

3. B. The skill cliff is a competitive failure mode, not a cooperative one. The other three — solo-carry, scripted-beats-bypassed, standing behind the strong player — are all cooperative failures discussed or implied in the chapter.

4. A. The opposite-demands framing is explicit in the chapter. The hybrid forms must manage both logics in the same design space, which is why boundary decisions (how big is your coop group? how far apart are the competitive encounters?) carry so much weight.

5. B. The chapter explicitly argues that async-leaderboard designs are a strong option that most studios skip in favor of defaulting to synchronous PvP — even when their goal could be achieved more cheaply and more scalably with ghosts, leaderboards, and async social framings.

6. C. The precise tradeoff: tighter matching excludes more potential opponents per query, so queues are longer; looser matching accepts wider skill differences for faster queues. Studios tune this regionally and by time of day.

7. Short answer. Lag compensation is the netcode technique where the server rewinds the game state by your client's ping and evaluates your shot (or action) against where the target was at the moment you pulled the trigger, not where they are when the server receives your input. This makes the shooter's experience feel responsive at realistic pings. It is controversial because the target's experience is that they "died behind cover" — from their local perspective, they had already run around the corner when the shot registered. The designer choosing lag compensation is implicitly choosing to favor the shooter's subjective experience over the target's. There is no neutral netcode choice; someone is always favored.

8. B. This is the chapter's explicit reframing. Toxicity is not random; it is distributed by channel. Games with no communication (like Journey) report low toxicity; games with unmoderated voice chat report high toxicity. If you ship the channels, you own the outcomes. The exercise for designers is to think of communication as a product decision with operations costs, not a feature to add without plan.

9. B. Ping-only was a deliberate decision that expanded the addressable audience — console players, casual players, players in rooms where they cannot speak, players uncomfortable with voice-chat-with-strangers. Respawn designed for the audience that would not have voice-chatted, and the audience grew accordingly.

10. Short answer. Rollback netcode is a technique where each client runs a full local simulation of the game and predicts what remote players are doing each frame. When actual remote inputs arrive (delayed by network latency), the client rolls back the simulation to the tick those inputs were supposed to apply to and replays forward with the corrected inputs. The result is that local inputs feel latency-free while the game remains synchronized across peers. The technique was pioneered and popularized in competitive fighting games — GGPO library, Killer Instinct (2013), Skullgirls, and now the standard for Arc System Works and modern Street Fighter. It is beginning to appear in other genres that need tight timing. The tradeoff is CPU cost (running multiple simulation passes per frame) and a specific visual artifact (brief "teleport" corrections when a prediction was wrong).

11. C. This is the competitive-design definition of health. One-strategy-dominant games die; rock-paper-scissors games feel un-skillful; a field of 3-5 interdependent strategies with skill expression inside each one is what the best competitive games sustain through patching.

12. B. The chapter's argument. The balancing problem is multiplied by the dimensions; Dead by Daylight has shipped 35+ killers and 40+ survivors and each addition is effectively a new mini-game that must remain fair against the existing roster. Evolve's collapse within a year of launch was substantially due to this balancing intractability.

13. B. The month-3-to-6 window is named explicitly in the chapter as the period where launch content is exhausted and the meta has stabilized. Studios that invested in Season 1 early retain; studios still fixing launch bugs lose their population.

14. B. The unreliable_ordered vs. reliable distinction is the netcode vocabulary applied to Godot's RPC system. Position is continuous state: dropping one packet is cheap because the next packet overwrites it. Damage is a discrete event: dropping the packet means the damage never happens, which is a correctness bug. You pay more bandwidth and more latency for reliability and only pay it where correctness requires it.