공격로에서는 죽음의 손길 관통 피해를 이용해 안전하게 적을 공격해 보세요.
제국의 눈을 바로 적중시키기는 어려우므로, 이미 전투가 일어나 어지러운 지역에 사용하거나 군중 제어 효과가 적용된 적에게 사용해 보세요.
속박명령으로 적을 속박시키기 어렵다면 적이 미니언 근처에 있을 때 미니언에게 스킬을 사용해 폭발을 일으키고 그 폭발로 적을 속박시켜 보세요.
악의 승천을 사용하면 적이 스웨인을 죽이기 어려워지지만 스웨인으로부터 도망가기는 쉬워집니다. 기동력이 좋은 적을 상대할 때는 둔화 효과가 있는 아이템을 구입해 적이 빠져나가지 못하게 해 보세요.
빅토르와 너무 가까이 붙지 마세요. 빅토르는 적과 가까이 붙을수록 공격이 정확해집니다.
현재 빅토르가 얼마나 많은 증강으로 업그레이드했는지 눈여겨보세요. 지팡이 끝의 색깔을 보고도 알 수 있습니다. (보라, 노랑, 파랑, 빨강)
The stats shown here emphasize some valuable 스웨인 vs. 빅토르 matchup stats that can help you grasp the distinctions between this set of champions. For instance, 스웨인’s KDA ratio ([kills + assists] / deaths) of NaN is greater than 빅토르’s ratio of NaN, demonstrating that 스웨인 may be more central to his team's team fighting effectiveness than 빅토르..
스웨인 usually has a slightly smaller longest killing spree than his counter does. Commonly, he receives more damage than 빅토르. This is usually reflective of differing health capacities; however, it can also illustrate that the champion with higher HP has less agility and thus is not able to escape further harm when poked or engaged.
Both League of Legends champions are great. Both champs have their strengths, weaknesses, and counters. In League's current meta, 스웨인 usually fairs equally well when trying to fight 빅토르, with a 49.4% win rate. Therefore, 스웨인 makes an ok counter to 빅토르.
While 스웨인 does have a lower winrate compared to 빅토르, when on opposite teams, 스웨인 also has a lower level of difficulty that makes him a less time consuming champion to learn. You still need to be cautious when picking 스웨인 into 빅토르as his relative depth means that you may not be able to unleash his full potential without a lot of practice beforehand.
Moreover, 스웨인 also has some amount of CC and other utility, a similar amount to 빅토르. This makes her just as valuable during team fights, especially when trying to counter champions with a ton of burst damage.
While there is not a single best champion overall in League of Legends, in 스웨인 vs 빅토르 matchups, 빅토르 is the better champion with a similar win rate, less champion complexity, and a similar amount of utility to help out your teammates during late stage team fights.
스웨인 is a somewhat poor counter for 빅토르. You will do well by focussing your gameplay on keeping up your CS and destroying objectives. If you are able to do that, you should be able to stand on your own as 스웨인 against 빅토르.
If you would like to truly master 스웨인 in order to counter 빅토르 during both the laning and mid / late game phases of League of Legends, you should keep reading to learn a few extra lessons on this matchup. If you pay attention to the build and stats shown here, you will grow your win rate by a lot and be that much closer to League of Legends pro players.
스웨인 often picks up less CS compared to 빅토르. Champions who on average don't acquire much CS typically don't have to have much CS to be valuable teammates, such as sup champs. They are capable of scaling properly off of their abilities and first items alone. Yet, champions with large amounts of CS, such as hyper-carries, typically require a lot of items to be effective. In either case, try to surpass the values displayed here to do well.
The most important items to focus on in your 스웨인 versus 빅토르 build consist of 라일라이의 수정홀, 악의, and 존야의 모래시계. When 스웨인 used at least these three items in his build, he performed a lot better countering 빅토르 than with most other commonly used builds. In fact, 스웨인 boasted an average win rate of 49.4% when playing against 빅토르 with this build.
To have the best probability of crushing 빅토르 as 스웨인, you should use the 정복자, 침착, 전설: 강인함, 최후의 저항, 사전 준비, and 과잉성장 runes from the 정밀 and 결의 rune sets. Out of all the rune builds we have analyed for 스웨인 vs 빅토르 LoL games, this mixture of runes yielded the best win rate. In fact, these runes averaged a 49.4% winrate overall.
By default, tips, stats, and builds on how to beat 빅토르 as 스웨인 are presented for all skill levels, merged. If you would like to filter the statistics and builds to a specific skill level, you should use the selection menu earlier on the page.