파멸의 돌격은 이동 거리에 비례한 피해를 줍니다. 그림자의 맹습이나 소환사 주문 유체화 혹은 점멸을 이용해 피해량을 극대화하세요.
공포의 망령 스킬은 주변 적들이 피해를 입을 때 체력을 회복해 주며, 아군이 피해를 입혀도 역시 체력이 회복됩니다. 대규모 교전 시 공포의 망령을 활용해 헤카림의 생존력을 올리세요.
생물 분해 광선을 사용할 때는 이 스킬을 끊을 수 있는 스킬을 가진 챔피언이 많으므로 매우 주의하셔야 합니다.
플라즈마 분열을 대각선으로 발사해 최대 사거리에서 갈라지게 하면 최초 투사체의 사거리 밖에 있는 적을 맞힐 수 있습니다. 대신 후퇴하기는 더 까다롭습니다.
공격로 대치 단계에서 공허 균열을 사용하면 미니언을 처치하면서 적 챔피언에게 유기물 분해 중첩까지 쌓을 수 있습니다. 그 다음 다른 스킬을 연계하세요.
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 decreased from NaN to NaN. This fall shows that 벨코즈 helps 헤카림 perform not as well in competitive League rounds. Yet, the small difference shows that this performance change is only marginal.
When 헤카림 is paired with 벨코즈, he sees a little drop in his total damage output. This change may signal that 벨코즈 does not provide cover for him to deal more damage or that his support also helps extend the game's duration. Similarly, when 헤카림 is played alongside 벨코즈 on the same team, he usually scores many fewer killing sprees compared to when he plays without 벨코즈. This is contrasting evidence that he is worse when playing with 벨코즈.
Additionally, when 헤카림 plays with 벨코즈 on the same side, he often receives a little more damage than when he fights alone. Getting dealt more damage could mean that 벨코즈 does a poor job of covering 헤카림 in team fights.
There is no universally accepted best ally for 헤카림 that will 100% of the time be his top synergy. Yet, overall, 벨코즈 is a very typical teammate for 헤카림. By playing on the same team as 헤카림, he increases their win rate by 0.8% to 49.3%. This proves that there is only a small strategic relationship between 헤카림 and 벨코즈 that allows them to perform better together than without each other.
벨코즈 has a greater difficulty than 헤카림. That means 헤카림 players must be careful when lining up 벨코즈 allies to play with, as they will have to have a greater level of skill to be able to fight well with you.
Working together, you will likely see an overall large increase in your team’s capability to to do a lot of AP damage. Combined, these two are able to dish out a surprising amount of magic type damage.
Conversely, by bringing 헤카림 and 벨코즈 together, you probably will not be providing your other allies a lot of crowd control. Make sure to bring other champs on your team that fills this relative gap in this pairing's abilities.
Regardless of the ability of your 벨코즈 teammate, you need to focus on increasing your gold income, outlasting your enemies, and clearing objectives. If you do this, you should do well, regardless.
To learn all of the intricacies of 헤카림 in order to work well with 벨코즈 during both the laning and mid / late game phases of League rounds, you should continue reading to learn a few extra tricks and insights into this champion pairing. If you use the build and stats displayed above, you will increase your win rate significantly.
The best finished items to have in your 헤카림 and 벨코즈 synergy build consist of 쇼진의 창, 갈라진 하늘, and 월식. When 헤카림 combined at least these three finished items in his build, he did much better when fighting alongside 벨코즈 than with most other common item sets. In fact, 헤카림 boasted an average win rate of 49.3% when playing alongside 벨코즈 with these items in his kit.
To have the highest likelihood of defeating your oponents, 헤카림 players should use the 난입, 빛의 망토, 기민함, 물 위를 걷는 자, 사냥의 증표, and 보물 사냥꾼 runes from the 마법 and 지배 rune sets. Out of all the rune builds that we analyzed for this team composition, this mix of runes resulted in the top win rate. In fact, these runes averaged a 49.3% winrate overall.
By default, tips, statistics, and builds on how to pair 벨코즈 with 헤카림 are shown for all skill levels, merged. If you want to narrow the stats and builds to an individual player tier, you may use the selection menu located at the top of this page.