대규모 접전에서는 다른 팀원이 먼저 전투를 시작할 때까지 기다리십시오.
구르기는 다양한 용도로 사용할 수 있지만 벽을 뚫고 지날 수는 없습니다.
선고는 대상을 벽에 밀어붙여 죽이거나 적에게서 탈출할 때 사용할 수 있습니다.
서포터로서 가장 중요한 역할은 약한 아군을 안전하게 지키는 것입니다. 집어삼키기의 재사용 대기시간과 사거리를 잘 생각해서 위치를 잡으세요!
두꺼운 피부 사용 효과는 언제 쓸지 잘 생각해야 합니다. 미리 보호막을 사용하여 추가 피해를 막는 편이 나을 때도 있지만, 체력 회복 효과를 활용하는 것이 훨씬 이득이 될 수도 있습니다.
The 베인 탐 켄치 synergy stats shown here demonstrate the areas of her gameplay that do better (or worse) when paired with 탐 켄치, compared to her overall stats. Significant differences are areas of focus that highlight how her gameplay changes when paired with this other champion.
Overall, 베인 sees a very large drop in her 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 poorer in competitive League games. Yet, the small difference proves that this performance change is not very impactful.
When 베인 is an ally to 탐 켄치, she observes a barely noticable drop in her total damage output. This change could signal that 탐 켄치 does not help protection for her to dish out more damage or that his presence also helps increase the match's duration. Similarly, when 베인 is played alongside 탐 켄치 on the same team, he usually scores many fewer killing sprees compared to when she plays on his own. This is contrasting evidence that she is worse when playing alongside 탐 켄치.
Additionally, when 베인 plays with 탐 켄치 on the same team, she often takes a little less damage than when she plays alone. Taking not as much damage may indicate that 탐 켄치 does a decent job of protecting 베인 in teamfights.
There is no top companion for 베인 that will no matter what be her ideal ally. However, 탐 켄치 is a decent companion for 베인. By being on the same team as 베인, he increases their win rate by 1.5% to 51.8%. This shows that there is a somewhat important bond between 베인 and 탐 켄치 that allows them to perform better together than alone.
탐 켄치 has a much lower diffuclty than 베인. That means 베인 players don't need to be very careful when lining up 탐 켄치 comrades to play with, as they will have to have a much lower level of skill to be able to work well with you.
Working on the same side, 베인 players should expect to see an overall large increase in your team’s capability to dish out massive AD. Combined, these two can provide a great amount of sustained physical damage.
Conversely, by pairing 베인 and 탐 켄치 together, you will not be providing your side a great deal of magical damage output. Make sure to bring other champions on your team that fills this disparity in their potential.
Regardless of the skill of your 탐 켄치 teammate, you need to focus on increasing your gold income, warding to avoid ambushes, and taking down objectives. If you follow these simple suggestions, you should do well anyway.
If you would like to learn all of the intricacies of 베인 in order to synergize with 탐 켄치 during both the laning and mid / late game phases of League of Legends matches, you should continue reading to master additional tricks and insights into this champion pairing. If you mind the build and stats displayed above, you will increase your win rate by a lot.
The most important finished items to focus on in your 베인 and 탐 켄치 synergy build include 마법사의 최후, 구인수의 격노검, and 경계. When 베인 bought at least these three items in her build, she did much better when fighting alongside 탐 켄치 than with many other commonly used builds. In fact, 베인 boasted an average winrate of 51.8% when synergizing her build and playstyle to 탐 켄치 with this build.
To have the greatest chance of crushing your oponents, you should equip the 치명적 속도, 승전보, 전설: 민첩함, 최후의 일격, 사전 준비, and 과잉성장 runes from the 정밀 and 결의 rune sets. Of all the rune combinations players chose for this team composition, this sequence of runes yielded the top win rate. Notably, these runes averaged a 51.8% winrate overall.
By default, tips, statistics, and builds on how to synergize 탐 켄치 with 베인 are displayed for all ranked divisions combined. If you want to narrow the statistics and builds to an individual division, you can use the selection menu located earlier on the page.