Background Image
如何赢得瘟疫之源与琴瑟仙女的对抗赛瘟疫之源 is in the a tier of champions

瘟疫之源 vs 琴瑟仙女

如何在LoL中以瘟疫之源的身份击败琴瑟仙女瘟疫之源 is in the a tier of champions
MarksmanAssassin
SupportMage

如何击败琴瑟仙女成为瘟疫之源

based on 3,768 瘟疫之源 vs 琴瑟仙女 matchups
胜率
47.6 %
kda
2.32
受欢迎度
2.5 %

How We Analyze LoL Champion Counters

We generate our matchup stats from the millions of recently ranked League of Legends rounds that we get from Riot Games every week. This guide on how to beat 琴瑟仙女 as 瘟疫之源 resulted from an evaluation of 3768 ranked matches where both champs faced each other. This champion matchup is fairly rare. 瘟疫之源 has to counter 琴瑟仙女 in only 2.5% of his matches.

瘟疫之源 vs 琴瑟仙女 Matchup Summary

Unfortunately, 瘟疫之源 does a below average job of beating 琴瑟仙女. Typically, he wins a lowly 47.6% of matches the champs clash against each other in. In 瘟疫之源 versus 琴瑟仙女 games, 瘟疫之源’s side is 0.1% more expected to gain first blood, indicating that he probably will be able to get first blood against 琴瑟仙女.

counterTitle

物品

第一项

期望时间
多兰之戒生命药水

下一个项目

5分钟
十字镐反曲之弓

Core 瘟疫之源 Items

22分钟
卢安娜的飓风鬼索的狂暴之刃界弓

可选项目

收集者智慧末刃灭世者的死亡之帽无尽之刃

Summoner Spells

summonerflash summoner spell D
summonerhaste summoner spell F

技能顺序

为瘟疫之源提升等级的第一个技能e
>
为瘟疫之源提供的第二种能力,以提高水平q
>
瘟疫之源 最大化的最后一项技能w

符文

主宰丛刃血之滋味眼球收集器无情猎手
精密气定神闲传说:欢欣
Attack SpeedAdaptive ForceHealth Scaling
瘟疫之源'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
E
5
E
6
R
7
E
8
Q
9
E
10
Q
11
R
12
Q
13
Q
14
W
15
W
16
R

Guide to Countering 琴瑟仙女 as 瘟疫之源

Tips for Playing as 瘟疫之源 against 琴瑟仙女

- 【E毒性爆发】范围很大,在使用之前尽量给对手多叠几层【死亡毒液】。

- 你可以用【W剧毒之桶】来追上那些超出射程的敌人。

- 图奇是游戏中最高攻击速度的英雄之一,尽量购买像黑色切割者、或智慧末刃等带有攻击附带效果的道具。

Advice to Win Against 琴瑟仙女

- 看到娑娜时要散开,避免她施法让你和友军跳舞。

- 先杀死娑娜,因为如果她一个人长时间停留会达到治疗友军的效果。

瘟疫之源 vs 琴瑟仙女 Counter Stats

瘟疫之源 Image
winRate
47.6 %
VS
winRate
52.4 %
琴瑟仙女 Image
7.6
< kills >
2.2
6.2
< deaths >
5.5
6.8
< assists >
14.7
1.75
< killingSprees >
0.42
144
< cs >
28
0.18
< dragons >
0.06
0.42
< inhibitors >
0.63
15,634
< physicalDamage >
1,677
3,111
< magicDamage >
8,041
3,945
< trueDamage >
510
22,691
< damageDealt >
10,228
20,649
< damageTaken >
18,662
11,673
< goldEarned >
8,602
1.99
< towers >
2.52
0.05
< barons >
0.02
4,706
< heal >
12,678
12,035
< xp >
10,642
20
< visionScore >
54
9
< wardsPlaced >
24
309
< ccTime >
48

How to Counter 琴瑟仙女 with 瘟疫之源 in LoL

The stats provided here show some strategic 瘟疫之源 against 琴瑟仙女 matchup statistics that may help us appreciate the distinctions between the two. For instance, 瘟疫之源’s KDA ratio ([kills + assists] / deaths) of NaN is better than 琴瑟仙女’s ratio of NaN, indicating that 瘟疫之源 may be more central to his team's team fighting effectiveness than 琴瑟仙女. This observation is in large part a result of the difference in kills.

瘟疫之源 usually has a much larger longest kill spree than his foe does. Typically, he takes a similar amount of damage to 琴瑟仙女. This commonly reflects differing health capacities, yet it can also show that the champion with increased HP has less agility and thus is unable to kite away from additional harm when poked or engaged.

championDifferences.title

伤害数据

瘟疫之源
琴瑟仙女
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

瘟疫之源
琴瑟仙女

championDifferences.whoIsBetter

Both LoL champs are great. Both have their strengths, weaknesses, and counters. In the game's current meta, 瘟疫之源 usually loses when taking on 琴瑟仙女, with a 47.6% win rate. Thus, 瘟疫之源 makes a poor counter to 琴瑟仙女.

While 瘟疫之源 does have a lower win rate than 琴瑟仙女, when they face off with one another, 瘟疫之源 also has a greater level of difficulty that makes him a more challenging character to pick up and master. You should expect to face a difficult match when picking 瘟疫之源 into 琴瑟仙女.

Additionally, 瘟疫之源 also has almost no amount of utility and CC, a similar amount to 琴瑟仙女. This often makes her just as valuable during team fights, especially when fighting champions with a ton of burst damage.

While there isn't one best champion in League of Legends, in 瘟疫之源 vs 琴瑟仙女 matchups, 琴瑟仙女 is the better champion with a lower win rate, more champion depth, and a similar amount of utility to help out your teammates during team fights.

瘟疫之源 is a trash counter to 琴瑟仙女. Make sure you focus your strategy on maximizing your gold income and taking out objectives. If you do that, you should do very well as 瘟疫之源 against 琴瑟仙女.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

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 pick up a few extra lessons on this matchup. If you mind the build and tips presented above, you will grow your win rate by a lot and be that much closer to League of Legends pro players.

瘟疫之源 typically racks up much more CS relative to 琴瑟仙女. Champs who typically don't acquire much CS usualy don't need much CS to be valuable teammates, such as sup champs. These kinds of champions are able to scale well off of their abilities and first items alone. Yet, champions with large amounts of CS, such as hyper-carries, typically require many items to be effective. In either situation, try to exceed the numbers reported here to do well.

The top items to have in your 瘟疫之源 versus 琴瑟仙女 build include 卢安娜的飓风, 鬼索的狂暴之刃, and 界弓. When 瘟疫之源 incorporated at least these three pieces in his build, he did much better versus 琴瑟仙女 than with most other typical item sets. In fact, 瘟疫之源 boasted an average winrate of 47.6% when countering 琴瑟仙女 with these items in his kit.

To have the greatest likelihood of defeating 琴瑟仙女 as 瘟疫之源, 瘟疫之源 players should use the 丛刃, 血之滋味, 眼球收集器, 无情猎手, 气定神闲, and 传说:欢欣 runes from the 主宰 and 精密 rune sets. Out of all the rune combinations players used for 瘟疫之源 vs 琴瑟仙女 counters, this combination of runes yielded the highest win rate. Moreover, these runes averaged a 47.6% winrate overall.

By default, tips, statistics, and builds on how to beat 琴瑟仙女 as 瘟疫之源 are shown for all skill levels, merged. To scope the statistics and builds to a distinct skill level, you can use the selection menu earlier on the page.