불사의 공포는 이미 살아남기 힘든 상태인 적에게 사용하세요. 주변 적을 떼어낼 때 특히 좋습니다.
각 다리의 재사용 대기시간에 주의하세요. 우르곳이 가하는 피해량의 상당 부분을 차지하니까요.
부식성 폭약 또는 경멸을 사용해 심판의 원을 사용할 대상을 추적하세요. 여러 다리에서 연달아 불꽃을 뿜어낼 수 있는 좋은 방법입니다.
체력이 낮을 때는 악의 장막이 주는 체력 회복 촉진 및 위장 효과로 전투에 복귀해 적의 빈틈을 노릴 수 있습니다.
은신 상태에서는 적 챔피언에게 얼마나 다가가면 감지되는지 주의를 기울이십시오. 근처 적 챔피언 위에 노란색이나 빨간색 눈이 빛나므로 적의 감지 여부를 파악할 수 있습니다.
황홀한 저주의 매혹 시전 시간이 길게 느껴질 수도 있지만 이블린은 매혹과 마법 저항력 감소 효과로 매우 유리한 입장에서 싸울 수 있기 때문에 기다릴 만한 가치가 있습니다.
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 large worsening in his KDA (ratio of kills and assists to deaths) when paired with 이블린. His KDA went down from NaN to NaN. This fall shows that 이블린 helps 우르곳 perform poorer in competitive League games. Yet, the small difference proves that this performance change is only marginal.
When 우르곳 is an ally to 이블린, he gets a marginal improvement in his complete damage output. This could indicate that 이블린 helps provide cover for him to deal more damage or that her allyship also helps extend the game's duration. Similarly, when 우르곳 is played with 이블린 on the same side, he usually scores many fewer killing sprees compared to when he plays without 이블린. This is contrasting evidence that he is worse when playing with 이블린.
Moreover, when 우르곳 plays with 이블린 on the same team, he typically takes a little more damage than when he plays alone. Getting dealt more damage may indicate that 이블린 does a poor job of protecting 우르곳 in team fights.
There is no universally accepted best ally for 우르곳 that will 100% of the time be his ideal ally. However, 이블린 is a pretty good ally for 우르곳. By locking into the same team as 우르곳, she increases their win rate by 1.3% to 52.4%. This proves that there is a somewhat important synergy between 우르곳 and 이블린 that allows them to perform stronger together than without each other.
이블린 has a greater difficulty than 우르곳. That means you must be very careful when finding 이블린 teammates to play with, as they will have to have a greater level of skill to be able to play well with you.
When playing cooperatively, 우르곳 players will likely see an overall large increase in your team’s ability to deal physical damage. Together, these champions can tear through the other team with a lot of physcial damage.
Conversely, by pairing 우르곳 and 이블린 together, you probably will not be giving your other allies very much support. Plan to bring other champions on your team that helps cover this relative gap in their kit.
Regardless of your 이블린 ally's skill level, you should focus on maximizing your gold income, outlasting your enemies, and taking down objectives. If you heed this simple advice, you will do well, regardless.
To truly master 우르곳 to pair well with 이블린 during both the early game and mid / late game phases of League of Legends matches, you should continue reading to master some more lessons on this champion pairing. If you use the build and stats shown above, you should grow your win rate significantly.
The best finished items to focus on in your 우르곳 and 이블린 synergy build consist of 스테락의 도전, 칠흑의 양날 도끼, and 죽음의 무도. When 우르곳 incorporated at least these three finished items in his build, he did a lot better as an ally of 이블린 than with many other common item sets. In fact, 우르곳 had an average winrate of 52.4% helping carry 이블린 with this build.
To have the highest probability of coming out on top against your oponents, 우르곳 players should use the 기민한 발놀림, 승전보, 전설: 강인함, 최후의 저항, 사전 준비, and 과잉성장 runes from the 정밀 and 결의 rune sets. Of all the runes players picked for 우르곳 and 이블린 pairings, this mixture of runes yielded the greatest win rate. Notably, these runes averaged a 52.4% winrate overall.
By default, tips, stats, and builds on how to team up 이블린 with 우르곳 are presented for all ranked divisions. If you would like to narrow the statistics and builds to a distinct division, you should use the selection menu earlier on the page.