교전 시에는 궁극기로 적을 기절시킬 수 있게끔 벽 근처로 유인하세요.
지피지기면 백전백승! 미니 나르는 빠르고 체력이 낮은 대신 지속 피해량이 높습니다. 메가 나르는 느리고 튼튼하며 순간 피해량이 높습니다.
분노 관리는 매우 중요합니다. 미니 나르와 메가 나르 두 형태의 이점을 극대화할 수 있도록 변신 시점을 잘 조절해 보세요.
시비르의 부메랑 검은 최대 사거리에 도달하면 다시 되돌아오므로 되돌아오는 위치를 계산하며 이동하여 적이 부메랑에 맞도록 유도할 수 있습니다.
주문 방어막은 기절이나 속박 등 방해 효과가 있는 적 스킬에 대비하여 아껴 두세요.
튕기는 부메랑 스킬은 시비르의 기본 공격 모션을 취소합니다. 기본 공격을 사용한 후 튕기는 부메랑 스킬을 사용하면 피해량을 최대화 할 수 있습니다.
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 fell from NaN to NaN. This negative change shows that 시비르 helps 나르 perform poorer in ranked LoL rounds. Yet, the small difference demonstrates that this performance change is not very impactful.
When 나르 is an ally to 시비르, he gets a marginal improvement in his complete damage dealt. This change could demonstrate that 시비르 provides protection for him to dish out more damage or that her allyship also helps extend the round's duration. Similarly, when 나르 is played with 시비르 on the same team, he usually scores many fewer killing sprees than when he plays without 시비르. This is contrasting evidence that he is worse when playing alongside 시비르.
Moreover, when 나르 plays with 시비르 on the same team, he often takes a little more damage than when he plays alone. Receiving more damage may mean that 시비르 does a poor job of protecting 나르 in team fights.
There is no top companion for 나르 that will always be his ideal ally. However, 시비르 is a not very good ally for 나르. By being on the same side as 나르, she lowers their win rate by -1.3% to 46.7%. This clearly indicates that there is a negative bond between 나르 and 시비르 that allows them to perform worse together than without each other.
시비르 has a much lower diffuclty than 나르. That means you don't need to be careful when finding 시비르 teammates to go into battle on the same side as, as they will need a much lower level of skill to fight well with you.
Fighting on the same side, 나르 players will likely see an overall large increase in your team’s capacity to dish out massive AD. Combined, these champs should be able to take down targets with auto-attacks and other AD damage abilities.
Conversely, by grouping 나르 and 시비르 together, you probably will not be providing your other teammates a great deal of AP. We recommend you bring other champs on your team that helps cover this gap in this pairing's potential.
Regardless of the ability of your 시비르 teammate, you need to focus on increasing your income, warding to avoid ambushes, and clearing objectives. If you follow these simple suggestions, you should do well anyway.
If you would like to truly master 나르 to pair well with 시비르 during both the early game and mid / late game phases of League of Legends rounds, you should continue reading to gather a few extra tricks and insights into this champion pairing. If you mind the build and suggestions shown here, you will grow your win rate by a lot.
The most crucial items to focus on in your 나르 and 시비르 synergy build consist of 스테락의 도전, 칠흑의 양날 도끼, and 삼위일체. When 나르 incorporated at least these three items in his build, he did a lot better when paired up with 시비르 than with many other typical builds. In fact, 나르 boasted an average winrate of 46.7% helping carry 시비르 with this build.
To have the highest probability of annihilating your oponents, 나르 players should use the 기민한 발놀림, 승전보, 전설: 민첩함, 최후의 저항, 뼈 방패, and 과잉성장 runes from the 정밀 and 결의 rune sets. Of all the runes players picked for 나르 and 시비르 pairings, this blending of runes resulted in the top win rate. In fact, these runes provided a 46.7% winrate overall.
By default, tips, stats, and builds on how to pair 시비르 with 나르 are displayed for all ranked divisions combined. If you would like to scope the stats and builds to a particular skill level, you should use the selection menu located at the top of this page.