Background Image
如何赢得万花通灵与痛苦之拥的对抗赛万花通灵 is in the a tier of champions

万花通灵 vs 痛苦之拥

如何在LoL中以万花通灵的身份击败痛苦之拥万花通灵 is in the s tier of champions
MageSupport
AssassinMage

如何击败痛苦之拥成为万花通灵

based on 2,834 万花通灵 vs 痛苦之拥 matchups
胜率
52.6 %
kda
2.16
受欢迎度
2.6 %

How We Analyze LoL Champion Counters

At MOBA Champion, we analyze millions of recently ranked League rounds each and every week. Within our database, 万花通灵 fought 痛苦之拥 in 2834 rounds. Including so many games with 万花通灵 versus 痛苦之拥 gives us a lot of faith in our capacity to provide enlightening stats and a supported build to destroy 痛苦之拥. This particular pairing is fairly rare. 万花通灵 fights 痛苦之拥 in only 2.6% of her games.

万花通灵 vs 痛苦之拥 Matchup Summary

万花通灵 does a good job of beating 痛苦之拥. Typically, she wins a whopping 52.6% of the time the champs fight one another in. In 万花通灵 versus 痛苦之拥 rounds, 万花通灵’s team is 0.1% more likely to get first blood. This indicates that she probably will get first blood versus 痛苦之拥.

counterTitle

物品

第一项

期望时间
生命药水云游图鉴

下一个项目

5分钟
增幅典籍以太精魂

Core 万花通灵 Items

22分钟
灭世者的死亡之帽影焰风暴狂涌

可选项目

蜕生女妖面纱巫妖之祸中娅沙漏

Summoner Spells

summonerflash summoner spell D
summonerteleport summoner spell F

技能顺序

为万花通灵提升等级的第一个技能q
>
为万花通灵提供的第二种能力,以提高水平e
>
万花通灵 最大化的最后一项技能w

符文

主宰电刑血之滋味眼球收集器寻宝猎人
巫术法力流系带焦灼
Adaptive ForceAdaptive ForceArmor
万花通灵's passive ability p
万花通灵's q ability q
万花通灵's w ability w
万花通灵's e ability e
万花通灵's ultimate ability r
1
Q
2
E
3
W
4
Q
5
Q
6
R
7
Q
8
E
9
Q
10
E
11
R
12
E
13
E
14
W
15
W
16
R

Guide to Countering 痛苦之拥 as 万花通灵

Tips for Playing as 万花通灵 against 痛苦之拥

你可以在[选项]菜单中将她的被动设置到热键上。默认键位是[SHIFT]+[F1~F5]

尽量选好你的【天生幻魅】的施放时机,没用好的话,就会引起敌人的警觉。

Advice to Win Against 痛苦之拥

- 购买控制守卫可以帮助你侦测伊芙琳的位置,从而对她的伏击做好准备。

- 伊芙琳的很大一部分威胁都在她的魅惑效果“引诱”上。保护那些带有“引诱”标记的友军,或者,如果你被标记了,确保你的友军隔在你和伊芙琳可能发起攻击的位置之间。

- 如果你猜测伊芙琳已经离开了你的战线,可以通过打字以及在小地图上进行标记来让友军知道。

万花通灵 vs 痛苦之拥 Counter Stats

万花通灵 Image
winRate
52.6 %
VS
winRate
47.4 %
痛苦之拥 Image
5.4
< kills >
8.9
6.3
< deaths >
6.3
8.2
< assists >
6.7
1.27
< killingSprees >
2.01
108
< cs >
21
0.12
< dragons >
1.33
0.48
< inhibitors >
0.31
1,283
< physicalDamage >
701
17,945
< magicDamage >
20,705
756
< trueDamage >
610
19,985
< damageDealt >
22,016
21,442
< damageTaken >
31,571
10,550
< goldEarned >
12,036
1.95
< towers >
0.84
0.03
< barons >
0.3
2,367
< heal >
14,991
12,981
< xp >
13,710
33
< visionScore >
20
15
< wardsPlaced >
7
181
< ccTime >
195

How to Counter 痛苦之拥 with 万花通灵 in LoL

The stats shown here emphasize several vital 万花通灵 versus 痛苦之拥 matchup stats that may help you interpret the differences and similarities between the two. 万花通灵’s KDA ratio ([kills + assists] / deaths) of NaN is better than 痛苦之拥’s KDA ratio of NaN, indicating that 万花通灵 may be more central to her team's team fighting effectiveness than 痛苦之拥..

万花通灵 typically has a slightly smaller longest kill spree than her enemy does. Commonly, she receives less damage than 痛苦之拥. This typically indicates different amounts of tankyness; however, it can also illustrate that the champion with higher health has less mobility and thus is not able to flee from additional damage when engaged or poked.

championDifferences.title

伤害数据

万花通灵
痛苦之拥
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

万花通灵
痛苦之拥

championDifferences.whoIsBetter

Both LoL champions are great. Both have their strengths, weaknesses, and counters. In the game's current meta, 万花通灵 usually wins when trying to fight 痛苦之拥, with a 52.6% win rate. As a result, 万花通灵 makes a good counter to 痛苦之拥.

While 万花通灵 does have a higher winrate than 痛苦之拥, when they face off with one another, 万花通灵 also has a much lower difficulty level that makes her a less time consuming champion to develop with. You don't need to be too worried when picking 万花通灵 into 痛苦之拥.

Additionally, 万花通灵 has some amount of utility and CC, a similar amount to 痛苦之拥. This often makes her just as valuable during teamfights, 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 noticably higher win rate, less champion complexity, and a similar amount of utility to help out your allies during teamfights.

万花通灵 is an above average counter for 痛苦之拥. Make sure you focus your gameplay on keeping up your CS and destroying objectives. If you do that, you should hold your own as 万花通灵 against 痛苦之拥.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

To truly master 万花通灵 in order to counter 痛苦之拥 during both the lane and mid / late game phases of League of Legends, you should keep reading to learn a few extra lessons on this matchup. If you mind the build and suggestions shown here, you will increase your win rate by a lot and be closer to League of Legends pro players.

万花通灵 on average picks up much more CS relative to 痛苦之拥. Champions who on average don't acquire many minion kills often don't require much CS to be valuable teammates, such as supports. These kinds of champions are able to scale properly off of their abilities and first items alone. Yet, champs with a lot of CS, such as hyper-carries, usually require a lot of items to be effective. In either situation, try to do better than the numbers reported on this page to do well.

The ideal items to prioritize in your 万花通灵 versus 痛苦之拥 build include 灭世者的死亡之帽, 影焰, and 风暴狂涌. When 万花通灵 used at least these three pieces in her build, she did much better vs 痛苦之拥 than with most other typical item sets. In fact, 万花通灵 had an average win rate of 52.6% when playing against 痛苦之拥 with this counter build.

To have the best probability of defeating 痛苦之拥 as 万花通灵, you should take the 电刑, 血之滋味, 眼球收集器, 寻宝猎人, 法力流系带, and 焦灼 runes from the 主宰 and 巫术 rune sets. Out of all the rune builds players used for 万花通灵 vs 痛苦之拥 counterpicks, this sequence of runes yielded the highest win rate. Notably, these runes provided a 52.6% winrate overall.

By default, tips, stats, and builds on how to beat 痛苦之拥 as 万花通灵 are shown for all skill levels, merged. If you want to narrow the stats and builds to a specific skill level, you should use the selection menu earlier on the page.