어떤 대상을 사냥할지 신중하게 선택하세요. 게임이 진행될수록 사냥에 많이 성공해야만 승리를 기약할 수 있습니다.
대규모 교전 시엔 선두에서 들어가지 마세요. 아군이 공격을 개시하길 기다리는 편이 좋습니다.
정글 사냥 시 공격하는 사이사이 움직이면 몬스터의 공격을 피할 수 있을 뿐더러 늑대의 광기 스킬로 인한 치유 효과가 활성화됩니다.
수호자의 심판은 힘을 모으지 않고도 사용할 수 있습니다. 1대1 상황에서 적에게 바로 수호자의 심판을 써서 밀어내 보세요.
강철의 외교관을 사용했을 때 던지는 방패는 보통 벽 옆에 떨어지므로 용감한 돌진 스킬을 연계하면 좋습니다.
The 킨드레드 뽀삐 synergy stats shown here demonstrate the areas of their gameplay that do better (or worse) when paired with 뽀삐, compared to their overall stats. Significant differences are areas of focus that highlight how their gameplay changes when paired with this other champion.
Overall, 킨드레드 sees a large worsening in their KDA (ratio of kills and assists to deaths) when paired with 뽀삐. His KDA fell from NaN to NaN. This worsening shows that 뽀삐 helps 킨드레드 perform not as well in ranked LoL matches. Yet, the small difference indicates that this performance change is not very impactful.
When 킨드레드 plays on the same team as 뽀삐, they gets a clear improvement in their full damage output. This may indicate that 뽀삐 provides protection for them to dish out more damage or that her presence also helps increase the round's duration. Similarly, when 킨드레드 is played with 뽀삐 on the same team, he usually scores many fewer killing sprees compared to when they plays without 뽀삐. This is contrasting evidence that they is worse when playing synergisticly with 뽀삐.
Additionally, when 킨드레드 plays with 뽀삐 on the same team, they usually takes a little less damage than when they fights alone. Taking not as much damage could mean that 뽀삐 does a decent job of covering 킨드레드 during teamfights.
There is no ideal companion for 킨드레드 that will 100% of the time be their best ally. Yet, overall, 뽀삐 is a fantastic ally for 킨드레드. By locking into the same side as 킨드레드, she improves their win rate by 4.1% to 52.4%. This clearly indicates that there is a very strong bond between 킨드레드 and 뽀삐 that allows them to perform stronger together than without each other.
뽀삐 has a greater difficulty than 킨드레드. That means you must be very careful when finding 뽀삐 allies to fight alongside, as they will require a greater level of skill to be able to do well with you.
Playing on the same side, 킨드레드 players should witness an overall large increase in your team’s capability to deal physical damage. Combined, these champions should be able to take down targets with auto-attacks and other AD damage abilities.
Conversely, by aligning 킨드레드 and 뽀삐 together, you will not be giving your side a great deal of AP. Plan to include other champions on your team that fills this hole in their playstyle.
Regardless of your 뽀삐 ally's ability, you should focus on maximizing your income, warding to avoid ambushes, and taking down objectives. If you do this, you will do well, regardless.
If you would like to learn all of the intricacies of 킨드레드 in order to work well with 뽀삐 during both the lane and mid / late game phases of League of Legends rounds, you should continue reading to master a few extra lessons on this champion pairing. If you pay attention to the build and tips 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 pieces in their build, they performed a lot better when fighting alongside 뽀삐 than with many other common item sets. In fact, 킨드레드 had an average win rate of 52.4% when synergizing their build and playstyle to 뽀삐 with these items in their kit.
To have the highest likelihood of crushing your oponents, 킨드레드 players should take the 집중 공격, 승전보, 전설: 민첩함, 최후의 일격, 돌발 일격, and 보물 사냥꾼 runes from the 정밀 and 지배 rune sets. Out of all the runes that we analyzed for 킨드레드 and 뽀삐 pairings, this blending of runes resulted in the highest win rate. Notably, these runes averaged a 52.4% winrate overall.
By default, tips, statistics, and builds on how to team up 뽀삐 with 킨드레드 are shown for all skill levels, merged. If you would like to scope the statistics and builds to a specific player tier, you may use the selection menu located earlier on the page.