Обманка и Верхом на облаке хорошо работают в связке, позволяя ударить врага и убежать, не получив урона самому.
Старайтесь использовать Обманку у кустов, чтобы еще больше смутить врага.
Вай не поддается контролю во время абсолютного умения. Приберегите эффекты перемещения до конца ее рывка.
Полностью заряженный Вскрыватель хранилищ наносит двойной урон. Если вы видите Вай, заряжающую умение, - отойдите и попробуйте увернуться от него.
Вай разрушит вашу броню и получит дополнительную скорость атаки, если сумеет ударить вас 3 раза подряд. Старайтесь не участвовать в затяжных боях с ней.
The stats shown on this page underscore several significant Вуконг versus Вай matchup stats that may help us explain the differences between the pair. Вуконг’s KDA ratio ([kills + assists] / deaths) of NaN is greater than Вай’s ratio of NaN, highlighting that Вуконг may be more central to his team's team fighting capacity than Вай..
Вуконг typically has a similar longest kill spree as his opponent does. Typically, he receives a similar amount of damage to Вай. This commonly reflects differing health capacities, yet it can also show that the one champ has less mobility and thus is not able to escape additional harm when poked or engaged.
Both League of Legends champs are great champions. Both have their pros and cons. In League's current meta, Вуконг usually loses when taking on Вай, with a 48.0% win rate. Therefore, Вуконг makes a poor counter to Вай.
While Вуконг does have a lower win rate compared to Вай, when on opposite teams, Вуконг also has a lower level of difficulty that makes him a less time consuming champ to learn. You should be very concerned when picking Вуконг into Вай.
Furthermore, Вуконг also has a good amount of utility and CC, a similar amount to Вай. This often makes her just as valuable during team fights, especially when trying to counter champions with a ton of burst damage.
While there isn't a single best champion in League of Legends, in Вуконг vs Вай matchups, Вай is the better champion with a lower win rate, less champion complexity, and a similar amount of utility to help out your teammates during team fights.
Вуконг is a trash counter to Вай. Focus your actions on increasing your gold and cs and destroying objectives. If you are able to do that, you should hold 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 continue reading to gather a few extra lessons on this matchup. If you mind the build and tips presented here, you should increase your win rate by a lot and be closer to League of Legends pro players.
Вуконг most often gets more CS as Вай. Champs who typically don't acquire much CS usualy don't need much CS to be effective, such as sup champs. They are capable of scaling properly off of their skills, stats, and first items alone. Yet, champions with large amounts of CS, such as hyper-carries, usually have to have many items to be effective. In either situation, try to exceed the values displayed on this page to do well.
The best items to use in your Вуконг versus Вай build consist of Тройственный Союз, Копье Седзина, and Расколотое небо. When Вуконг included at least these three pieces in his build, he did a lot better vs Вай than with many other typical counter builds. In fact, Вуконг had an average win rate of 48.0% when playing against Вай with this build.
To have the highest chance of annihilating Вай as Вуконг, you should use the Завоеватель, Триумф, Легенда: рвение, Последний рубеж, Магическая обувь, and Космическое знание runes from the Точность and Вдохновение rune sets. Out of all the rune sets we have analyed for Вуконг vs Вай fights, this composite of runes yielded the greatest win rate. In fact, these runes provided a 48.0% winrate overall.
By default, tips, stats, and builds on how to beat Вай as Вуконг are displayed for every ranked division. If you want to filter the statistics and builds to a specific player tier, you should use the selection menu located earlier on the page.