Back

Ten-player Dota 2 team profile: individual notes, contribution values, teammate synergy, and win-condition structure.

Dota 2 Match 8834032913 Ten-Player Team Profile

Match: 8834032913

Duration: 54:27

Result: Dire win, kills 36-36

Radiant: Lion / Necrophos / Legion Commander / Luna / Rubick

Dire: Hoodwink / Snapfire / Lich / Terrorblade / Night Stalker

Goal: upgrade the review from a Ling/Rubick-focused report into a full ten-player match profile with individual player notes, team contribution value, teammate synergy value, and key-window explanation.

Data Boundary

This report uses:

This is not first-person VOD/camera review. It cannot see comms, camera discipline, exact click intent, or pixel-level positioning.

Coaching posture:

State what the data confirms.
Label event-chain interpretation as coaching judgment.

Scoring Model

Contribution score is a coaching heuristic, not an official Dota metric.

It uses:

Synergy score:

kill co-participation * 2 + teamfight co-activity

Meaning:

Overall Read

This was not a true even game just because kills ended 36-36.

Radiant's strengths:

Dire's win condition:

Team-level difference:

Team Contribution total Hero damage Tower damage Net worth Vision index Deaths
Radiant 207.3 170,159 10,615 117,565 70.5 37
Dire 258.2 182,794 26,583 129,237 84.0 36

The largest difference was not kills. It was building conversion:

Dire tower damage: 26,583
Radiant tower damage: 10,615

Terrorblade alone dealt 22,219 tower damage, nearly twice Radiant's total tower damage.

Short version:

Radiant could kill heroes. Dire could end the game. Radiant had pickoff and fight tools, but Dire had a cleaner Roshan -> Aegis -> high ground -> barracks -> Ancient route.

Ten-Player Table

Side Hero KDA KP Net worth Hero dmg Tower dmg Vision Contribution
Radiant Lion 2/11/14 44.4% 10,171 13,469 71 9 obs / 15 sen 24.7
Radiant Necrophos 13/6/10 63.9% 36,470 56,633 1,558 2 / 1 52.5
Radiant Legion Commander 9/5/20 80.6% 21,949 39,037 1,157 0 / 3 42.3
Radiant Luna 4/4/11 41.7% 32,714 36,164 7,611 0 / 0 46.5
Radiant Rubick 8/11/19 75.0% 16,261 24,856 218 12 / 17 41.3
Dire Hoodwink 5/4/25 83.3% 20,664 32,858 1,116 8 / 15 48.7
Dire Snapfire 12/8/13 69.4% 28,716 49,493 1,615 2 / 0 45.5
Dire Lich 3/11/22 69.4% 16,491 21,900 269 16 / 30 44.8
Dire Terrorblade 12/4/12 66.7% 42,046 51,448 22,219 0 / 0 84.9
Dire Night Stalker 4/9/24 77.8% 21,320 27,095 1,364 0 / 0 34.3

First read:

Radiant Player Notes

1. Lion

Data:

Lion did some support work. The vision count is real. The issue is that his deaths were too expensive, especially once Dire shifted into Night Stalker backline pressure plus Terrorblade building pressure.

Pressure sources against Lion:

That says Dire were not randomly killing Lion. Their whole system squeezed Radiant's backline.

Ideal Lion job:

Do not reveal first.
Do not trade your life for an uncertain start.
Live behind the core line and punish Night Stalker/Terrorblade when they enter.

Repair points:

Short read:

Lion did work, but too often became a consumable support. In late game he needed to be counter-control, not vision sacrifice.

2. Necrophos

Data:

Necrophos was Radiant's strongest individual performer. Damage was not the problem.

The problem:

Huge damage did not become enough map control.

Key fights:

Repair:

Short read:

Necrophos was Radiant's fight core, but not the map finisher. His damage needed a faster objective call.

3. Legion Commander

Data:

Legion Commander was Radiant's primary connector and initiator.

Radiant's top synergy:

Pair Kill co-participation Teamfight co-activity Synergy
LC + Rubick 19 7 45
Necrophos + LC 18 7 43
Necrophos + Rubick 16 7 39

Radiant's real structure was:

LC starts
Rubick connects control/spell utility
Necrophos follows with damage
Luna should convert the result into buildings

The first half worked. The final conversion did not.

Repair:

Short read:

LC was Radiant's best team connector. The issue was not finding fights; it was turning good starts into map-ending objectives.

4. Luna

Data:

Luna did not feed. Four deaths in a 54:27 game is healthy, and her tower damage led Radiant.

But the opposite carry was Terrorblade.

Tower race:

Luna: 7,611
Terrorblade: 22,219

Luna's objective moments:

Terrorblade's objective chain was much longer and cleaner.

Repair:

Short read:

Luna was not bad. She lost the objective race. Against TB, surviving is not enough; every won fight has to become structure damage.

5. Rubick / Ling

Data:

In the ten-player view, Rubick was not simply a high-death support. He had 75% KP, meaningful damage, heavy vision work, and the strongest Radiant synergy pair with LC.

The previous personal diagnosis still holds:

Rubick was an early engine.
After 30 minutes, Rubick's deaths became much more expensive.

Early evidence:

High-cost death windows:

Positive late proof:

Repair:

Short read:

Rubick was one of Radiant's tempo cores, but did not complete the late-game mode switch from playmaker to second-cycle control.

Dire Player Notes

6. Hoodwink

Data:

Hoodwink was a hidden MVP candidate.

Terrorblade was the finisher, but Hoodwink made Radiant's backline unsafe. 83.3% KP with meaningful vision work means she was inside almost every fight chain.

Her strongest pair:

Hoodwink + Night Stalker
kill co-participation 23
teamfight co-activity 7
synergy score 53

Hoodwink's jobs:

Short read:

Hoodwink was Dire's hunting radar. She made Night Stalker's backline pressure executable.

7. Snapfire

Data:

Snapfire was Dire's second damage core.

Key fight damage:

Snapfire died 8 times, but those deaths were less structurally damaging than Radiant support deaths because Dire's main objective engine was TB. If Snapfire cast and softened the fight, TB could still finish structures.

Short read:

Snapfire was the teamfight artillery. Not perfectly clean, but high enough damage to let TB convert.

8. Lich

Data:

Lich's KDA looks rough, but contribution is real.

He was Dire's vision sink:

16 observer wards
30 sentries
69.4% kill participation

Radiant targeted him heavily:

Lich died often, but Dire still won because his deaths did not stop the TB objective chain. That is the difference from Radiant Lion/Rubick deaths.

Short read:

Lich was a high-sacrifice vision support. His deaths were acceptable when vision and spells had already enabled TB.

9. Terrorblade

Data:

Terrorblade was the deciding player.

Not because he killed the most heroes. Necrophos had 13 kills.

Because TB converted windows into buildings.

Objective chain:

TB synergy:

Dire's team was organized around him:

NS/Hoodwink find backline
Snapfire supplies fight damage
Lich supplies vision/utility
TB takes buildings

Short read:

Terrorblade was not merely farmed. He connected kills, Roshan, Aegis, high ground, barracks, and Ancient into one win condition.

10. Night Stalker

Data:

Night Stalker's contribution score is modest because of 9 deaths and low tower damage, but tactical value was higher than the score.

His job:

Make Radiant's backline unsafe.
Stop Lion/Rubick from freely casting while TB hits buildings.

Pressure signals:

That explains why Radiant's late control chain broke down.

Short read:

Night Stalker was the darkness/backline pressure piece. His KDA was not pretty, but he damaged Radiant's support positioning enough for TB to end.

Synergy Map

Radiant Synergy

Pair Kill co-participation Teamfight co-activity Synergy Coaching read
LC + Rubick 19 7 45 Radiant's real pickoff engine.
Necrophos + LC 18 7 43 Main fight-core chain.
Necrophos + Rubick 16 7 39 Control plus sustained damage; strong early/mid.
Necrophos + Luna 15 7 37 Fight connection exists, objective follow-up less stable.
LC + Luna 14 7 35 Should be pickoff-to-tower chain, but did not beat TB.
Lion + LC 13 6 32 Control overlap exists, but Lion deaths hurt.
Luna + Rubick 10 7 27 Active together, but not the strongest kill chain.
Lion + Rubick 10 6 26 Double support participation, but also double support pressure target.

Radiant's real shape:

LC/Rubick start
Necrophos follows with damage
Luna should hit buildings
Lion should counter-control and provide vision

The first half worked. Objective conversion did not.

Dire Synergy

Pair Kill co-participation Teamfight co-activity Synergy Coaching read
Hoodwink + Night Stalker 23 7 53 Best hunting pair in the game.
Terrorblade + Night Stalker 19 7 45 NS creates chaos, TB cleans and hits buildings.
Snapfire + Terrorblade 18 7 43 Teamfight damage plus objective finisher.
Hoodwink + Snapfire 18 7 43 Ranged catch and burst chain.
Snapfire + Night Stalker 18 7 43 NS holds targets, Snapfire damages them.
Lich + Night Stalker 18 7 43 Darkness pressure plus utility.
Snapfire + Lich 17 7 41 Backline spell coverage.
Hoodwink + Lich 17 7 41 Vision/control/attrition chain.

Dire's real shape:

Hoodwink + NS find backline
Snapfire + Lich provide spell coverage and vision
Terrorblade takes Roshan, Aegis, buildings, and the game

Dire's task alignment was much cleaner.

Key Windows

Window 1: 0-12, Radiant Early Advantage Was Real

Evidence:

Judgment:

Radiant's early game was not failure. Ling's claim that Rubick helped build early mid/map advantage is supported, and it was not only Rubick. Necro, LC, and Lion were also part of the early kill chain.

The problem was not creating advantage. It was converting that advantage faster than TB converted his windows.

Window 2: 29:56-30:37, Dire Mid Conversion

Teamfight:

Objective:

Judgment:

This was the first major turning point. Radiant was not economically dead yet, but mid-map structure collapsed.

Rubick's 30:18 death mattered, but the wider team issue was failing to turn Necro damage and LC/Rubick control into mid defense or counter-objective.

Window 3: 36:37-38:08, Radiant Tower But Dire Roshan

Radiant:

Dire:

Teamfight:

Judgment:

Radiant got a tower. Dire got the more important resource. Against Terrorblade, Roshan/Aegis matters more than one outer tower.

Window 4: 45:39-46:43, Mid High Ground Break

Events:

Judgment:

This was the TB system cashing out. Once one Radiant control support died, TB's building speed was too high.

Window 5: 49:31-50:16, Radiant Good Fight But Map Already Damaged

Teamfight:

But Dire had already taken:

Judgment:

Radiant could still fight late. The problem was that the good fight happened after TB had already converted too much map value.

Window 6: 53:32-54:14, Final Defense

Teamfight:

Objective:

Judgment:

The final fight was not one person's isolated mistake. It was the accumulated result of Roshan control, barracks pressure, and TB endgame conversion.

Team Profiles

Radiant

Strengths:

Problems:

  1. Kill-to-objective conversion was unstable.

Radiant had 36 kills but only 10,615 tower damage.

  1. Backline supports were squeezed.

Lion died 11; Rubick died 11. Hoodwink + NS + Snapfire + TB repeatedly broke support positioning.

  1. Luna lost the objective race.

Luna tower damage 7,611; TB 22,219.

  1. Roshan priority was lost.

Dire secured Roshan at 38:08 and 48:19, both going to Terrorblade.

Radiant sentence:

Radiant could fight, but did not consistently turn fights into game-ending resources.

Dire

Strengths:

Weaknesses:

Dire sentence:

Dire could be hit early, but the mid-late plan was clear: protect TB, take Roshan, take buildings.

Training Notes

Radiant Training Line

1. Ten-second objective call after every kill

After LC/Rubick/Necro win a fight, the team must immediately call:

Tower?
Roshan?
Deep vision?
Lane?
Buyback pressure?
Reset?

Do not stop at "we killed one."

2. Late support survival layer

Lion/Rubick were too fragile against Night Stalker + TB pressure.

Targets:

3. Luna objective-race training

Luna cannot only play to not die.

Question after every won fight:

Can I hit a building within 15 seconds?
If not, should I already have pushed another lane?

4. Roshan priority

Against TB, Roshan is not optional. After 35:00, every kill must connect to Rosh vision, pit control, buyback tracking, or direct trade.

Dire Training Line

1. Keep TB objective identity

This game's win pattern was correct. Do not let TB become only a farmer. When the window appears, hit buildings.

2. Preserve Hoodwink + NS backline linkage

This was the strongest pair in the game:

3. Lich sacrifice needs a ceiling

Lich died 11, but the contribution was still high.

Rule:

Death after vision/spells are delivered can be acceptable.
Death before vision/spells/Roshan setup is not.

Final Coaching Verdict

Best full-match profile:

Radiant = pickoff and fight-output team.
Dire = backline pressure plus TB objective-conversion team.

Radiant's loss was not only Ling's problem, not only Luna's problem, and not because Necrophos lacked damage.

Radiant's structural issue:

  1. LC/Rubick/Necro created kills.
  2. Kills did not consistently become Luna buildings or Roshan.
  3. Lion/Rubick were pressured too hard by Hoodwink/NS/TB.
  4. Dire won two Roshan/Aegis windows.
  5. TB converted every Aegis/high-ground window into structures.

Dire's structural win:

  1. TB was the absolute finisher.
  2. Hoodwink + NS controlled Radiant backline space.
  3. Snapfire/Lich supplied damage, utility, and vision.
  4. The whole team served one win condition.

Updated conclusion for Ling:

Your early Rubick impact was real. In the ten-player view, you were neither the only problem nor the only engine. Radiant's bigger loss pattern was that the pickoff chain did not reliably connect to Luna buildings or Roshan, while Dire's backline pressure broke the support layer and TB converted the map. Your personal repair remains the same after 30 minutes: live to second spell cycle. The team repair is kill -> objective, especially Roshan and Luna structure conversion.

Radiant one-liner:

You can kill heroes. Now learn to use kills to end the game.

Dire one-liner:

You won because everyone knew how Terrorblade wins.