Replay Capture and Sharing
Replay capture records a match as game data rather than video, letting players rewatch it from any camera angle, pause anywhere, and export screenshots or clips to share.
Rather than storing pixels, the game stores inputs and events and re-simulates the match during playback. Because the world is rebuilt instead of replayed, the camera comes free: it can detach from any player, fly, slow down, or sit inside an explosion. Files are tiny next to video. Screenshots and short clips can be pulled from any moment and uploaded to a service outside the game entirely.
Bungie added saved films and a theatre mode to Halo 3 in 2007, alongside a web service that hosted whatever players captured. Determinism in the engine made it feasible, since a match already had to be reconstructible from inputs for networking reasons. Cultural timing supplied the rest, arriving as video sharing sites became mainstream while capture hardware was still expensive and awkward for console players.
Play turned into media, and the clip economy that now drives discovery for competitive games grew straight out of this capability. Consequences include a quiet change in how people play, because a highlight worth clipping is not always the correct decision. Fragility is the technical cost: a replay depends on the exact build that produced it, so patches invalidate archives and long-term preservation is close to impossible.
Lineage — traced back to a root
Every mechanic in this dataset resolves to an ancestral chain. This one is 8 steps deep, beginning with Object Collision As Verb in 1962.
Descends directly from
Carried forward by 2 later games
Look this mechanic up elsewhere
Also called: replay theatre, saved films, clip capture