<!-- The gate: a one page build checklist from the SPOILED dev log. -->
<!-- Written from the studio's own gate lists. -->
<!-- Shared by BYOK Games under the MIT License -->

# The gate: what a build must show before anyone calls it ready

One page, taken from the lists the SPOILED studio used on its own builds. Use what fits.

## Before a build goes to the human

1. It starts from the normal start with no crash, in ten launches out of ten. Count hangs per launch, not per package.
2. Bots at three skill levels (passive, average and sharp) play the whole cut. Their numbers are in: deaths, damage and time per room, so unfair and dead stretches show up as numbers.
3. The frame rate lines are in: the mean, and the number inside the hardest fight. Our 3W package fell to a mean of 42 (27 in the fight) and 3X was gated on finding the cause. The 3X package ran at a mean of 66.
4. One full take has been watched end to end by the reviewing agent, and its log travels with the package: the packaged capture, the launch tally, the bot reports and the frame rate lines.
5. The opening was judged on packaged frames, not in the editor.
6. A checker passing is not a picture seen. Someone looks at the frames.
7. A look passes only as a side by side with a named reference.

## At the freeze

Anything not passed on packaged frames at the freeze ships off, behind a flag that defaults to off.

## Numbers from our last gate package (3X)

- 10 of 10 starts, mean 66 fps, 844 MiB against a 1 GB limit.
- Failed anyway, and written down: the mix peak read +1.9 dBTP, and 3 of 16 scares had their quiet.
