시비르의 부메랑 검은 최대 사거리에 도달하면 다시 되돌아오므로 되돌아오는 위치를 계산하며 이동하여 적이 부메랑에 맞도록 유도할 수 있습니다.
주문 방어막은 기절이나 속박 등 방해 효과가 있는 적 스킬에 대비하여 아껴 두세요.
튕기는 부메랑 스킬은 시비르의 기본 공격 모션을 취소합니다. 기본 공격을 사용한 후 튕기는 부메랑 스킬을 사용하면 피해량을 최대화 할 수 있습니다.
올라프는 광전사의 분노, 광포한 공격, 라그나로크를 함께 사용하여 체력이 낮은 상태에서 적의 허를 찌를 정도로 강해질 수 있습니다.
광포한 공격의 추가 치유 효과는 생명력 흡수율을 올려주는 동시에 아군으로부터 받는 치유 효과도 증폭시켜 줍니다.
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 worsened from NaN to NaN. This worsening shows that 올라프 helps 시비르 perform not as well in competitive League matches. Yet, the small difference shows that this performance change is not very impactful.
When 시비르 is an ally to 올라프, she gets a noticable drop in her complete damage dealt. This may indicate that 올라프 does not help protection for her to dish out more damage or that his allyship also helps increase the match's duration. Similarly, when 시비르 is played together with 올라프 on the same side, he usually scores many fewer killing sprees compared to when she plays without 올라프. This is contrasting evidence that she is worse when playing with 올라프.
Additionally, when 시비르 plays with 올라프 on the same team, she often takes a little less damage than when she fights alone. Taking not as much damage may indicate that 올라프 does a decent job of protecting 시비르 in team fights.
There is no universally accepted best ally for 시비르 that will always be her best teammate. Yet, 올라프 is a relatively poor companion for 시비르. By locking into the same side as 시비르, he drops their win rate by -2.8% to 45.1%. This signals that there is a harmful bond between 시비르 and 올라프 that allows them to perform worse together than alone.
올라프 has a lower difficulty than 시비르. That means you don't need to be careful when enlisting 올라프 teammates to go into battle on the same side as, as they will need a lower level of skill to do well with you.
When playing alongside, 시비르 players will likely observe an overall large increase in your team’s capability to deal physical damage. Combined, these two should be able to take down targets with auto-attacks and other AD damage abilities.
In contrast, by grouping 시비르 and 올라프 together, you probably will not be giving your side a lot of magical damage output. We recommend you include other champs on your team that neutralizes this relative disparity in their capabilities.
Regardless of your 올라프 ally's ability, you should focus on maximizing 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 truly master 시비르 to pair well with 올라프 during both the early game and mid / late game phases of League, you should keep reading to pick up additional lessons on this champion pairing. If you pay attention to the build and stats shown above, you will grow your win rate by a lot.
The top items to get in your 시비르 and 올라프 synergy build include 도미닉 경의 인사, 크라켄 학살자, and 나보리 신속검. When 시비르 included at least these three great items in her build, she did a lot better when fighting alongside 올라프 than with most other commonly used builds. In fact, 시비르 had an average win rate of 45.1% when synergizing her build and playstyle to 올라프 with this build.
To have the highest likelihood of vanquishing your oponents, you should take the 치명적 속도, 침착, 전설: 핏빛 길, 최후의 일격, 절대 집중, and 폭풍의 결집 runes from the 정밀 and 마법 rune sets. Out of all the runes that we analyzed for 시비르 and 올라프 pairings, this combo of runes resulted in the greatest win rate. Notably, these runes provided a 45.1% win rate overall.
By default, tips, statistics, and builds on how to synergize 올라프 with 시비르 are presented for all ranked divisions combined. If you would like to scope the statistics and builds to a distinct skill level, you may use the selection menu located earlier on the page.