Background Image
如何赢得海洋之灾与暮光之眼的对抗赛海洋之灾 is in the a tier of champions

海洋之灾 vs 暮光之眼

如何在LoL中以海洋之灾的身份击败暮光之眼海洋之灾 is in the a tier of champions
Fighter
Tank

如何击败暮光之眼成为海洋之灾

based on 949 海洋之灾 vs 暮光之眼 matchups
胜率
49.2 %
kda
1.98
受欢迎度
1.7 %

How We Analyze LoL Champion Counters

We summarize our counter statistics from the millions of recently ranked League of Legends rounds that we analyze each week. This guide on how to beat 暮光之眼 as 海洋之灾 came out of an evaluation of 949 ranked rounds where both champs faced one another. This champ pairing is relatively rare. 海洋之灾 has to counter 暮光之眼 in only 1.7% of his games.

海洋之灾 vs 暮光之眼 Matchup Summary

Unfortunately, 海洋之灾 does a poor job of countering 暮光之眼. On average, he wins a acceptable 49.2% of matches the champs oppose one another in. In 海洋之灾 against 暮光之眼 games, 海洋之灾’s side is 0.1% less likely to obtain first blood, implying that he most likely won't get first blood versus 暮光之眼.

counterTitle

物品

第一项

期望时间
长剑复用型药水

下一个项目

5分钟
长剑考尔菲德的战锤

Core 海洋之灾 Items

22分钟
多米尼克领主的致意纳沃利迅刃收集者

可选项目

凡性的提醒饮血剑无尽之刃夺萃之镰

Summoner Spells

summonerflash summoner spell D
summonerteleport 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
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 暮光之眼

- 准备好躲避慎的嘲讽,并在他失误时予以反击。

- 一旦慎到达了6级,就要留意他用全图传送终极技能快速扭转局部战斗的局势。

海洋之灾 vs 暮光之眼 Counter Stats

海洋之灾 Image
winRate
49.2 %
VS
winRate
50.8 %
暮光之眼 Image
6
< kills >
4.2
6.2
< deaths >
5.1
6.3
< assists >
10.7
1.35
< killingSprees >
0.96
196
< cs >
124
0.11
< dragons >
0.14
0.45
< inhibitors >
0.46
17,643
< physicalDamage >
7,992
3,907
< magicDamage >
6,259
4,829
< trueDamage >
1,084
26,380
< damageDealt >
15,335
25,906
< damageTaken >
31,449
14,117
< goldEarned >
10,357
2.39
< towers >
1.73
0.06
< barons >
0.02
6,866
< heal >
4,132
15,586
< xp >
14,184
17
< visionScore >
23
9
< wardsPlaced >
11
319
< ccTime >
340

How to Counter 暮光之眼 with 海洋之灾 in LoL

The stats provided here clarify some important 海洋之灾 versus 暮光之眼 counter stats that can help you understand the differences between the pair. 海洋之灾’s KDA ratio ([kills + assists] / deaths) of NaN is greater than 暮光之眼’s ratio of NaN, indicating that 海洋之灾 may be more central to his team's team fighting effectiveness than 暮光之眼..

海洋之灾 usually has a slightly larger longest kill spree than his matchup does. On average, he takes less damage than 暮光之眼. This often reflects differing health capacities, yet it can also hint that the one champ has less agility and thus is unable to escape additional damage when engaged or poked.

championDifferences.title

伤害数据

海洋之灾
暮光之眼
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

海洋之灾
暮光之眼

championDifferences.whoIsBetter

Both LoL champions are great champions. Both have their pros and cons. In League's current meta, 海洋之灾 usually fairs equally well when trying to fight 暮光之眼, with a 49.2% win rate. Therefore, 海洋之灾 makes an ok counter for 暮光之眼.

While 海洋之灾 does have a lower winrate compared to 暮光之眼, when facing one another, 海洋之灾 also has a much greater difficulty level that makes him a more challenging champion to develop with. You still need to be cautious when picking 海洋之灾 into 暮光之眼as his relative depth means you may not be able to unleash his full potential without a lot of practice beforehand.

Moreover, 海洋之灾 also has almost no amount of utility and CC, a similar amount to 暮光之眼. This makes her just as valuable during team fights, especially when facing champions with a lot of burst damage.

While there is not a single best champion overall in League of Legends, in 海洋之灾 vs 暮光之眼 matchups, 暮光之眼 is the better champion with a similar win rate, more champion depth, and a similar amount of utility to help out your allies during late stage team fights.

海洋之灾 is a somewhat poor counter for 暮光之眼. Focus your gameplay on increasing your gold and cs and destroying objectives. If you can do that, you should do very well as 海洋之灾 against 暮光之眼.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

If you would like to learn all of the intricacies of 海洋之灾 in order 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 listen to the build and suggestions presented above, you should increase your win rate significantly and be closer to League of Legends pro players.

海洋之灾 on average picks up more CS as 暮光之眼. Champions who typically don't acquire many minion kills usualy don't require much CS to be valuable teammates, such as support champions. They are capable of scaling properly off of their skills, stats, and first items alone. Yet, champions with a lot of CS, such as hyper-carries, often need several high cost items to be effective. In either case, try to do better than the numbers shown on this page to do well.

The top items to focus on in your 海洋之灾 versus 暮光之眼 build consist of 多米尼克领主的致意, 纳沃利迅刃, and 收集者. When 海洋之灾 bought at least these three items in his build, he did significantly better against 暮光之眼 than with many other common item sets. In fact, 海洋之灾 boasted an average winrate of 49.2% when countering 暮光之眼 with these items in his kit.

To have the greatest chance of beating 暮光之眼 as 海洋之灾, 海洋之灾 players should equip the 先攻, 神奇之鞋, 饼干配送, 星界洞悉, 骸骨镀层, and 过度生长 runes from the 启迪 and 坚决 rune sets. Of all the rune combinations players picked for 海洋之灾 vs 暮光之眼 battles, this set of runes resulted in the greatest win rate. Moreover, these runes averaged a 49.2% winrate overall.

By default, tips, statistics, and builds on how to beat 暮光之眼 as 海洋之灾 are given for every ranked division. To filter the statistics and builds to a specific division, you can use the selection menu located at the top of this page.