VCT Americas Stage 2All ten teams
Primary navigation

playbyplay oracle

playbyplayoracle In beta

A Computer Vision Parser for Valorant VODs

Oracle reads VALORANT broadcasts. Our computer vision pipeline parses the killfeed and round clock, then links each recorded event to its moment in the video.

This version uses tournament broadcasts, without relying on match demo files. Search by player, team or round to review the footage. Missing events and uncertain timings are marked.

Roadmap

  1. Kill boundary

    Ongoing

    Identify who killed whom, place each kill within its round, and narrow down when it happened in the VOD. Check the sequence and flag gaps.

  2. Map awareness

    Planned

    Read player positions from the minimap. Track round-start setups, defaults, rotations and site hits as the round develops.

  3. Full VOD review

    Planned

    Review whole matches inside Oracle: mark moments, build clip lists, and turn them into strategy plans you can carry into prep.

Situation & provenance 19 more filters: round, series, agent, spike phase, man-count, clock, every class and mark 1 active
Where
–
Who
Situation
–

Not available. Killfeed weapon icons are not classified yet: the column exists and is empty for every event. Filtering on it would silently return nothing.

Provenance every mark is filterable
24 events searching… 21 rounds · 7 maps · 4 series ChronologicalMost recent
12 rounds have missing events. For the selected maps and series. Player and event filters do not hide these gaps. The missing events' positions in each round are unknown.
Where Kill Clock Video Marks Expand
G2 v C9BreezeR6jawgemoG2DEF→ZellsisC92v2+1:1415:02
G2 v C9SunsetR1jawgemoG2ATK→jawgemoG2same team2v0+1:0838:10
G2 v C9SunsetR1BABYBAYG2ATK→BABYBAYG2same team1v0+1:0838:10
G2 v C9SunsetR12leafG2ATK→jawgemoG2same team2v5+0:261:01:41
G2 v C9SunsetR18leafG2DEF→jawgemoG2same team4v4+0:381:15:27
KRU v G2BreezeR2valynG2DEF→valynG2same team1v4+1:058:30
KRU v G2BreezeR3leafG2DEF→heatKRU4v2+0:199:25
KRU v G2BreezeR4jawgemoG2DEF→heatKRU4v5+0:2210:47
KRU v G2BreezeR8jawgemoG2DEF→heatKRU4v5+0:1819:36
KRU v G2BreezeR11jawgemoG2DEF→heatKRU3v4+0:3624:42
KRU v G2LotusR23leafG2ATK→leafG2same team3v1+1:371:49:38
KRU v G2LotusR23trentG2ATK→trentG2same team2v1+1:381:49:39
G2 v SENBreezeR3valynG2DEF→ReduxxSEN4v5+1:035:47
G2 v SENBreezeR6jawgemoG2DEF→ReduxxSEN3v4+0:3713:50
G2 v SENBreezeR8not verified→trentG2——
G2 v SENBreezeR10leafG2DEF→ReduxxSEN5v4+0:2821:47
G2 v SENBreezeR22trentG2ATK→ReduxxSEN3v5+1:1353:49
G2 v SENSplitR13trentG2DEF→JerrwinSEN5v3+0:412:30:14
G2 v LOUDSunsetR3leafG2DEF→leafG2same team1v5+1:224:53
G2 v LOUDSunsetR12leafG2DEF→BABYBAYG2same team3v5+0:2627:40
G2 v LOUDSunsetR12valynG2DEF→valynG2same team1v0+1:1328:27
G2 v LOUDSunsetR18leafG2ATK→jawgemoG2same team4v3+0:1541:29
G2 v LOUDSunsetR24leafG2ATK→BABYBAYG2same team4v5+0:1452:35
G2 v LOUDSunsetR26leafG2ATK→valynG2same team3v1+0:5257:56
Rows follow the killfeed within each round: the broadcast printed the kills in this order. Two kills too close to time apart keep it and carry an . Marks less certain · single witness · outside match records · not an ordinary kill · needs a look · checked by a person. Expand any row to read them in full.
42 rounds in this filter were measured less precisely
  • Breeze R2: the exact end of the round is known only to within a few seconds
  • Breeze R3: the exact end of the round is known only to within a few seconds
  • Breeze R5: the exact end of the round is known only to within a few seconds; the on-screen scoreboard froze for a moment
  • Breeze R6: the exact end of the round is known only to within a few seconds; the on-screen scoreboard froze for a moment; kills landed after the round was already decided
  • Sunset R1: kills landed after the round was already decided
  • Sunset R3: the exact end of the round is known only to within a few seconds
  • Sunset R5: the exact end of the round is known only to within a few seconds
  • Sunset R11: the exact end of the round is known only to within a few seconds
  • Sunset R16: the exact end of the round is known only to within a few seconds
  • Sunset R18: the exact end of the round is known only to within a few seconds
  • Breeze R5: the exact end of the round is known only to within a few seconds
  • Breeze R7: the exact end of the round is known only to within a few seconds
  • Breeze R20: the exact end of the round is known only to within a few seconds
  • Lotus R2: the exact end of the round is known only to within a few seconds
  • Lotus R5: the on-screen scoreboard froze for a moment
  • Lotus R10: the on-screen scoreboard froze for a moment
  • Lotus R14: the exact end of the round is known only to within a few seconds
  • Lotus R15: the on-screen scoreboard froze for a moment
  • Lotus R19: the exact end of the round is known only to within a few seconds
  • Lotus R20: the on-screen scoreboard froze for a moment
  • Breeze R10: the exact end of the round is known only to within a few seconds; the on-screen scoreboard froze for a moment
  • Breeze R15: the on-screen scoreboard froze for a moment
  • Breeze R18: the exact end of the round is known only to within a few seconds
  • Breeze R19: the exact end of the round is known only to within a few seconds
  • Breeze R21: the exact end of the round is known only to within a few seconds
  • …and 17 more.
Run-up 0s 3s 6s 10s 15s
Watch at 4:24 ↗ BABYBAY → Zellsis · Breeze R1

Opens in one reused tab; a second click re-seeks the same tab. The broadcaster has embedding turned off for these VODs, so the video cannot play inside this page.

BABYBAY → Zellsis G2 v C9 · Breeze · R1 · feed:7

Seeking to 4:24 minus 6s run-up · round clock +1:16

Class
Kill
Record
In the match records
Timing
Timing exact
Order
Order certain
Witness
Single witness
Source
Read from the killfeed
Spike
No plant