Gameplay moments need more than a spike detector. A useful result preserves setup, the decisive action, confirmation of the outcome, and the immediate reaction.
Use the gameplay profile
The gameplay profile activates the pipeline’s gameplay-oriented evidence and selection behavior. Keep the scanner instruction game- and outcome-specific: name what confirms a knock, elimination, win, save, failure, or strategic error.
{
"name": "Confirmed eliminations with reaction",
"type": "find_moments",
"profile": "gameplay",
"instructions": "Find decisive sequences where the player directly secures a confirmed elimination. Preserve the setup through confirmation and include the immediate reaction when present."
}Review before rendering
Rank and review timestamped observations in your own UI. Video find_moments observations include Moment IDs, so a scouting, coaching, or publishing workflow can explicitly render only the approved results.
Audio-only gameplay is commentary
An audio upload can use all six scanner methods for commentary questions, but it cannot prove a visible elimination, score, or UI state. Generated speech excerpts are not certified verbatim transcripts. Use video when the question depends on gameplay shown on screen.
Version game-specific rules
Confirmation signals change between games and modes. Update the scanner when the rule changes; new runs snapshot the new version and old results stay attributable to the definition that created them.
What this does not do
The current API analyzes completed recordings. It is not a live spectator feed, anti-cheat system, deterministic game telemetry parser, or certified transcript service. When authoritative telemetry exists, combine it with observation metadata rather than treating model relevance as ground truth.