신지드는 맹독의 자취를 사용하여 효과적으로 미니언을 제거하거나 적에게 피해를 가할 수 있습니다. 이는 공격로 관리에 매우 유용합니다.
적에게 던져넘기기를 사용하여 아군 포탑 쪽으로 던져버리면 큰 피해를 입힐 수 있습니다.
광기의 물약을 사용하여 적을 유인한 뒤 맹독의 자취를 사용하십시오.
뼈 작살을 짧게 눌러 사용하면 훨씬 빠르게 추가 피해를 줄 수 있습니다.
공격 스킬의 대부분은 도주 수단이 되기도 합니다. 전투에서 빠져나올 방법을 미리 계획해 두세요.
뼈 작살을 길게 눌러 사용하면 항상 일정한 거리만큼 적을 끌어당깁니다. 가까운 적에게 사용할 경우 파이크의 등 뒤로 적을 넘길 수 있습니다.
파이크는 체력이 약한 편이기 때문에 전투에서 잠시 동안 몸을 피해야 할 때도 있습니다. 적에게 보이지 않을 경우에는 가라앉은 자들의 축복으로 상당량의 체력을 회복할 수 있습니다.
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 worsened from NaN to NaN. This drop shows that 파이크 helps 신지드 perform poorer in competitive League rounds. Yet, the small difference indicates that this performance change is only marginal.
When 신지드 plays on the same team as 파이크, he observes a marginal improvement in his full damage output. This could signal that 파이크 supports by providing cover for him to dish out more damage or that his support also helps increase the match's duration. Similarly, when 신지드 is played alongside 파이크 on the same side, he usually scores many fewer killing sprees than when he plays without 파이크. This is contrasting evidence that he is worse when playing with 파이크.
Moreover, when 신지드 plays with 파이크 on the same side, he on average takes a little more damage than when he fights alone. Taking more damage could indicate that 파이크 does a poor job of protecting 신지드 in team fights.
There is no one best companion for 신지드 that will always be his best synergy. Yet, 파이크 is a relatively poor companion for 신지드. By locking into the same side as 신지드, he decreases their win rate by -1.9% to 50.5%. This proves that there is a harmful strategic relationship between 신지드 and 파이크 that results in them performing not as well together than without each other.
파이크 has a greater difficulty than 신지드. That means 신지드 players should be careful when arranging 파이크 teammates to go into battle on the same side as, as they will have to have a greater level of skill to work well with you.
Playing cooperatively, you will likely witness an overall large increase in your team’s capability to destroy wih physical damage. Together, these champions can provide a great amount of sustained physical damage.
Conversely, by bringing 신지드 and 파이크 together, you will not be granting your team a lot of magic damage. We recommend you have other champs on your team that fills this relative gap in their kit.
Regardless of your 파이크 ally's ability, you should focus on increasing your gold income, staying alive by avoiding foolish fights, and taking down objectives. If you do this, you should do well anyway.
If you would like to learn all of the intricacies of 신지드 to work well with 파이크 during both the laning and mid / late game phases of League, you should keep reading to gather some more lessons on this champion pairing. If you listen to the build and stats presented here, you should increase your win rate by a lot.
The most crucial finished items to include in your 신지드 and 파이크 synergy build include 라일라이의 수정홀, 무덤꽃, and 리안드리의 고통. When 신지드 combined at least these three pieces in his build, he performed much better as an ally of 파이크 than with most other commonly used item sets. In fact, 신지드 had an average win rate of 50.5% when synergizing his build and playstyle to 파이크 with these items in his kit.
To have the best chance of vanquishing your oponents, you should take the 정복자, 승전보, 전설: 강인함, 최후의 저항, 기민함, and 빛의 망토 runes from the 정밀 and 마법 rune sets. Out of all the rune builds players used for this team composition, this mix of runes yielded the top win rate. Moreover, these runes gave a 50.5% winrate overall.
By default, tips, statistics, and builds on how to synergize 파이크 with 신지드 are given for all ranked divisions. To filter the stats and builds to a specific division, you can use the selection menu located earlier on the page.