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."
}Keep scanner results JSON-only
Rank and review typed visual observations in your own UI. Scanner runs never render. If a scouting, coaching, or publishing workflow later needs an MP4, submit a separate one-off analysis and render selected Moment IDs from that flow.
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, or deterministic game telemetry parser. When authoritative telemetry exists, combine it with observation metadata rather than treating visual relevance as ground truth.