라칸은 이동 속도가 증가하면 도약 속도도 증가합니다. 적을 깜짝 놀라게 해 보세요.
위험해 보이는 상황도 충분히 즐길 수 있는 게 라칸입니다.
라칸은 모든 스킬을 잘 활용하려면 근처에 아군이 함께 있어야 합니다.
체력이 낮을 때는 악의 장막이 주는 체력 회복 촉진 및 위장 효과로 전투에 복귀해 적의 빈틈을 노릴 수 있습니다.
은신 상태에서는 적 챔피언에게 얼마나 다가가면 감지되는지 주의를 기울이십시오. 근처 적 챔피언 위에 노란색이나 빨간색 눈이 빛나므로 적의 감지 여부를 파악할 수 있습니다.
황홀한 저주의 매혹 시전 시간이 길게 느껴질 수도 있지만 이블린은 매혹과 마법 저항력 감소 효과로 매우 유리한 입장에서 싸울 수 있기 때문에 기다릴 만한 가치가 있습니다.
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 fell from NaN to NaN. This negative change shows that 이블린 helps 라칸 perform worse in ranked League games. Yet, the small difference proves that this performance change is not very impactful.
When 라칸 tries to synergize with 이블린, he gets a small decrease in his full damage output. This could indicate that 이블린 does not support by providing protection for him to deal more damage or that her support also helps increase the game's duration. Similarly, when 라칸 is played with 이블린 on the same side, he usually scores many fewer killing sprees compared to when he plays without 이블린. This is contrasting evidence that he is worse when playing alongside 이블린.
Moreover, when 라칸 plays with 이블린 on the same side, he usually takes a little more damage than when he fights alone. Receiving more damage could mean that 이블린 does a poor job of protecting 라칸 during team fights.
There is no universally accepted best champion pairing for 라칸 that will always be his best teammate. However, overall, 이블린 is a very typical companion for 라칸. By locking into the same side as 라칸, she lowers their win rate by -0.9% to 49.7%. This signals that there is a weak strategic relationship between 라칸 and 이블린 that results in them performing worse together than without each other.
이블린 has a much greater difficulty compared to 라칸. That means 라칸 players need to be cautious when enlisting 이블린 comrades to fight alongside, as they will require a much higher level of skill to be able to work well with you.
Fighting on the same side, 라칸 players should expect to witness an overall large increase in your team’s capability to deal magic damage. When paired, these champs can deal quite a lot of AP type damage.
Although, by grouping 라칸 and 이블린 together, you probably will not be providing your other allies very much attack damage. Make sure to bring other champions on your team that nullifies this disparity in their capabilities.
Regardless of the ability of your 이블린 teammate, you need to focus on increasing your income, outlasting your enemies, and clearing objectives. If you do this, you will do well anyway.
If you would like to learn all of the intricacies of 라칸 in order to work well with 이블린 during both the lane and mid / late game phases of League matches, you should keep reading to learn some more tips and tricks for this champion pairing. If you listen to the build and suggestions shown above, you will increase your win rate by a lot.
The top finished items to prioritize in your 라칸 and 이블린 synergy build include 개척자, 강철의 솔라리 펜던트, and 천상의 이의. When 라칸 bought at least these three pieces in his build, he did much better when paired up with 이블린 than with most other typical builds. In fact, 라칸 had an average win rate of 49.7% when synergizing his build and playstyle to 이블린 with this build.
To have the best probability of beating your oponents, 라칸 players should equip the 수호자, 생명의 샘, 뼈 방패, 불굴의 의지, 좀비 와드, and 궁극의 사냥꾼 runes from the 결의 and 지배 rune sets. Of all the rune sets we have analyed for this team composition, this set of runes yielded the top win rate. Moreover, these runes gave a 49.7% win rate overall.
By default, tips, statistics, and builds on how to synergize 이블린 with 라칸 are shown for all ranked divisions. If you would like to scope the stats and builds to a distinct rank, you should use the selection menu at the top of this page.