The agent watches ten complete Super Smash Bros. Melee games from three tournament sets in one video and lists, in order, every conversion: one player’s continuous punish on the other that lands four or more hits or takes a stock. For each it gives the game, the attacker, the victim’s stock count beforehand, the number of hits, a damage band and how it ended. The reference holds 104 conversions.
What a good answer has to get right, and how the verifier checks it
- Every conversion is found, in order
- The answer is compared with the reference as a sequence: the verifier counts the longest run of entries that appear in both lists in the same order. No timestamps are asked for; the order carries the timing.
- The conversion is attributed
- Game number, attacker and the victim’s stock count before it must be exact.
- The hits are counted
- The hit count must be exact. The task defines what counts as a hit, including each pummel and each damaging part of a multi-hit move.
- The damage and the ending are classed
- The damage band (under 25%, 25% to under 50%, 50% or more) and the ending (kill, reversal or escape) must be exact.
How the checks become one score
Score = F1 = 2 × precision × recall / (precision + recall). Recall is matched conversions over 104; precision is matched conversions over every entry in the file, including entries the verifier rejects as invalid. An entry counts only when all six fields are right.
What scores zero
No solution file or one that cannot be read, an empty list, or a list in which no entry is right on all six fields.
Outside the score: conversions of fewer than four hits that do not kill, which the task says not to report; an entry for one is invalid and lowers precision. The verifier also reports matches on game, attacker, stock and ending alone, as a diagnostic.