어떤 대상을 사냥할지 신중하게 선택하세요. 게임이 진행될수록 사냥에 많이 성공해야만 승리를 기약할 수 있습니다.
대규모 교전 시엔 선두에서 들어가지 마세요. 아군이 공격을 개시하길 기다리는 편이 좋습니다.
정글 사냥 시 공격하는 사이사이 움직이면 몬스터의 공격을 피할 수 있을 뿐더러 늑대의 광기 스킬로 인한 치유 효과가 활성화됩니다.
아펠리오스의 다섯 가지 무기는 각각 장점을 지니고 있습니다. 상황에 맞게 무기를 활용해 보세요.
The 킨드레드 아펠리오스 synergy stats shown here demonstrate the areas of their gameplay that do better (or worse) when paired with 아펠리오스, compared to their overall stats. Significant differences are areas of focus that highlight how their gameplay changes when paired with this other champion.
Overall, 킨드레드 sees a large worsening in their KDA (ratio of kills and assists to deaths) when paired with 아펠리오스. His KDA decreased from NaN to NaN. This fall shows that 아펠리오스 helps 킨드레드 perform poorer in competitive League matches. Yet, the small difference demonstrates that this performance change is not very impactful.
When 킨드레드 is paired with 아펠리오스, they observes a barely noticable drop in their complete damage dealt. This could signal that 아펠리오스 does not support by providing protection for them to deal more damage or that his presence also helps increase the round's duration. Similarly, when 킨드레드 is played alongside 아펠리오스 on the same side, he usually scores many fewer killing sprees compared to when they plays without 아펠리오스. This is contrasting evidence that they is worse when playing synergisticly with 아펠리오스.
Moreover, when 킨드레드 plays with 아펠리오스 on the same side, they typically takes a little less damage than when they plays alone. Receiving 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 their top teammate. Yet, 아펠리오스 is a very bad companion for 킨드레드. By being on the same side as 킨드레드, he drops their win rate by -3.3% to 45.0%. This demonstrates that there is an easy to overcome and exploit synergy between 킨드레드 and 아펠리오스 that allows them to perform worse together than alone.
아펠리오스 has a much greater difficulty compared to 킨드레드. That means you must be careful when arranging 아펠리오스 allies to go into battle on the same side as, as they will need a much greater level of skill to do well with you.
Working cooperatively, 킨드레드 players will likely witness an overall large increase in your team’s capacity to destroy wih physical damage. When paired, these champions should be able to take down targets with auto-attacks and other AD damage abilities.
Conversely, by grouping 킨드레드 and 아펠리오스 together, you may not be giving your other allies a lot of magic damage. We recommend you include other champs on your team that fills this disparity in their potential.
Regardless of the ability of your 아펠리오스 teammate, you need to focus on maximizing your gold income, staying alive by avoiding foolish fights, and clearing objectives. If you follow these simple suggestions, you will do well, regardless.
If you would like to truly master 킨드레드 to work well with 아펠리오스 during both the early game and mid / late game phases of League of Legends rounds, you should continue reading to pick up additional lessons on this champion pairing. If you listen to the build and tips presented here, you will increase your win rate significantly.
The top items to get in your 킨드레드 and 아펠리오스 synergy build include 삼위일체, 마법사의 최후, and 크라켄 학살자. When 킨드레드 included at least these three pieces in their build, they did much better as an ally of 아펠리오스 than with most other commonly used builds. In fact, 킨드레드 had an average winrate of 45.0% helping carry 아펠리오스 with this build.
To have the best probability of beating your oponents, you should equip the 정복자, 승전보, 전설: 민첩함, 최후의 일격, 돌발 일격, and 보물 사냥꾼 runes from the 정밀 and 지배 rune sets. Of all the rune combinations we have analyed for this champion pairing, this sequence of runes resulted in the greatest win rate. Moreover, these runes provided a 45.0% winrate overall.
By default, tips, statistics, and builds on how to pair 아펠리오스 with 킨드레드 are given for all skill levels, merged. If you would like to scope the statistics and builds to an individual division, you may use the selection menu at the top of this page.