Background Image
如何赢得海洋之灾与迅捷斥候的对抗赛海洋之灾 is in the a tier of champions

海洋之灾 vs 迅捷斥候

如何在LoL中以海洋之灾的身份击败迅捷斥候海洋之灾 is in the a tier of champions
Fighter
MarksmanAssassin

如何击败迅捷斥候成为海洋之灾

based on 4,493 海洋之灾 vs 迅捷斥候 matchups
胜率
45.8 %
kda
2.1
受欢迎度
8.1 %

How We Analyze LoL Champion Counters

We generate our counter stats from the millions of recently ranked LoL games that we review every week. Our guide on how to beat 迅捷斥候 as 海洋之灾 resulted from an analysis of 4493 ranked matches where both champs engaged one another. This particular champion matchup is relatively uncommon. 海洋之灾 fights 迅捷斥候 in only 8.1% of his games.

海洋之灾 vs 迅捷斥候 Matchup Summary

Unfortunately, 海洋之灾 has done a terrible job of countering 迅捷斥候. On average, he wins a lowly 45.8% of the time the champs clash against each other in. In 海洋之灾 versus 迅捷斥候 rounds, 海洋之灾’s team is 0.0% more expected to earn first blood, implying that he most likely will get first blood against 迅捷斥候.

counterTitle

物品

第一项

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

下一个项目

5分钟
灵巧披风耀光

Core 海洋之灾 Items

22分钟
多米尼克领主的致意幽梦之灵纳沃利迅刃

可选项目

朔极之矛兰德里的折磨饮血剑狂妄

Summoner Spells

summonerflash summoner spell D
summonerteleport summoner spell F

技能顺序

为海洋之灾提升等级的第一个技能q
>
为海洋之灾提供的第二种能力,以提高水平e
>
海洋之灾 最大化的最后一项技能w

符文

启迪先攻神奇之鞋未来市场星界洞悉
主宰血之滋味寻宝猎人
Adaptive ForceAdaptive ForceMagic Resist
海洋之灾's passive ability p
海洋之灾's q ability q
海洋之灾's w ability w
海洋之灾's e ability e
海洋之灾's ultimate ability r
1
E
2
Q
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
45.8 %
VS
winRate
54.2 %
迅捷斥候 Image
6.6
< kills >
5.5
6.2
< deaths >
6.5
6.4
< assists >
7
1.52
< killingSprees >
1.25
201
< cs >
136
0.11
< dragons >
0.23
0.44
< inhibitors >
0.47
16,189
< physicalDamage >
2,463
3,987
< magicDamage >
23,456
4,004
< trueDamage >
1,715
24,181
< damageDealt >
27,635
28,744
< damageTaken >
22,946
14,261
< goldEarned >
11,696
2.08
< towers >
1.93
0.04
< barons >
0.06
7,984
< heal >
3,222
16,466
< xp >
14,884
16
< visionScore >
29
7
< wardsPlaced >
12
311
< ccTime >
508

How to Counter 迅捷斥候 with 海洋之灾 in LoL

The stat comparisons provided here highlight several significant 海洋之灾 versus 迅捷斥候 counter statistics that may help you distinguish the differences and similarities between the two. 海洋之灾’s KDA ratio ([kills + assists] / deaths) of NaN is greater than 迅捷斥候’s KDA ratio of NaN, showing that 海洋之灾 may be more central to his team's team fighting capability than 迅捷斥候..

海洋之灾 normally has a similar longest killing spree as his enemy does. Typically, he takes more damage than 迅捷斥候. This typically indicates different amounts of tankyness; however, it can also show that the one champ has less agility and thus is not able to flee from further damage when poked or engaged.

championDifferences.title

伤害数据

海洋之灾
迅捷斥候
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

海洋之灾
迅捷斥候

championDifferences.whoIsBetter

Both LoL champions are great champions. Both champs have their strengths, weaknesses, and counters. In League's current meta, 海洋之灾 usually loses when taking on 迅捷斥候, with a 45.8% win rate. Therefore, 海洋之灾 makes a bad counter for 迅捷斥候.

While 海洋之灾 does have a much lower win rate than 迅捷斥候, when they face off with one another, 海洋之灾 also has a much greater difficulty level that makes him a more challenging character to develop with. You may get destroyed when picking 海洋之灾 into 迅捷斥候as his relative depth means that you may not be able to unleash his full potential without a lot of practice beforehand.

Additionally, 海洋之灾 also has almost no amount of CC and other utility, a similar amount to 迅捷斥候. This makes her just as valuable during team fights, 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 champion with a much lower win rate, more champion depth, and a similar amount of utility to help out your teammates during teamfights.

海洋之灾 is a trash counter to 迅捷斥候. Focus your tactics on maximizing your gold and cs and clearing objectives. If you can do that, you should do very well as 海洋之灾 against 迅捷斥候.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

To learn all of the intricacies of 海洋之灾 to counter 迅捷斥候 during both the lane and mid / late game phases of League of Legends, you should continue reading to gather a few extra lessons on this matchup. If you pay attention to the build and tips shown above, you will grow your win rate significantly and be closer to League of Legends pro players.

海洋之灾 on average racks up a similar amount of CS relative to 迅捷斥候. Champs who on average don't acquire much CS typically don't require much CS to be valuable teammates, such as supports. They are capable of scaling well off of their abilities and first items alone. Yet, champs with a lot of CS, such as hyper-carries, often have to have a lot of items to be effective. In either situation, try to exceed the numbers displayed on this page to do well.

The most important items to prioritize in your 海洋之灾 versus 迅捷斥候 build include 多米尼克领主的致意, 幽梦之灵, and 纳沃利迅刃. When 海洋之灾 combined at least these three items in his build, he did a lot better against 迅捷斥候 than with many other common item sets. In fact, 海洋之灾 boasted an average winrate of 45.8% when playing against 迅捷斥候 with this counter build.

To have the greatest probability of vanquishing 迅捷斥候 as 海洋之灾, you should use the 先攻, 神奇之鞋, 未来市场, 星界洞悉, 血之滋味, and 寻宝猎人 runes from the 启迪 and 主宰 rune sets. Out of all the rune combinations that we analyzed for 海洋之灾 vs 迅捷斥候 face-offs, this order of runes yielded the highest win rate. Notably, these runes gave a 45.8% winrate overall.

By default, tips, statistics, and builds on how to beat 迅捷斥候 as 海洋之灾 are presented for all skill levels, merged. If you want to filter the stats and builds to a particular division, you should use the selection menu located above.