Background Image
如何赢得深渊巨口与迅捷斥候的对抗赛深渊巨口 is in the b tier of champions

深渊巨口 vs 迅捷斥候

如何在LoL中以深渊巨口的身份击败迅捷斥候深渊巨口 is in the a tier of champions
MarksmanMage
MarksmanAssassin

如何击败迅捷斥候成为深渊巨口

based on 2,390 深渊巨口 vs 迅捷斥候 matchups
胜率
47.9 %
kda
2.06
受欢迎度
8 %

How We Analyze LoL Champion Counters

We calculate our matchup stats from the millions of recently rated League of Legends matches that we analyze each and every week. This guide on how to beat 迅捷斥候 as 深渊巨口 came out of an examination of 2390 ranked matches where both champs clashed against one another. This pairing is relatively uncommon. 深渊巨口 is forced to battle against 迅捷斥候 in only 8.0% of his games.

深渊巨口 vs 迅捷斥候 Matchup Summary

Unfortunately, 深渊巨口 has done a poor job of countering 迅捷斥候. On average, he wins a lowly 47.9% of matches the champs battle one another in. In 深渊巨口 versus 迅捷斥候 games, 深渊巨口’s team is 0.0% more probable to get first blood, implying that he most likely will get first blood versus 迅捷斥候.

counterTitle

物品

第一项

期望时间
多兰之戒生命药水

下一个项目

5分钟
鞋子吸血鬼节杖

Core 深渊巨口 Items

22分钟
卢安娜的飓风破败王者之刃界弓

可选项目

兰德里的折磨瑞莱的冰晶节杖残疫智慧末刃

Summoner Spells

summonerflash summoner spell D
summonerheal summoner spell F

技能顺序

为深渊巨口提升等级的第一个技能w
>
为深渊巨口提供的第二种能力,以提高水平q
>
深渊巨口 最大化的最后一项技能e

符文

精密致命节奏凯旋传说:血统坚毅不倒
坚决调节过度生长
Attack SpeedAdaptive ForceHealth Scaling
深渊巨口's passive ability p
深渊巨口's q ability q
深渊巨口's w ability w
深渊巨口's e ability e
深渊巨口's ultimate ability r
1
W
2
E
3
Q
4
W
5
W
6
R
7
W
8
Q
9
W
10
Q
11
R
12
Q
13
Q
14
E
15
E
16
R

Guide to Countering 迅捷斥候 as 深渊巨口

Tips for Playing as 深渊巨口 against 迅捷斥候

- 用【来自艾卡西亚的惊喜】来对尽可能多的敌人造成伤害。

- 在【E虚空淤泥】的帮助下可以施放一个完美的【R活体大炮】。

- 克格莫使用【W生化弹幕】时,其射程比大多数英雄都远。

Advice to Win Against 迅捷斥候

- 提莫的毒性射击技能对被击中再退后的玩家同样有效,在你准备好反击之前要和提莫保持距离。

- 你可以用神谕透镜来安全地摧毁关键地区的蘑菇。

深渊巨口 vs 迅捷斥候 Counter Stats

深渊巨口 Image
winRate
47.9 %
VS
winRate
52.1 %
迅捷斥候 Image
7.7
< kills >
5.6
7.2
< deaths >
6.7
7.1
< assists >
7.4
1.83
< killingSprees >
1.26
170
< cs >
133
0.18
< dragons >
0.23
0.47
< inhibitors >
0.49
9,279
< physicalDamage >
2,635
13,558
< magicDamage >
23,551
2,896
< trueDamage >
1,798
25,734
< damageDealt >
27,984
23,516
< damageTaken >
22,770
12,718
< goldEarned >
11,637
2.13
< towers >
2
0.05
< barons >
0.07
5,740
< heal >
3,190
13,745
< xp >
14,772
19
< visionScore >
28
9
< wardsPlaced >
11
308
< ccTime >
513

How to Counter 迅捷斥候 with 深渊巨口 in LoL

The stats shown here feature some valuable 深渊巨口 versus 迅捷斥候 counter stats that may help you understand the differences between this pair of champions. For instance, 深渊巨口’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 capability than 迅捷斥候..

深渊巨口 usually has a slightly larger longest kill spree than his opponent does. On average, he takes a similar amount of damage to 迅捷斥候. This commonly reflects different amounts of tankyness, but it can also imply that the one champion has less mobility and thus is not able to escape further damage when poked or engaged.

championDifferences.title

伤害数据

深渊巨口
迅捷斥候
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

深渊巨口
迅捷斥候

championDifferences.whoIsBetter

Both League champions are great champions. Both have their strengths, weaknesses, and counters. In the game's current meta, 深渊巨口 usually loses when taking on 迅捷斥候, with a 47.9% win rate. As a result, 深渊巨口 makes a bad counter for 迅捷斥候.

While 深渊巨口 does have a lower winrate than 迅捷斥候, when they face off with one another, 深渊巨口 also has a greater learning curve that makes him a more challenging character to pick up and master. You should expect to face a difficult match when picking 深渊巨口 into 迅捷斥候.

Furthermore, 深渊巨口 also has almost no amount of utility and CC, a similar amount to 迅捷斥候. This makes her just as valuable during teamfights, especially when trying to counter champions with a ton of burst damage.

While there isn't a single best champion overall in League of Legends, in 深渊巨口 vs 迅捷斥候 matchups, 迅捷斥候 is the better champion with a lower win rate, similar champion depth, and a similar amount of utility to help out your allied champions during teamfights.

深渊巨口 is a bad counter to 迅捷斥候. Make sure you focus your strategy on keeping up your CS and destroying objectives. If you are able to do that, you should be able to stand on your own as 深渊巨口 against 迅捷斥候.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

To truly master 深渊巨口 in order to counter 迅捷斥候 during both the lane and mid / late game phases of League of Legends, you should continue reading to learn a few extra lessons on this matchup. If you pay attention to the build and tips presented above, you will grow your win rate significantly and be that much closer to League of Legends pro players.

深渊巨口 usually accumulates a similar amount of CS relative to 迅捷斥候. Champs who typically don't acquire much CS usualy don't require much CS to be effective, such as sup champs. These kinds of champions are able to scale well off of their abilities and first items alone. Yet, champions with a lot of CS, such as hyper-carries, usually require a lot of items to be effective. In either case, try to exceed the values shown on this page to do well.

The best items to prioritize in your 深渊巨口 versus 迅捷斥候 build include 卢安娜的飓风, 破败王者之刃, and 界弓. When 深渊巨口 combined at least these three pieces in his build, he performed much better countering 迅捷斥候 than with many other commonly used item sets. In fact, 深渊巨口 had an average win rate of 47.9% when playing against 迅捷斥候 with this counter build.

To have the greatest probability of vanquishing 迅捷斥候 as 深渊巨口, you should equip the 致命节奏, 凯旋, 传说:血统, 坚毅不倒, 调节, and 过度生长 runes from the 精密 and 坚决 rune sets. Out of all the rune combinations players chose for 深渊巨口 vs 迅捷斥候 counters, this blending of runes resulted in the greatest win rate. Notably, these runes provided a 47.9% winrate overall.

By default, tips, statistics, and builds on how to beat 迅捷斥候 as 深渊巨口 are given for all ranked divisions. To filter the statistics and builds to an individual player tier, you should use the selection menu earlier on the page.