Ling Dota 2 Replay Deep Dive v0.2: Map Impact Windows

Date: 2026-06-03

Player: Ling, account_id 179107140

Hero: Rubick

Match: 8834032913

Result: Radiant loss, 54:27, 36-36

Evidence:

• Valve replay downloaded and parsed locally for death timestamps.
• OpenDota parsed match summary used for objectives, teamfights, wards, purchases, and gold/xp advantage.
• This is sliding-window event review, not player POV camera review.

What Changed From v0.1

v0.1 answered:

Which Rubick deaths mattered?

v0.2 answers:

Did Rubick's actions change the map, and when did aggression stop converting into objectives?

This matters because Ling's own read is reasonable:

Sometimes aggressive play is correct if it creates advantage. Too passive can also hurt the team.

The evidence supports that. Ling was not just feeding. Early Rubick map impact was real. The issue is that after the map shifted into Roshan/high-ground mode, Rubick deaths became more expensive than the plays they were trying to create.

Claim Audit: Did Rubick Help Build Early Mid Advantage?

Short answer:

Yes, this claim is supported.

Evidence from 0:00-12:00:

• Radiant gold advantage moved from 0 to +2377.
• Radiant XP advantage moved from 0 to +1119.
• Rubick kill involvement:
• 3:19 killed Lich
• 8:09 killed Lich
• 11:11 killed Terrorblade
• 12:27 killed Night Stalker
• Rubick had tower credit at 10:01 when Radiant took Dire T1 mid.
• Rubick placed early vision/sentries around 1:04, 2:59, 5:43, 7:37, and 9:37.

That is not passive support play. It is active map impact.

Coaching interpretation:

Ling's early aggression was creating usable map advantage. Do not remove this part of his style.

The first death at 12:41 is not a major criticism point because it came inside a fight where Rubick killed Night Stalker and Radiant had already gained map value.

Window 1: 0:00-12:00 Early Mid/Map Impact

Rubick's early-map contribution was positive.

Important signals:

• Early wards/sentries helped create usable information.
• Rubick participated in kills before and around the first mid tower.
• Radiant was ahead in gold and XP by the end of the window.
• Dire T1 mid fell at 10:01 with Rubick credited.

Classification:

correct aggression, map-positive.

Training note:

Keep this early style. The correction is not "stop moving." The correction is "know when the game changes from creating chaos to preserving objective control."

Window 2: 29:01-30:58 Blink Timing And Mid Collapse

This is where the game starts to punish the same aggression pattern.

Evidence:

• Rubick bought Blink at 29:01.
• Rubick died at 30:18 to Terrorblade.
• Dire took Radiant T1 mid at 29:59.
• Dire took Radiant T2 mid at 30:58.
• In the 29:56-30:37 teamfight, Radiant had 3 deaths and Dire had 0.

Radiant still had some XP advantage, but the map result was bad:

Dire converted the fight into the mid tower chain.

Classification:

wrong or over-expensive aggression; map-negative.

Coaching question:

After Blink, was Rubick trying to start a fight, save a tower, or chase a kill? If the answer was "start a fight," the team needed a clear objective conversion plan. If the answer was "save tower," Rubick could not die first.

Window 3: 36:37-38:08 Rubick Death Into Dire Roshan

This is the clearest objective-window death.

Evidence:

• Rubick died at 37:03 to Snapfire.
• Radiant took Dire T2 top at 37:36.
• Dire killed Roshan at 38:08.
• Terrorblade took Aegis at 38:09.
• In the nearby teamfight, Radiant had 3 deaths and Dire had 1.
• Radiant gold advantage dropped from +1074 to -80.
• Radiant XP advantage dropped from +5193 to -8.

This is the key nuance:

Radiant did get an objective: Dire T2 top. But Dire got Roshan and Aegis, which mattered more for the next phase.

Classification:

objective trade lost.

Coaching interpretation:

Rubick's death before Roshan did not just add one death. It helped convert the map from Radiant's partial outer-tower pressure into Dire's Aegis/high-ground setup.

Training rule:

If Roshan is live, a support death is only acceptable if it wins Roshan access or forces a better trade than Aegis.

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

This is the second major objective-window death.

Evidence:

• Rubick died at 45:39 to Terrorblade.
• Dire took Radiant mid T3 at 46:29.
• Dire took Radiant mid ranged barracks at 46:32.
• Dire took Radiant mid melee barracks at 46:43.
• Radiant gold advantage moved from -1142 to -2781.
• Radiant XP advantage moved from +1645 to -5185.

This is exactly where late Rubick life becomes more valuable than another pick attempt.

Classification:

high-ground-window death; map-critical.

Coaching interpretation:

Rubick's value here is not first-contact initiation. It is staying alive to slow Terrorblade, steal/control a fight spell, save a core, and force Dire to spend more time hitting buildings.

Window 5: 49:31-50:16 Positive Late-Fight Sample

This is the proof that Ling's aggression can still work late.

Evidence:

• Rubick did not die.
• Rubick killed Snapfire at 49:47.
• Rubick killed Night Stalker at 49:54.
• Rubick gained +1930 gold and +4945 XP in the teamfight.
• Radiant took a 3-for-1 fight result.

But the surrounding map context was still bad:

• Dire had already killed Roshan at 48:19.
• Terrorblade had Aegis.
• Dire had taken Radiant bot T2, bot T3, and bot ranged racks before the fight fully stabilized.

Classification:

correct aggression, strong fight execution, but late relative to objective damage.

Coaching interpretation:

This is the model for late Rubick: live through the first contact, cast multiple times, and punish enemy backline/core access. The issue is that the map had already been damaged by earlier objective-window deaths.

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

Evidence:

• Rubick died at 53:58 to Terrorblade.
• Dire killed both Radiant T4s at 54:17 and 54:20.
• Dire ended at 54:28.
• Radiant lost 5 heroes in the final teamfight.
• Rubick used Blink and Glimmer, but Glimmer was purchased at 50:40, very late.

Classification:

final-defense death, mostly downstream of earlier Roshan/high-ground loss.

Coaching interpretation:

By this point, the game needed perfect support survival. The survival layer existed, but too late.

Map Impact Pattern

The pattern is not:

Ling is too aggressive.

The pattern is:

Ling's aggression is good when it changes lane/mid-map state, but dangerous when the game state requires support survival for Roshan or high-ground defense.

Early game:

• Rubick aggression created kills, vision, and mid tower value.
• This supports Ling's self-read.

Mid/late game:

• Rubick deaths near 30:18, 37:03, and 45:39 coincided with Dire objective conversions.
• Those deaths were not equal to the early death at 12:41.

The coaching target is timing recognition:

Same aggressive instinct, different map state. Different rule.

Revised Training Rule

Use two modes:

Chaos-Creation Mode

Allowed before enemy Roshan/high-ground pressure is online.

Rubick can:

• rotate early
• pressure mid
• take risky but high-value trades
• force fights if the payoff is tower/rune/vision

This was good in the first 12 minutes.

Objective-Preservation Mode

Required when Roshan/high-ground/TB push is the next map event.

Rubick must:

• live through first contact
• cast twice
• avoid dying before Roshan
• avoid dying before high-ground defense
• buy survival/displacement before the fight demands it

This failed in the 37:03 and 45:39 windows.

Coach Verdict

Ling's self-judgment is partly correct and should be preserved:

His early aggression helped Radiant build mid-map advantage.

The correction is not to make him passive. The correction is to make him change modes when the map state changes.

Plain version:

前 12 分钟你确实在帮队伍打开地图，尤其是中路和视野，这不是 feed。问题从 Blink 后开始：30 分钟以后，Roshan 和高地变成主线，你的命比一次先手更值钱。你要保留前期主动性，但到 Roshan/守高窗口必须切换成“活到第二轮技能”的模式。