In-Engine Cutscene

Engine drives characters through scripted actions while input is ignored or reduced, then hands control back. Because the same assets are used, a scene can cut to a location the player will later occupy, or show an antagonist doing something elsewhere. Length and frequency are the design levers, and the crucial question is always what a scene does that the playable portion could not have done instead.

Jordan Mechner's Karateka in 1984 cut between the approaching hero and events inside the fortress, including a princess and a captor the player had not yet met. Technique came from cinema literacy applied to an 8-bit computer, and it worked because rotoscoped animation was expressive enough to carry a moment without text. Nothing extra had to be stored, since the scenes reused the game's own sprites and backgrounds.

Scenes became the default way games deliver plot, and the argument about them started almost immediately, since taking the controller is the one thing an interactive medium is uniquely able not to do. Costs are concrete too, because cutscenes consume budget, resist localisation and interrupt pacing. Every later technique, from full-motion video to fully playable dialogue, is a response to the same unsolved tension.