Separate a fixed performance from active play
game-build uses pre-rendered media for short fixed performances without player-controlled perspective or space. A beautiful video cannot replace required control or invent a gameplay result.
Original game: the player repairs a lighthouse circuit in the correct order, and rules confirm the light is on. A cutscene can show the beam crossing the sea and a ship responding. If the player still needs to aim the beam to locate the ship, that remains play rather than an automatic film.
Identify the confirmed result and where control resumes. A repair input rejected for missing materials must not trigger a successful illumination animation.
Plan boundaries and skip results together
| Item | Lighthouse sequence |
|---|---|
| Trigger | Repair result already committed |
| Start | Light on; player remains in the control room |
| Required fact | Ship responded; guidance is available |
| End | Signal action becomes available in the control room |
| Skip | Response summary and the same playable state |
| Fallback | Still plus sound or text preserving response and next action |
Boundaries preserve identity, objects, space and story state. A broken old lamp, absent character or premature secret needs repair despite attractive imagery.
Skipping bypasses presentation, not the rule result. Watchers and skippers must retain necessary conditions. Playback and skip callbacks must not each award the same reward.
Complete paper paths: a response is not a safe arrival
Keep the control room and lighthouse. This candidate adds an explicit design: repair commits once and triggers a subsequent response event. During the sequence, the same story rule commits the ship’s acknowledgement; the player does not decide it. Watch, skip and media failure all pass through that response node. No item reward or automatic guidance signal is added. These are unbuilt, untested design paths.
Watch: After repair the control room reads, “Circuit repaired; light on; awaiting the ship’s response.” The beam sweeps across the sea. When the response event actually arrives, the ship flashes back and text reads, “Ship acknowledged; guidance signal available.” Playback ends in the control room. Sending is available but has not happened.
Skip: From the same repaired state, skipping stops the presentation. If the response event has not arrived, show “Light on; awaiting the ship’s response” without unlocking guidance early. Once the same response node commits, summarize acknowledgement and enable sending in the control room. Preserve necessary information without adding a captain’s secret.
Media failure: This candidate classifies the sequence as degradable. A failed video uses a still of the lit tower and text. Wait while acknowledgement is pending; when it arrives, display the same confirmation and enable sending. Media failure means neither repair failure nor an already received response.
All three paths end with repair complete, acknowledgement received and sending awaiting player input. A design selecting no response must show its actual waiting or failure outcome rather than apply this success summary. Classifying media as degradable is this example’s choice; other projects follow their own required effects.
Handle failed media and interrupted playback
Decide whether the media is essential or degradable before production. A failed degradable video uses its approved still or reduced-motion expression. Missing essential media needs an explicit failure rather than treating a black screen as completion. A fallback preserves the same fact, not a generic success message.
Check loading, start, skip, focus loss, mute and return of control. Essential information cannot exist only in speech; reduced motion must still show the repaired light and ship response.
Use drafts to check boundary facts before increasing dimensions. Provider and format depend on the environment and need official capability checks. No single generation model is promised to solve every cutscene.
Compare watching, skipping and fallback paths
From the same initial state, follow watch, skip and fallback paths. Compare location, objects, knowledge, rewards and next actions. Presentation can differ, but each reaches its declared legal state.
Check repeated skip input, completion callbacks, loading after viewing and necessary input when media is missing. These tests establish runtime relationships, not pacing or enjoyment.
If one path reveals more, check whether that knowledge should become public now. An intended difference belongs in gameplay design rather than accidental player behavior. The cutscene communicates a confirmed change and returns control reliably.
FAQ
Can skipping omit essential story information?
If the fact is needed for the next choice, preserve it through a brief summary, still or accessible record. Skipping shortens presentation without removing understanding of the current state.
Do it with the skill
Use game-build to review this approved cutscene. List trigger, boundaries, required information and skip or fallback results. Compare state and input opportunities across paths; prevent duplicate presentation rewards.
Read the method: Dynamic media, skipping and fallback · Presentation reads committed state