Background Image
如何赢得海兽祭司与巨魔之王的对抗赛海兽祭司 is in the a tier of champions

海兽祭司 vs 巨魔之王

如何在LoL中以海兽祭司的身份击败巨魔之王海兽祭司 is in the s tier of champions
FighterTank
FighterTank

如何击败巨魔之王成为海兽祭司

based on 5,462 海兽祭司 vs 巨魔之王 matchups
胜率
45.8 %
kda
1.42
受欢迎度
7.7 %

How We Analyze LoL Champion Counters

We get our matchup statistics from the millions of recently rated League rounds that we analyze each and every week. This guide on how to beat 巨魔之王 as 海兽祭司 resulted from an evaluation of 5462 ranked games where both champions clashed against each other. This counter pairing is fairly uncommon. 海兽祭司 is forced to battle against 巨魔之王 in only 7.7% of her matches.

海兽祭司 vs 巨魔之王 Matchup Summary

Unfortunately, 海兽祭司 does a pathetic job of countering 巨魔之王. Typically, she wins a lowly 45.8% of games the champions clash against each other in. In 海兽祭司 vs 巨魔之王 games, 海兽祭司’s team is 0.1% less probable to obtain first blood. This implies that she most likely won't get first blood against 巨魔之王.

counterTitle

物品

第一项

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

下一个项目

5分钟
鞋子掘道钻头

Core 海兽祭司 Items

22分钟
斯特拉克的挑战护手三相之力焚天

可选项目

振奋盔甲死亡之舞朔极之矛黑色切割者

Summoner Spells

summonerflash summoner spell D
summonerdot summoner spell F

技能顺序

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

符文

坚决不灭之握爆破骸骨镀层过度生长
精密气定神闲坚毅不倒
Adaptive ForceAdaptive ForceHealth Scaling
海兽祭司'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
E
5
E
6
R
7
E
8
Q
9
E
10
Q
11
R
12
Q
13
Q
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
5.2
< kills >
5.8
6.6
< deaths >
6
4.2
< assists >
5.6
1.18
< killingSprees >
1.34
185
< cs >
139
0.05
< dragons >
0.47
0.5
< inhibitors >
0.76
24,277
< physicalDamage >
16,629
796
< magicDamage >
2,537
366
< trueDamage >
545
25,440
< damageDealt >
19,712
33,225
< damageTaken >
36,268
11,641
< goldEarned >
12,269
2.57
< towers >
3.23
0.02
< barons >
0.11
8,202
< heal >
17,113
14,940
< xp >
14,663
16
< visionScore >
17
8
< wardsPlaced >
7
438
< ccTime >
342

How to Counter 巨魔之王 with 海兽祭司 in LoL

The stats shown here feature several influential 海兽祭司 vs. 巨魔之王 counter statistics that may help you distinguish the distinctions between the pair. 海兽祭司’s KDA ratio ([kills + assists] / deaths) of NaN is greater than 巨魔之王’s ratio of NaN, demonstrating that 海兽祭司 may be more central to her team's team fighting capacity than 巨魔之王..

海兽祭司 normally has a similar longest kill spree as her foe does. Commonly, she takes less damage than 巨魔之王. This often reflects differing health capacities, yet it can also show that the champ with more HP has less agility and thus is unable to flee from additional harm when poked or engaged.

championDifferences.title

伤害数据

海兽祭司
巨魔之王
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

海兽祭司
巨魔之王

championDifferences.whoIsBetter

Both League champs are great. Both have their strengths, weaknesses, and counters. In the game's current meta, 海兽祭司 usually loses when playing against 巨魔之王, with a 45.8% win rate. Therefore, 海兽祭司 makes a poor counter for 巨魔之王.

While 海兽祭司 does have a much lower winrate than 巨魔之王, when they face off with one another, 海兽祭司 also has a lower learning curve that makes her a less difficult character to learn. You may get destroyed when picking 海兽祭司 into 巨魔之王.

Additionally, 海兽祭司 has almost no amount of utility and CC, a similar amount to 巨魔之王. This often makes her just as valuable during teamfights, 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 much lower win rate, less champion complexity, and a similar amount of utility to help out your teammates during late stage team fights.

海兽祭司 is a garbage counter to 巨魔之王. Make sure you focus your play on keeping up your CS and taking out objectives. If you are able to do that, you should do very well as 海兽祭司 against 巨魔之王.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

If you would like to truly master 海兽祭司 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 significantly and be that much closer to League of Legends pro players.

海兽祭司 most often accumulates a similar amount of CS as 巨魔之王. Champs who on average don't take many minion kills usualy don't need much CS to be effective, such as support champions. These kinds of champions are capable of scaling properly off of their skills, stats, and first items alone. Yet, champs with large amounts of CS, such as hyper-carries, often require a lot of items to be effective. In either case, try to do better than the numbers displayed on this page to do well.

The ideal items to focus on in your 海兽祭司 versus 巨魔之王 build include 斯特拉克的挑战护手, 三相之力, and 焚天. When 海兽祭司 combined at least these three items in her build, she did a lot better versus 巨魔之王 than with many other typical counter builds. In fact, 海兽祭司 boasted an average winrate of 45.8% when playing against 巨魔之王 with these items in her kit.

To have the greatest likelihood of beating 巨魔之王 as 海兽祭司, you should take the 不灭之握, 爆破, 骸骨镀层, 过度生长, 坚毅不倒, and 气定神闲 runes from the 坚决 and 精密 rune sets. Of all the rune sets players picked for 海兽祭司 vs 巨魔之王 matchups, this mixture of runes yielded the greatest win rate. Notably, these runes gave a 45.8% winrate overall.

By default, tips, stats, and builds on how to beat 巨魔之王 as 海兽祭司 are given for every ranked division. If you want to narrow the statistics and builds to a distinct player tier, you should use the selection menu at the top of this page.