Background Image
如何赢得迅捷斥候与河流之王的对抗赛迅捷斥候 is in the a tier of champions

迅捷斥候 vs 河流之王

如何在LoL中以迅捷斥候的身份击败河流之王迅捷斥候 is in the s tier of champions
MarksmanAssassin
SupportTank

如何击败河流之王成为迅捷斥候

based on 7,717 迅捷斥候 vs 河流之王 matchups
胜率
48.9 %
kda
1.81
受欢迎度
2.5 %

How We Analyze LoL Champion Counters

We summarize our counter stats from the millions of rated LoL rounds that we get from Riot Games every week. This guide on how to beat 河流之王 as 迅捷斥候 came out of an evaluation of 7717 ranked games where both champs faced one another. This counter pairing is fairly rare. 迅捷斥候 has to counter 河流之王 in only 2.5% of his rounds.

迅捷斥候 vs 河流之王 Matchup Summary

Unfortunately, 迅捷斥候 has done a poor job of countering 河流之王. On average, he wins a acceptable 48.9% of games the champions face each other in. In 迅捷斥候 versus 河流之王 rounds, 迅捷斥候’s side is 0.0% more probable to obtain first blood. This indicates that he most likely will get first blood against 河流之王.

counterTitle

物品

第一项

期望时间
生命药水云游图鉴

下一个项目

5分钟
鞋子爆裂魔杖

Core 迅捷斥候 Items

22分钟
影焰风暴狂涌兰德里的折磨

可选项目

星界驱驰灭世者的死亡之帽虚空之杖裂隙制造者

Summoner Spells

summonerflash summoner spell D
summonerdot summoner spell F

技能顺序

为迅捷斥候提升等级的第一个技能q
>
为迅捷斥候提供的第二种能力,以提高水平e
>
迅捷斥候 最大化的最后一项技能w

符文

坚决不灭之握爆破骸骨镀层过度生长
主宰恶意中伤终极猎人
Adaptive ForceAdaptive ForceArmor
迅捷斥候's passive ability p
迅捷斥候's q ability q
迅捷斥候's w ability w
迅捷斥候's e ability e
迅捷斥候's ultimate ability r
1
Q
2
E
3
W
4
Q
5
Q
6
R
7
Q
8
E
9
Q
10
E
11
R
12
E
13
E
14
W
15
W
16
R

Guide to Countering 河流之王 as 迅捷斥候

Tips for Playing as 迅捷斥候 against 河流之王

- 提莫的蘑菇用来打钱是很有效的。

- 将你的蘑菇放在地图上的关键位置,比如靠近龙或纳什男爵的地方,以便在敌人试图杀死他们的时候能侦查到。

Advice to Win Against 河流之王

当你看到塔姆使用了来自【厚实表皮】的护盾时,说明他舍弃了一次可观的治疗。在【厚实表皮】冷却完毕前,他将不会积累新的灰色生命值。

要留意塔姆的【深渊潜航】 - 你只能用禁锢类控制效果才能打断他的引导。

迅捷斥候 vs 河流之王 Counter Stats

迅捷斥候 Image
winRate
48.9 %
VS
winRate
51.1 %
河流之王 Image
5
< kills >
5.5
6.7
< deaths >
5.1
7.1
< assists >
8.1
1.11
< killingSprees >
1.24
127
< cs >
123
0.21
< dragons >
0.07
0.45
< inhibitors >
0.5
2,975
< physicalDamage >
3,625
24,247
< magicDamage >
15,222
1,747
< trueDamage >
721
28,969
< damageDealt >
19,569
21,939
< damageTaken >
42,640
11,095
< goldEarned >
10,872
1.91
< towers >
2.07
0.06
< barons >
0.02
3,000
< heal >
12,963
13,979
< xp >
13,996
27
< visionScore >
25
11
< wardsPlaced >
11
505
< ccTime >
296

How to Counter 河流之王 with 迅捷斥候 in LoL

The stats shown here feature some significant 迅捷斥候 against 河流之王 matchup stats that can help us figure out the distinctions between the pair. As an example, 迅捷斥候’s KDA ratio ([kills + assists] / deaths) of NaN is better than 河流之王’s KDA ratio of NaN, highlighting that 迅捷斥候 may be more central to his team's team fighting potential than 河流之王..

迅捷斥候 often has a similar longest kill spree as his counter does. Typically, he takes less damage than 河流之王. This often reflects different amounts of tankyness; however, it can also indicate that the one champ has less mobility and thus is unable to kite away from further harm when engaged or poked.

championDifferences.title

伤害数据

迅捷斥候
河流之王
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

迅捷斥候
河流之王

championDifferences.whoIsBetter

Both League champions are great. Both champs have their strengths, weaknesses, and counters. In the game's current meta, 迅捷斥候 usually loses when trying to fight 河流之王, with a 48.9% win rate. Thus, 迅捷斥候 makes a poor counter to 河流之王.

While 迅捷斥候 does have a lower winrate than 河流之王, when facing one another, 迅捷斥候 also has a greater learning curve that makes him a more challenging character to develop with. You still need to be cautious when picking 迅捷斥候 into 河流之王.

Furthermore, 迅捷斥候 also has some amount of CC and other utility, a similar amount to 河流之王. This makes her just as valuable during teamfights, especially when facing champions with a lot of burst damage.

While there is not one best champion overall in League of Legends, in 迅捷斥候 vs 河流之王 matchups, 河流之王 is the better champion with a lower win rate, more champion depth, and a similar amount of utility to help out your team members during team fights.

迅捷斥候 is a somewhat poor counter for 河流之王. Make sure you focus your strategy on maximizing your CS and taking out objectives. If you can do that, you should hold your own as 迅捷斥候 against 河流之王.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

If you would like to learn all of the intricacies of 迅捷斥候 to counter 河流之王 during both the laning and mid / late game phases of League of Legends, you should keep reading to pick up a few extra lessons on this matchup. If you mind the build and stats shown above, you will increase your win rate significantly and be closer to League of Legends pro players.

迅捷斥候 typically racks up a similar amount of CS relative to 河流之王. Champions who typically don't acquire much CS often don't have to have much CS to be valuable teammates, such as supports. These kinds of champions are capable of scaling well off of their abilities and first items alone. Yet, champs with a lot of CS, such as hyper-carries, typically have to have several high cost items to be effective. In either case, try to do better than the numbers displayed on this page to do well.

The most important items to prioritize in your 迅捷斥候 versus 河流之王 build include 影焰, 风暴狂涌, and 兰德里的折磨. When 迅捷斥候 incorporated at least these three items in his build, he did a lot better vs 河流之王 than with most other typical item sets. In fact, 迅捷斥候 had an average winrate of 48.9% when countering 河流之王 with this build.

To have the greatest likelihood of vanquishing 河流之王 as 迅捷斥候, 迅捷斥候 players should equip the 不灭之握, 爆破, 骸骨镀层, 过度生长, 恶意中伤, and 终极猎人 runes from the 坚决 and 主宰 rune sets. Of all the runes players picked for 迅捷斥候 vs 河流之王 counterpicks, this set of runes resulted in the best win rate. Moreover, these runes averaged a 48.9% winrate overall.

If you would like to get 迅捷斥候 vs 河流之王 tips and matchup stats and build suggestions for a a distinct division rank, feel free to select one from the selection menu displayed above. If viewing for the first time, the statistics and build suggestions shown are calculated using every round played with both champions.