시간 도약은 에코의 다른 스킬과 연계하기 좋습니다. 이 스킬을 활용해 시간의 톱니바퀴를 두 번 적중시키거나 평행 시간 교차를 터뜨리기 좋은 위치를 잡으세요.
시공간 붕괴는 탈출기로도 좋지만, 공격적으로도 활용할 수 있는 강력한 스킬입니다. 이 스킬의 피해량을 잘 활용하세요.
Z 드라이브 공진은 가능한 한 적 챔피언에게 발동시키세요. 이동 속도 상승 효과로 인해 탈출이 쉬워집니다.
아무무는 팀원들에 대한 의존도가 높습니다. 믿을 수 있는 아군과 함께 공격로에 나가십시오.
절망은 다른 방어 담당 챔피언을 상대로 매우 유용합니다. 체력이 가장 높은 적 가까이에서 싸우십시오.
재사용 대기시간 감소 효과는 아무무에게 매력적이지만 이를 아이템으로 모두 얻기에는 무리가 따릅니다. 가능할 때마다 푸른 파수꾼을 처치하여 공짜 재사용 대기시간 감소 효과를 얻으십시오.
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 decrease shows that 아무무 helps 에코 perform worse in competitive League of Legends matches. Yet, the small difference proves that this performance change is not very impactful.
When 에코 is an ally to 아무무, he sees a little increase in his full damage dealt. This difference could demonstrate that 아무무 helps provide protection for him to dish out more damage or that his allyship also helps increase the game's duration. Similarly, when 에코 is played with 아무무 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 receives less damage than when he plays alone. Receiving not as much damage may mean that 아무무 does a decent job of protecting 에코 during team fights.
There is no top champion pairing for 에코 that will no matter what be his ideal synergy. However, 아무무 is a decent teammate for 에코. By playing on the same side as 에코, he increases their win rate by 2.7% to 53.1%. This clearly indicates that there is pretty good bond between 에코 and 아무무 that allows them to perform stronger together than alone.
아무무 has a much lower diffuclty than 에코. That means you don't need to be careful when arranging 아무무 teammates to fight alongside, as they will have to have a much lower level of skill to work well with you.
Working on the same side, 에코 players should expect to observe an overall large increase in your team’s ability to to do a lot of AP damage. Together, these two can deal quite a lot of AP type damage.
Conversely, by pairing 에코 and 아무무 together, you will not be giving your team enough anti-tank damage dealing potential. Make sure to pick other champs on your team that helps cover this disparity in this pairing's playstyle.
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 do this, 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, you should keep reading to pick up a few extra tips and tricks for this champion pairing. If you mind the build and suggestions displayed here, you will grow your win rate significantly.
The most important items to use in your 에코 and 아무무 synergy build include 마법공학 로켓 벨트, 라바돈의 죽음모자, and 리치베인. When 에코 included at least these three pieces in his build, he performed much better when paired up with 아무무 than with many other commonly used builds. In fact, 에코 boasted an average win rate of 53.1% when playing alongside 아무무 with this build.
To have the best chance of coming out on top against your oponents, you should equip the 감전, 돌발 일격, 사냥의 증표, 보물 사냥꾼, 절대 집중, and 폭풍의 결집 runes from the 지배 and 마법 rune sets. Of all the rune combinations players chose for this champion pairing, this order of runes resulted in the top win rate. Moreover, these runes provided a 53.1% win rate overall.
By default, tips, statistics, and builds on how to pair 아무무 with 에코 are displayed for all ranked divisions combined. If you would like to narrow the stats and builds to a specific rank, you can use the selection menu at the top of this page.