- 用强权至上来削弱强大的敌方坦克或以此让你的队伍集中火力。
- 特朗德尔擅长在冰封领域内战斗。试着把敌人引到此区域内。
- 利齿撕咬能够很好地降低敌人的物理伤害,试着将此技能用于敌方的物理输出英雄。
- 菲兹的技能伤害会受到法术强度的加成——在面对高爆发队伍的威胁时,可以考虑购买【中娅沙漏】或【女妖面纱】——并且如果你有信心不靠生命值加成提供的生存能力的话,可以选择【灭世者的死亡之帽】或【巫妖之祸】。
- 菲兹在移动时能无视单位的碰撞体积,可以跨过小兵直取敌方英雄,并用你的【W海石三叉戟】的被动效果戳他——然后在几秒后开启主动效果继续戳。
- 菲兹的终极技能,【R巨鲨强袭】,能够朝着一名敌人施放,或者朝着敌人即将走过的区域施放。
The 巨魔之王 潮汐海灵 synergy stats shown here demonstrate the areas of his gameplay that do better (or worse) when paired with 潮汐海灵, compared to his overall stats. Significant differences are areas of focus that highlight how his gameplay changes when paired with this other champion.
Overall, 巨魔之王 sees a large worsening in his KDA (ratio of kills and assists to deaths) when paired with 潮汐海灵. His KDA worsened from NaN to NaN. This decrease shows that 潮汐海灵 helps 巨魔之王 perform worse in competitive League of Legends matches. Yet, the small difference shows that this performance change is not very impactful.
When 巨魔之王 is an ally to 潮汐海灵, he observes a small increase in his full damage dealt. This difference could demonstrate that 潮汐海灵 helps provide cover for him to dish out more damage or that his presence on the team also helps increase the match's duration. Similarly, when 巨魔之王 is played together with 潮汐海灵 on the same team, he usually scores many fewer killing sprees than when he plays without 潮汐海灵. This is contrasting evidence that he is worse when playing alongside 潮汐海灵.
Moreover, when 巨魔之王 plays with 潮汐海灵 on the same team, he typically takes a little less damage than when he plays alone. Receiving not as much damage may indicate that 潮汐海灵 does a decent job of covering 巨魔之王 during teamfights.
There is no universally accepted best ally for 巨魔之王 that will always be his ideal ally. However, 潮汐海灵 is a superb companion for 巨魔之王. By locking into the same team as 巨魔之王, he improves their win rate by 3.6% to 56.3%. This clearly indicates that there is a strong strategic relationship between 巨魔之王 and 潮汐海灵 that results in them performing stronger together than alone.
潮汐海灵 has a greater difficulty than 巨魔之王. That means you should be very careful when finding 潮汐海灵 comrades to go into battle on the same side as, as they will require a greater level of skill to do well with you.
When playing on the same side, 巨魔之王 players should see an overall large increase in your team’s capacity to destroy wih physical damage. Combined, these champions can provide a great amount of sustained physical damage.
Conversely, by bringing 巨魔之王 and 潮汐海灵 together, you may not be granting your other allies a great deal of utility. Make sure to have other champions on your team that nullifies this relative disparity in their abilities.
Regardless of your 潮汐海灵 ally's ability, you should focus on increasing your gold income, staying alive by avoiding foolish fights, and taking down objectives. If you follow these simple suggestions, you will do well, regardless.
If you would like to learn all of the intricacies of 巨魔之王 to synergize with 潮汐海灵 during both the laning and mid / late game phases of League of Legends games, you should continue reading to learn a few extra lessons on this champion pairing. If you listen to the build and tips displayed here, you will increase your win rate by a lot.
The top items to focus on in your 巨魔之王 and 潮汐海灵 synergy build include 振奋盔甲, 荆棘之甲, and 巨型九头蛇. When 巨魔之王 included at least these three pieces in his build, he performed a lot better as an ally of 潮汐海灵 than with most other commonly used builds. In fact, 巨魔之王 boasted an average win rate of 56.3% helping carry 潮汐海灵 with this build.
To have the greatest probability of vanquishing your oponents, you should take the 致命节奏, 凯旋, 传说:欢欣, 致命一击, 行近速率, and 神奇之鞋 runes from the 精密 and 启迪 rune sets. Of all the rune builds that we analyzed for 巨魔之王 and 潮汐海灵 pairings, this mix of runes yielded the top win rate. Notably, these runes gave a 56.3% win rate overall.
By default, tips, stats, and builds on how to synergize 潮汐海灵 with 巨魔之王 are given for all skill levels, merged. To scope the stats and builds to a distinct player tier, you can use the selection menu earlier in the counter matchup guide.