빙하 균열은 강력한 둔화 구역을 남깁니다. 팀간 전투 시 적들을 갈라놓고 다가오는 속도를 늦출 수 있는 위치에 사용하세요.
불굴 스킬을 사용하면 방어력이 약한 아군 앞으로 도약하여 투사체 공격을 막아줄 수 있습니다.
아군과 협동하여 뇌진탕 펀치 중첩을 쌓는 게 좋습니다. 아군에게 표식이 생긴 대상을 기본 공격하라고 알려주세요.
카사딘의 궁극기는 사용법이 다양하고 재사용 대기시간도 비교적 짧으므로 자주 활용하십시오.
카사딘은 여러 가지 방면으로 성장시킬 수 있는 챔피언입니다. 마나와 주문력을 늘려 마법 공격형 챔피언으로 성장시킬 수도 있으며 재사용 대기시간 감소와 마법 저항력 위주의 아이템을 장착하면 마법사 사냥꾼으로 둔갑합니다.
푸른 파수꾼을 처치하여 균열 이동을 연속해서 사용할 때 증가하는 마나 소모량에 대비하십시오.
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 decreased from NaN to NaN. This decrease shows that 카사딘 helps 브라움 perform not as well in ranked League of Legends games. Yet, the small difference shows that this performance change is only marginal.
When 브라움 is paired with 카사딘, he gets a little drop in his complete damage output. This may signal that 카사딘 does not provide protection for him to dish out more damage or that his support also helps increase the match's duration. Similarly, when 브라움 is played together with 카사딘 on the same side, he usually scores many fewer killing sprees than when he plays alone. This is contrasting evidence that he is worse when playing with 카사딘.
Moreover, when 브라움 plays with 카사딘 on the same team, he typically receives a little less damage than when he plays alone. Receiving not as much damage may mean that 카사딘 does a decent job of covering 브라움 during teamfights.
There is no one best companion for 브라움 that will 100% of the time be his top synergy. Yet, 카사딘 is a very typical companion for 브라움. By locking into the same side as 브라움, he drops their win rate by -0.9% to 50.5%. This shows that there is only a small strategic relationship between 브라움 and 카사딘 that results in them performing worse together than alone.
카사딘 has a much greater difficulty compared to 브라움. That means you must be careful when finding 카사딘 comrades to go into battle on the same side as, as they will need a much higher level of skill to be able to play well with you.
When playing together, you will likely see an overall large increase in your team’s capability to to cover for your other teammates. When paired, these two might be able to provide enough cover for their team's carries.
In contrast, by bringing 브라움 and 카사딘 together, you probably will not be providing your other allies very much sustained damage output. We recommend you include other champs on your team that offsets this relative hole in their potential.
Regardless of your 카사딘 ally's skill level, you should focus on maximizing your gold income, staying alive by avoiding foolish fights, and clearing objectives. If you do this, you should do well anyway.
To learn all of the intricacies of 브라움 to pair well with 카사딘 during both the lane and mid / late game phases of League rounds, you should continue reading to master a few extra tricks and insights into this champion pairing. If you mind the build and tips shown here, you will increase your win rate by a lot.
The top items to have in your 브라움 and 카사딘 synergy build include 기사의 맹세, 강철의 솔라리 펜던트, and 태양의 썰매. When 브라움 incorporated at least these three items in his build, he performed a lot better as an ally of 카사딘 than with most other typical item sets. In fact, 브라움 boasted an average winrate of 50.5% helping carry 카사딘 with these items in his kit.
To have the best chance of coming out on top against your oponents, 브라움 players should equip the 수호자, 생명의 샘, 뼈 방패, 불굴의 의지, 비스킷 배달, and 우주적 통찰력 runes from the 결의 and 영감 rune sets. Of all the rune builds we have analyed for this champion pairing, this mixture of runes resulted in the best win rate. Moreover, these runes provided a 50.5% winrate overall.
By default, tips, statistics, and builds on how to synergize 카사딘 with 브라움 are given for all skill levels, merged. To narrow the statistics and builds to a distinct rank, you may use the selection menu earlier on the page.