가까운 범위 내에 아군이 없으면 적은 고립된 것으로 간주됩니다. 이런 적에게는 공포 감지 스킬의 피해량이 대폭 증가합니다.
보이지 않는 위협은 카직스가 적의 시야에 노출되지 않을 때 발동됩니다. 수풀에 들어가거나 공허의 습격을 시전하면 보이지 않는 위협이 재발동됩니다. 적 챔피언을 자동 공격할 때는 계속 보이지 않는 위협을 적용해 주세요.
카직스는 교전 시점과 위치를 자유자재로 선택할 수 있습니다. 이 점을 잘 활용하면 이길 수 있습니다.
땅굴을 맵 전역에 분산시켜두면 공허의 돌진 스킬에 유용하게 활용할 수 있습니다.
맵에서 이동하기 전에 매복을 시전하여 이동 속도 증가 효과를 받는 동시에 진동 감지의 이득도 챙기세요.
진동 감지 효과는 적들이 다가올 때 경고가 뜨므로, 적진으로 들어갈 때 특히 유용합니다.
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 decrease shows that 렉사이 helps 카직스 perform poorer in ranked League of Legends matches. Yet, the small difference shows that this performance change is only marginal.
When 카직스 is an ally to 렉사이, he sees a sizeable uptick in his total damage output. This could demonstrate that 렉사이 provides cover for him to dish out more damage or that his presence on the team also helps increase the round's duration. Similarly, when 카직스 is played alongside 렉사이 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 with 렉사이.
Moreover, when 카직스 plays with 렉사이 on the same side, he typically receives a little less damage than when he fights alone. Receiving not as much damage could indicate that 렉사이 does a decent job of protecting 카직스 in team fights.
There is no one best companion for 카직스 that will 100% of the time be his best ally. However, 렉사이 is a great companion for 카직스. By playing on the same team as 카직스, he improves their win rate by 3.2% to 52.4%. This proves that there is a strong strategic relationship between 카직스 and 렉사이 that results in them performing at the top of their game together than without each other.
렉사이 has a much lower diffuclty than 카직스. That means 카직스 players don't need to be very careful when enlisting 렉사이 teammates to fight alongside, as they will need a much lower level of skill to do well with you.
Working cooperatively, 카직스 players will likely see an overall large increase in your team’s ability to destroy wih physical damage. Combined, these champs can tear through the other team with a lot of physcial damage.
In contrast, by grouping 카직스 and 렉사이 together, you probably will not be giving your team a great deal of magic damage. Plan to pick other champions on your team that offsets this disparity in this pairing's capabilities.
Regardless of the skill of your 렉사이 ally, you need to focus on increasing your gold income, staying alive by avoiding foolish fights, and clearing objectives. If you heed this simple advice, you will do well, regardless.
To learn all of the intricacies of 카직스 in order to synergize 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 listen to the build and stats displayed above, you should grow your win rate by a lot.
The best items to use in your 카직스 and 렉사이 synergy build consist of 수호 천사, 요우무의 유령검, and 오만. When 카직스 incorporated at least these three items in his build, he performed a lot better when paired up with 렉사이 than with most other common builds. In fact, 카직스 had an average win rate of 52.4% helping carry 렉사이 with this build.
To have the best chance of beating your oponents, 카직스 players should equip the 선제공격, 마법의 신발, 외상, 우주적 통찰력, 절대 집중, and 폭풍의 결집 runes from the 영감 and 마법 rune sets. Of all the rune builds players chose for this champion pairing, this sequence of runes yielded the top win rate. In fact, these runes averaged a 52.4% winrate overall.
By default, tips, stats, and builds on how to pair 렉사이 with 카직스 are displayed for all skill levels combined. To scope the stats and builds to a distinct division, you may use the selection menu at the top of this page.