- 菲兹的技能伤害会受到法术强度的加成——在面对高爆发队伍的威胁时,可以考虑购买【中娅沙漏】或【女妖面纱】——并且如果你有信心不靠生命值加成提供的生存能力的话,可以选择【灭世者的死亡之帽】或【巫妖之祸】。
- 菲兹在移动时能无视单位的碰撞体积,可以跨过小兵直取敌方英雄,并用你的【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 went down from NaN to NaN. This decrease shows that 九尾妖狐 helps 潮汐海灵 perform not as well in competitive League rounds. Yet, the small difference proves that this performance change is only marginal.
When 潮汐海灵 is paired with 九尾妖狐, he observes a barely noticable drop in his total damage dealt. This difference may signal that 九尾妖狐 does not provide cover for him to deal more damage or that her participation also helps extend the round's duration. Similarly, when 潮汐海灵 is played alongside 九尾妖狐 on the same team, he usually scores many fewer killing sprees than when he plays on his own. This is contrasting evidence that he is worse when playing synergisticly with 九尾妖狐.
Moreover, when 潮汐海灵 plays with 九尾妖狐 on the same side, he often takes more damage than when he plays alone. Getting dealt more damage could mean that 九尾妖狐 does a poor job of covering 潮汐海灵 in teamfights.
There is no top synergy for 潮汐海灵 that will always be his ideal synergy. Yet, 九尾妖狐 is a very typical companion for 潮汐海灵. By playing on the same side as 潮汐海灵, she lowers their win rate by -0.3% to 52.3%. This demonstrates that there is only a small synergy between 潮汐海灵 and 九尾妖狐 that results in them performing not as well together than without each other.
九尾妖狐 has a lower difficulty than 潮汐海灵. That means 潮汐海灵 players don't need to be cautious when arranging 九尾妖狐 allies to fight alongside, as they will need a lower level of skill to be able to cooperate well with you.
Playing alongside, you should expect to observe an overall large increase in your team’s capacity to deal magic damage. Together, these champs are able to dish out a surprising amount of magic type damage.
Conversely, by aligning 潮汐海灵 and 九尾妖狐 together, you probably will not be providing your other allies very much crowd control. Plan to include other champions on your team that fills this gap in their capabilities.
Regardless of the ability of your 九尾妖狐 ally, you need to focus on increasing your gold income, outlasting your enemies, and taking down objectives. If you follow these simple suggestions, you should do well, regardless.
To truly master 潮汐海灵 in order to synergize with 九尾妖狐 during both the lane and mid / late game phases of LoL matches, you should continue reading to pick up some more tips and tricks for this champion pairing. If you listen to the build and tips displayed here, you will increase your win rate significantly.
The top finished items to build first in your 潮汐海灵 and 九尾妖狐 synergy build consist of 灭世者的死亡之帽, 巫妖之祸, and 风暴狂涌. When 潮汐海灵 bought at least these three finished items in his build, he did significantly better when fighting alongside 九尾妖狐 than with most other commonly used item sets. In fact, 潮汐海灵 had an average winrate of 52.3% when playing alongside 九尾妖狐 with this build.
To have the best likelihood of coming out on top against your oponents, you should take the 电刑, 猛然冲击, 眼球收集器, 寻宝猎人, 致命一击, and 凯旋 runes from the 主宰 and 精密 rune sets. Out of all the rune combinations we have analyed for this team composition, this sequence of runes resulted in the highest win rate. Notably, these runes gave a 52.3% win rate overall.
By default, tips, stats, and builds on how to team up 九尾妖狐 with 潮汐海灵 are presented for all ranked divisions. If you want to scope the statistics and builds to a particular skill level, you may use the selection menu earlier on the page.