라칸은 이동 속도가 증가하면 도약 속도도 증가합니다. 적을 깜짝 놀라게 해 보세요.
위험해 보이는 상황도 충분히 즐길 수 있는 게 라칸입니다.
라칸은 모든 스킬을 잘 활용하려면 근처에 아군이 함께 있어야 합니다.
스킬을 시전하는 사이사이에 기본 공격을 끼워 넣는 방식으로 질풍격 효과를 볼 수 있습니다. 적에게 줄 수 있는 피해가 더욱 올라가는 반면 기력 소모량은 더욱 줄일 수 있습니다.
용의 분노를 쓰기 전에 음파를 사용하면 공명의 일격으로 대상을 쫓아갈 수 있습니다.
자신에게 방호를 시전하고 강철의 의지를 사용하면 정글에 있는 중립 몬스터를 쉽게 해치울 수 있습니다.
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 negative change shows that 크산테 helps 라칸 perform not as well in competitive League of Legends rounds. Yet, the small difference demonstrates that this performance change is only marginal.
When 라칸 plays on the same team as 크산테, he sees a little decrease in his complete damage dealt. This may signal that 크산테 does not help protection for him to dish out more damage or that their presence on the team also helps extend the round's duration. Similarly, when 라칸 is played alongside 크산테 on the same side, he usually scores many fewer killing sprees compared to when he plays alone. This is contrasting evidence that he is worse when playing synergisticly with 크산테.
Additionally, when 라칸 plays with 크산테 on the same side, he usually receives a little less damage than when he fights alone. Taking not as much damage may mean that 크산테 does a decent job of protecting 라칸 during teamfights.
There is no universally accepted best synergy for 라칸 that will 100% of the time be his ideal teammate. Yet, overall, 크산테 is a terrible companion for 라칸. By locking into the same team as 라칸, they decreases their win rate by -5.3% to 45.3%. This signals that there is a very bad strategic relationship between 라칸 and 크산테 that allows them to perform worse together than without each other.
크산테 has a much greater difficulty compared to 라칸. That means 라칸 players should be cautious when arranging 크산테 allies to play with, as they will require a much higher level of skill to do well with you.
Working alongside, 라칸 players will likely observe an overall large increase in your team’s capability to deal magical damage. Together, these champions can deal quite a lot of AP type damage.
Conversely, by bringing 라칸 and 크산테 together, you may not be giving your side very much anti-tank damage dealing potential. Make sure to pick other champions on your team that offsets this disparity in this pairing's capabilities.
Regardless of your 크산테 ally's skill level, you should focus on maximizing your gold income, outlasting your enemies, and taking down objectives. If you follow these simple suggestions, you will do well, regardless.
To truly master 라칸 to work well with 크산테 during both the early game and mid / late game phases of League rounds, you should continue reading to gather a few extra tips and tricks for this champion pairing. If you mind the build and tips shown here, you will grow your win rate by a lot.
The most crucial items to focus on in your 라칸 and 크산테 synergy build include 개척자, 기사의 맹세, and 태양의 썰매. When 라칸 bought at least these three great items in his build, he performed much better when paired up with 크산테 than with most other typical builds. In fact, 라칸 had an average winrate of 45.3% when synergizing his build and playstyle to 크산테 with these items in his kit.
To have the greatest chance of vanquishing your oponents, 라칸 players should take the 수호자, 생명의 샘, 뼈 방패, 불굴의 의지, 궁극의 사냥꾼, and 좀비 와드 runes from the 결의 and 지배 rune sets. Out of all the rune combinations we have analyed for this team composition, this composite of runes yielded the highest win rate. Notably, these runes gave a 45.3% win rate overall.
By default, tips, statistics, and builds on how to synergize 크산테 with 라칸 are presented for all skill levels, merged. If you would like to scope the statistics and builds to a particular rank, you should use the selection menu at the top of this page.