Captures And Reels
The day-to-day proof of a game change is a capture or a reel from the seeded scenarios, never a hand recording. One capture script per level labels its stills by the ticket's id and writes them into the wiki's image folder, linked from the ticket's Done part. One reel script per level records highlights as segments and joins them into one video with the game's own sound.
Why
The director can reproduce every state a capture shows.
Captures
- A capture belongs to one ticket and is taken while that ticket is in progress, to see that what was just made looks good. It goes in the ticket's Done part (The Done Part). There is no capture batch of every level at the close.
- A later ticket that changes what an earlier capture shows takes a new capture under a new file name. A capture is never retaken under its old name, which would erase the step before.
- A report that hands a visible change made outside a ticket to the director carries its picture. A ticket's picture stands in its Done part.
- Wait for the intro to settle before a still. Capture only what changed, plus a sanity check.
- Every capture is read before it goes on the page (Review Every Capture Before Reporting).
Reels
- Reels are recorded on demand only, never at a version's close: with a playtest on every version the director sees the motion and sound first hand. The reels' flows still run quickly as tests, without recording.
- A segment starts from a scenario, marks its cut when the scene is on screen, records the sound, and saves both. The joiner orders the segments by recording time, since a shortened folder name loses its number.
- A level's reel runs on into the next level's opening. The changelog keeps a copy of a reel, when one is made, under the version's name.
- An edge flow worked on in the iteration goes into the level's reel or a small video of its own, so the director sees the flow that changed.
In A Browser
- Park the mouse in a corner and hide any app frame the game draws, such as a custom title bar, before a still.
- A segment records the sound by tapping the audio graph in the page.
How To Apply
- Suites and capture runs are muted (Silent Runs).
- Only the reel records sound.
- The videos stay untracked in git, the reels and the changelog's copies alike, since they are heavy and a reel, when one is made, is made for one version. Only chosen ones, such as a store page's, get tracked later. Ignore the video folders on day one.