Враг, оглушенный Поражающей сферой, легко может оказаться в центре Ока разрушения.
Попасть во врагов Магическим разрядом проще, когда они движутся по направлению к вам или от вас, а не вбок.
Око разрушения может помочь попасть по цели Магическим разрядом, замедлив ее.
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 very large drop in his KDA (ratio of kills and assists to deaths) when paired with Юми. His KDA went down from NaN to NaN. This negative change shows that Юми helps Зерат perform worse in competitive League rounds. Yet, the small difference demonstrates that this performance change is not very impactful.
When Зерат plays on the same team as Юми, he gets a small decrease in his total damage output. This difference could indicate that Юми doesn't help cover for him to deal more damage or that her allyship also helps increase the game's duration. Similarly, when Зерат is played with Юми on the same side, he usually scores many fewer killing sprees than when he plays on his own. This is contrasting evidence that he is worse when playing alongside Юми.
Additionally, when Зерат plays with Юми on the same team, he often receives a little less damage than when he plays alone. Taking not as much damage may mean that Юми does a decent job of protecting Зерат during teamfights.
There is no one best companion for Зерат that will no matter what be his ideal synergy. Yet, Юми is a terrible companion for Зерат. By being on the same side as Зерат, she drops their win rate by -6.0% to 44.6%. This clearly indicates that there is a terrible synergy between Зерат and Юми that results in them performing worse together than alone.
Юми has a much lower diffuclty than Зерат. That means you don't need to be cautious when finding Юми allies to play with, as they will require a much lower level of skill to be able to cooperate well with you.
Playing cooperatively, you should expect to observe an overall large increase in your team’s capacity to deal magical damage. When paired, these champions can deal quite a lot of AP type damage.
Conversely, by bringing Зерат and Юми together, you will not be giving your side much cover. Make sure to have other champions on your team that fills this hole in this pairing's kit.
Regardless of your Юми ally's skill level, you need to focus on increasing your income, outlasting your enemies, and taking down objectives. If you heed this simple advice, you will do well anyway.
To truly master Зерат in order to pair well with Юми during both the laning and mid / late game phases of League of Legends rounds, you should keep reading to gather additional tips and tricks for this champion pairing. If you pay attention to the build and stats presented here, you will increase your win rate by a lot.
The top finished items to have in your Зерат and Юми synergy build consist of Смертельная шляпа Рабадона, Хекстековый прицел, and Помощник Людена. When Зерат bought at least these three pieces in his build, he did significantly better when paired up with Юми than with many other typical builds. In fact, Зерат boasted an average winrate of 44.6% when synergizing his build and playstyle to Юми with this build.
To have the greatest probability of coming out on top against your oponents, Зерат players should take the Удар на опережение, Магическая обувь, Доставка печенья, Космическое знание, Поток маны, and Ожог runes from the Вдохновение and Колдовство rune sets. Out of all the rune builds players used for Зерат and Юми pairings, this sequence of runes resulted in the best win rate. Moreover, these runes gave a 44.6% winrate overall.
By default, tips, statistics, and builds on how to synergize Юми with Зерат are presented for all skill levels combined. If you would like to scope the stats and builds to a particular player tier, you can use the selection menu located earlier on the page.