마법공학 초소형 로켓을 멀리 분산시키면 여러 적에게 확실하게 안정적으로 피해를 가할 수 있지만, 한 대상에게 집중시킬 때 효과는 가장 큽니다.
하이머딩거의 생존을 위해서는 전자폭풍 수류탄을 잘 사용하는 것이 매우 중요합니다. 둔화와 기절을 통해 적들을 한 자리에 잡아두고 맹공을 가할 수도 있지만, 적의 급습에 대응하는 우선 방어 수단으로 잘 활용하세요.
포탑 설치 위치는 전투에 중요한 영향을 미칠 수 있습니다. 대부분의 적에 대해서는 포탑을 여러 개 모아 설치하는 게 제일 좋지만, 적에게 광역 공격 피해를 받으면 순식간에 포탑을 잃게 됩니다. 포탑을 수풀 안에 설치하면 기습 공격으로 유리한 위치를 선점할 수 있습니다.
오공은 적에게 둘러싸여 있을 때 더 강해집니다. 먼저 고립시킨 다음 처치할 기회를 노리세요.
오공은 자주 근두운 급습을 사용한 다음 분신술을 사용합니다. 잠시 기다렸다가 오공 본체를 확인한 다음 스킬을 사용하십시오.
The stats shown on this page show several significant 하이머딩거 vs. 오공 counter stats that can help you realize the distinctions between the two. For instance, 하이머딩거’s KDA ratio ([kills + assists] / deaths) of NaN is more than 오공’s KDA ratio of NaN, highlighting that 하이머딩거 may be more central to his team's team fighting potential than 오공..
하이머딩거 often has a slightly smaller longest killing spree than his opponent does. Commonly, he receives less damage than 오공. This typically indicates differing health capacities, yet it can also illustrate that the one champ has less agility and thus is not able to escape additional damage when poked or engaged.
Both LoL champions are great champions. Both have their pros and cons. In League's current meta, 하이머딩거 usually fairs equally well when taking on 오공, with a 49.7% win rate. As a result, 하이머딩거 makes an ok counter for 오공.
While 하이머딩거 does have a lower winrate than 오공, when facing one another, 하이머딩거 also has a much greater difficulty level that makes him a more difficult champion to pick up and master. You should be careful when picking 하이머딩거 into 오공as his relative depth means you may not be able to unleash his full potential without a significant amount of practice beforehand.
Additionally, 하이머딩거 also has a good amount of utility and CC, a similar amount to 오공. This makes her just as valuable during team fights, especially when fighting champions with a lot of burst damage.
While there isn't one best champion for every situation in League of Legends, in 하이머딩거 vs 오공 matchups, 오공 is the better champion with a similar win rate, more champion depth, and a similar amount of utility to help out your teammates during late stage team fights.
하이머딩거 is a somewhat poor counter to 오공. You will do well by focussing your actions on keeping up your CS and taking out objectives. If you are able to do that, you should hold your own as 하이머딩거 against 오공.
To truly master 하이머딩거 in order to counter 오공 during both the early game and mid / late game phases of League of Legends, you should keep reading to learn a few extra tips and tricks for this matchup. If you pay attention to the build and suggestions presented above, you should grow your win rate by a lot and be closer to League of Legends pro players.
하이머딩거 usually accumulates more CS relative to 오공. Champions who typically don't get much CS typically don't need much CS to be valuable teammates, such as support champions. They are able to scale properly off of their skills, stats, and first items alone. Yet, champs with a lot of CS, such as hyper-carries, often have to have several high cost items to be effective. In either situation, try to exceed the numbers shown on this page to do well.
The best items to prioritize in your 하이머딩거 versus 오공 build consist of 라일라이의 수정홀, 존야의 모래시계, and 리안드리의 고통. When 하이머딩거 included at least these three items in his build, he did a lot better when fighting 오공 than with many other common item sets. In fact, 하이머딩거 had an average win rate of 49.7% when countering 오공 with these items in his kit.
To have the greatest chance of annihilating 오공 as 하이머딩거, you should use the 신비로운 유성, 마나순환 팔찌, 절대 집중, 주문 작열, 비스킷 배달, and 마법의 신발 runes from the 마법 and 영감 rune sets. Out of all the runes that we analyzed for 하이머딩거 vs 오공 counter picks, this blending of runes resulted in the best win rate. Moreover, these runes gave a 49.7% winrate overall.
By default, tips, statistics, and builds on how to beat 오공 as 하이머딩거 are presented for every ranked division. If you would like to filter the stats and builds to a particular rank, you can use the selection menu earlier in the counter matchup guide.