Death followed by an objective loss
You died at 9:27 with the team advantage at +490 souls. Within 90s your team lost: Guardian at 9:30, Guardian at 9:47. This sequence coincided with the objective loss; the data cannot show whether it caused it.
Only 1 earlier Warden match tracked. Comparisons start at 4. Each new Warden match is added automatically, so comparisons will appear here once there is enough history to mean something.
The Warden secured a win despite 10 deaths, leveraging top-tier economy (44,804 souls) and strong objective damage (11,427). Key swings in soul advantage highlight vulnerability to late-game engagements.
At 9:27 (567s), the Warden died with a +490 soul advantage. Within 90s, the team lost two Guardians, coinciding with a shift to a -11,902 soul disadvantage.
Positive means your team was ahead in total souls. Sampled at 9 points the API provides; the line between samples is interpolated.
You died at 9:27 with the team advantage at +490 souls. Within 90s your team lost: Guardian at 9:30, Guardian at 9:47. This sequence coincided with the objective loss; the data cannot show whether it caused it.
You died at 14:00 with the team advantage at +1,446 souls. Within 90s your team lost: Guardian at 14:09. This sequence coincided with the objective loss; the data cannot show whether it caused it.
Team soul advantage moved from +1,446 to -11,902 (lost 13,348). In the same window your team lost a Guardian; you died 2x.
Team soul advantage moved from -11,902 to -4,508 (gained 7,394). In the same window your team took a Walker; your team lost a Walker; you died 1x.
You died at 23:58 with the team advantage at -4,508 souls. Within 90s your team lost: Walker at 25:28. This sequence coincided with the objective loss; the data cannot show whether it caused it.
Team soul advantage moved from -4,080 to +29,747 (gained 33,827). In the same window your team took a Walker, a Base objective; your team lost a Walker; you died 1x.
21 purchases · 52,000 souls spent, in order.
Context around each of your deaths. The API does not expose map awareness or vision, so no positioning claims are made.