Background Image
如何赢得迅捷斥候与赏金猎人的对抗赛迅捷斥候 is in the a tier of champions

迅捷斥候 vs 赏金猎人

如何在LoL中以迅捷斥候的身份击败赏金猎人迅捷斥候 is in the a tier of champions
MarksmanAssassin
Marksman

如何击败赏金猎人成为迅捷斥候

based on 42,843 迅捷斥候 vs 赏金猎人 matchups
胜率
49.2 %
kda
1.82
受欢迎度
14.1 %

How We Analyze LoL Champion Counters

We summarize our counter statistics from the millions of recently rated League of Legends games that we analyze each week. Our guide on how to beat 赏金猎人 as 迅捷斥候 resulted from an analysis of 42843 ranked games where both champs engaged one another. This particular matchup is somewhat common. 迅捷斥候 fights 赏金猎人 in 14.1% of his matches.

迅捷斥候 vs 赏金猎人 Matchup Summary

Unfortunately, 迅捷斥候 has done a dismal job of beating 赏金猎人. Normally, he wins a acceptable 49.2% of games the champions oppose each other in. In 迅捷斥候 vs 赏金猎人 games, 迅捷斥候’s team is 0.1% less probable to get first blood, implying that he probably won't be able to get first blood versus 赏金猎人.

counterTitle

物品

第一项

期望时间
黑暗封印复用型药水

下一个项目

5分钟
爆裂魔杖恶魔法典

Core 迅捷斥候 Items

22分钟
灭世者的死亡之帽扎兹沙克的溃口影焰

可选项目

蜕生星界驱驰巫妖之祸风暴狂涌

Summoner Spells

summonerflash summoner spell D
summonersmite 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
49.2 %
VS
winRate
50.8 %
赏金猎人 Image
5.4
< kills >
8.6
6.7
< deaths >
6.3
6.8
< assists >
7
1.24
< killingSprees >
1.98
134
< cs >
178
0.22
< dragons >
0.19
0.45
< inhibitors >
0.54
2,621
< physicalDamage >
20,899
23,075
< magicDamage >
1,289
1,739
< trueDamage >
970
27,436
< damageDealt >
23,159
22,455
< damageTaken >
21,744
11,503
< goldEarned >
13,284
1.9
< towers >
2.39
0.06
< barons >
0.05
3,081
< heal >
5,209
14,573
< xp >
13,461
27
< visionScore >
20
11
< wardsPlaced >
10
511
< ccTime >
157

How to Counter 赏金猎人 with 迅捷斥候 in LoL

The stat comparisons shown here clarify several critical 迅捷斥候 against 赏金猎人 matchup stats that may help us understand the differences between this set of champs. As an example, 迅捷斥候’s KDA ratio ([kills + assists] / deaths) of NaN is more than 赏金猎人’s ratio of NaN, showing that 迅捷斥候 may be more central to his team's team fighting effectiveness than 赏金猎人..

迅捷斥候 usually has a slightly smaller longest kill spree than his foe does. Typically, he takes a similar amount of damage to 赏金猎人. This is usually reflective of different amounts of tankyness, but it can also illustrate that the champ with more HP 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 of Legends champions are great champions. Both have their strengths, weaknesses, and counters. In the game's current meta, 迅捷斥候 usually fairs equally well when trying to fight 赏金猎人, with a 49.2% win rate. Thus, 迅捷斥候 makes an ok counter for 赏金猎人.

While 迅捷斥候 does have a lower winrate than 赏金猎人, when facing one another, 迅捷斥候 also has a much greater learning curve that makes him a more challenging champ to learn and master. You still need to be cautious when picking 迅捷斥候 into 赏金猎人.

Furthermore, 迅捷斥候 has some amount of utility and CC, a similar amount to 赏金猎人. This often makes her just as valuable during teamfights, especially when facing champions with a ton of burst damage.

While there isn't one best champion overall in League of Legends, in 迅捷斥候 vs 赏金猎人 matchups, 赏金猎人 is the better champ with a similar win rate, more champion depth, and a similar amount of utility to help out your teammates during late stage team fights.

迅捷斥候 is a somewhat poor counter to 赏金猎人. You will do well by focussing your gameplay on increasing your gold income and taking out objectives. If you are able to 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 early game and mid / late game phases of League of Legends, you should continue reading to gather a few extra tricks and insights into this matchup. If you mind the build and suggestions displayed here, you will grow your win rate by a lot and be that much closer to League of Legends pro players.

迅捷斥候 usually gets a similar amount of CS relative to 赏金猎人. Champions who typically don't get many minion kills often don't need 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 large amounts of CS, such as hyper-carries, typically need a lot of items to be effective. In either situation, try to exceed the numbers reported here to do well.

The most crucial items to use in your 迅捷斥候 versus 赏金猎人 build consist of 灭世者的死亡之帽, 扎兹沙克的溃口, and 影焰. When 迅捷斥候 included at least these three items in his build, he did much better vs 赏金猎人 than with many other typical item sets. In fact, 迅捷斥候 had an average winrate of 49.2% when playing against 赏金猎人 with these items in his kit.

To have the greatest probability of beating 赏金猎人 as 迅捷斥候, 迅捷斥候 players should equip the 黑暗收割, 恶意中伤, 眼球收集器, 终极猎人, 法力流系带, and 焦灼 runes from the 主宰 and 巫术 rune sets. Of all the runes players chose for 迅捷斥候 vs 赏金猎人 battles, this set of runes resulted in the highest win rate. Notably, these runes averaged a 49.2% winrate overall.

By default, tips, stats, and builds on how to beat 赏金猎人 as 迅捷斥候 are presented for all ranked divisions combined. If you want to narrow the statistics and builds to an individual division, you can use the selection menu at the top of this page.