수호자의 심판은 힘을 모으지 않고도 사용할 수 있습니다. 1대1 상황에서 적에게 바로 수호자의 심판을 써서 밀어내 보세요.
강철의 외교관을 사용했을 때 던지는 방패는 보통 벽 옆에 떨어지므로 용감한 돌진 스킬을 연계하면 좋습니다.
적이 많을 때 양떼 도륙 스킬을 사용할 경우 대량의 체력을 회복합니다. 이것을 미끼로 약한 척 행세하며 적을 유인할 수 있습니다.
자르고 토막내기는 적을 견제하며 괴롭힐 때 좋은 스킬입니다. 찌르며 들어가 다른 스킬을 사용한 뒤 다시 안전한 곳으로 물러날 수 있기 때문입니다.
재사용 대기시간 감소 효과는 레넥톤의 분노를 빠르게 늘릴 수 있게 해줍니다.
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 large worsening in her KDA (ratio of kills and assists to deaths) when paired with 레넥톤. His KDA fell from NaN to NaN. This decrease shows that 레넥톤 helps 뽀삐 perform poorer in ranked LoL games. Yet, the small difference shows that this performance change is not very impactful.
When 뽀삐 plays on the same team as 레넥톤, she observes a small decrease in her total damage dealt. This could demonstrate that 레넥톤 doesn't help cover for her to dish out more damage or that his allyship also helps extend the match's duration. Similarly, when 뽀삐 is played with 레넥톤 on the same team, he usually scores many fewer killing sprees compared to when she plays alone. This is contrasting evidence that she is worse when playing with 레넥톤.
Moreover, when 뽀삐 plays with 레넥톤 on the same team, she on average takes a little more damage than when she plays alone. Taking more damage could indicate that 레넥톤 does a poor job of protecting 뽀삐 during team fights.
There is no ideal synergy for 뽀삐 that will no matter what be her top ally. Yet, overall, 레넥톤 is a very bad companion for 뽀삐. By playing on the same side as 뽀삐, he drops their win rate by -5.0% to 44.7%. This demonstrates that there is an easy to overcome and exploit strategic relationship between 뽀삐 and 레넥톤 that results in them performing worse together than alone.
레넥톤 has a much lower diffuclty than 뽀삐. That means 뽀삐 players don't need to be cautious when arranging 레넥톤 allies to go into battle on the same side as, as they will need a much lower level of skill to fight well with you.
When playing alongside, 뽀삐 players should expect to see an overall large increase in your team’s ability to destroy wih physical damage. Combined, these champs can tear through the other team with a lot of physcial damage.
In contrast, by pairing 뽀삐 and 레넥톤 together, you may not be granting your team a great deal of magic damage. We recommend you have other champions on your team that offsets this disparity in this pairing's capabilities.
Regardless of your 레넥톤 ally's ability, you need to focus on maximizing your gold income, staying alive by avoiding foolish fights, and taking down objectives. If you follow these simple suggestions, you will do well, regardless.
If you would like to learn all of the intricacies of 뽀삐 to pair well with 레넥톤 during both the early game and mid / late game phases of League games, you should continue reading to learn some more tricks and insights into this champion pairing. If you listen to the build and stats shown here, you will increase your win rate by a lot.
The most important finished items to have in your 뽀삐 and 레넥톤 synergy build consist of 끝없는 절망, 태양불꽃 방패, and 가시 갑옷. When 뽀삐 combined at least these three finished items in her build, she did significantly better when fighting alongside 레넥톤 than with most other common item sets. In fact, 뽀삐 boasted an average win rate of 44.7% when playing alongside 레넥톤 with this build.
To have the highest likelihood of crushing your oponents, you should use the 어둠의 수확, 비열한 한 방, 사냥의 증표, 끈질긴 사냥꾼, 기민함, and 물 위를 걷는 자 runes from the 지배 and 마법 rune sets. Out of all the runes we have analyed for this team composition, this order of runes resulted in the best win rate. In fact, these runes provided a 44.7% winrate overall.
By default, tips, stats, and builds on how to synergize 레넥톤 with 뽀삐 are given for every ranked division. If you would like to narrow the statistics and builds to a distinct player tier, you should use the selection menu located earlier on the page.