가까운 범위 내에 아군이 없으면 적은 고립된 것으로 간주됩니다. 이런 적에게는 공포 감지 스킬의 피해량이 대폭 증가합니다.
보이지 않는 위협은 카직스가 적의 시야에 노출되지 않을 때 발동됩니다. 수풀에 들어가거나 공허의 습격을 시전하면 보이지 않는 위협이 재발동됩니다. 적 챔피언을 자동 공격할 때는 계속 보이지 않는 위협을 적용해 주세요.
카직스는 교전 시점과 위치를 자유자재로 선택할 수 있습니다. 이 점을 잘 활용하면 이길 수 있습니다.
주의하세요. 신비한 차원문은 적군도 이용할 수 있고, 궁극기는 아군도 함께 정지시킵니다!
수호자의 성소는 설치한 후 충전될 시간을 주세요. 완전히 충전됐을 때 체력이 훨씬 더 많이 회복됩니다.
고대의 종을 모아서 정령 공격을 강화하는 것도 중요하지만, 공격로 파트너를 너무 혼자 둬도 안 됩니다! 신비한 차원문으로 통로를 만들어서 아군을 더 데리고 공격로로 돌아오는 것도 좋겠군요.
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 drop shows that 바드 helps 카직스 perform worse in competitive LoL games. Yet, the small difference demonstrates that this performance change is only marginal.
When 카직스 plays on the same team as 바드, he gets a marginal improvement in his full damage dealt. This change may signal that 바드 supports by providing protection for him to dish out more damage or that his allyship also helps extend the round's duration. Similarly, when 카직스 is played alongside 바드 on the same team, he usually scores many fewer killing sprees compared to when he plays on his own. This is contrasting evidence that he is worse when playing with 바드.
Additionally, when 카직스 plays with 바드 on the same side, he usually takes a little more damage than when he fights alone. Getting dealt more damage could mean that 바드 does a poor job of protecting 카직스 in teamfights.
There is no ideal ally for 카직스 that will no matter what be his ideal teammate. Yet, overall, 바드 is a good companion for 카직스. By playing on the same team as 카직스, he raises their win rate by 2.6% to 51.8%. This demonstrates that there is a somewhat important synergy between 카직스 and 바드 that results in them performing better together than alone.
바드 has a greater difficulty than 카직스. That means 카직스 players should be cautious when lining up 바드 allies to go into battle on the same side as, as they will have to have a greater level of skill to do well with you.
Fighting cooperatively, you should see an overall large increase in your team’s capability to deal physical damage. When paired, these two can provide a great amount of sustained physical damage.
In contrast, by grouping 카직스 and 바드 together, you will not be providing your other allies much magic damage. We recommend you pick other champions on your team that helps cover this hole in their kit.
Regardless of the skill of your 바드 ally, you need to focus on maximizing your gold income, outlasting your enemies, and clearing objectives. If you do this, you will do well, regardless.
If you would like to truly master 카직스 to pair well with 바드 during both the lane and mid / late game phases of League, you should continue reading to learn additional tips and tricks for this champion pairing. If you pay attention to the build and suggestions shown here, you will increase your win rate significantly.
The ideal items to prioritize in your 카직스 and 바드 synergy build include 밤의 끝자락, 세릴다의 원한, and 기회. When 카직스 included at least these three items in his build, he did significantly better when paired up with 바드 than with many other common item sets. In fact, 카직스 had an average winrate of 51.8% when synergizing his build and playstyle to 바드 with these items in his kit.
To have the best probability of defeating your oponents, 카직스 players should take the 선제공격, 마법의 신발, 외상, 우주적 통찰력, 돌발 일격, and 끈질긴 사냥꾼 runes from the 영감 and 지배 rune sets. Of all the rune builds we have analyed for 카직스 and 바드 pairings, this set of runes yielded the greatest win rate. Notably, these runes gave a 51.8% winrate overall.
By default, tips, statistics, and builds on how to synergize 바드 with 카직스 are presented for all ranked divisions. If you would like to narrow the statistics and builds to an individual division, you can use the selection menu earlier on the page.