Background Image
如何赢得瘟疫之源与符文法师的对抗赛瘟疫之源 is in the a tier of champions

瘟疫之源 vs 符文法师

如何在LoL中以瘟疫之源的身份击败符文法师瘟疫之源 is in the a tier of champions
MarksmanAssassin
MageFighter

如何击败符文法师成为瘟疫之源

based on 1,317 瘟疫之源 vs 符文法师 matchups
胜率
51.2 %
kda
2.46
受欢迎度
0.9 %

How We Analyze LoL Champion Counters

At MOBA Champion, we summarize millions of recently ranked LoL games each week. Within our dataset, 瘟疫之源 faced off against 符文法师 1317 times. Including so many matchups for 瘟疫之源 vs 符文法师 gives us faith in our capability to provide actionable stats and a pro build to defeat 符文法师. This counter pairing is somewhat rare. 瘟疫之源 has to counter 符文法师 in only 0.9% of his matches.

瘟疫之源 vs 符文法师 Matchup Summary

瘟疫之源 does a decent job of beating 符文法师. Typically, he wins a acceptable 51.2% of games the champs clash against one another in. In 瘟疫之源 against 符文法师 games, 瘟疫之源’s team is 0.1% more probable to earn first blood. This implies that he most likely will get first blood against 符文法师.

counterTitle

物品

第一项

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

下一个项目

5分钟
短剑吸血鬼节杖

Core 瘟疫之源 Items

22分钟
灭世者的死亡之帽纳什之牙影焰

可选项目

无尽之刃卢安娜的飓风智慧末刃界弓

Summoner Spells

summonerflash summoner spell D
summonerhaste summoner spell F

技能顺序

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

符文

精密致命节奏气定神闲传说:欢欣致命一击
主宰血之滋味寻宝猎人
Attack SpeedAdaptive 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
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
51.2 %
VS
winRate
48.8 %
符文法师 Image
8.6
< kills >
5.9
6.5
< deaths >
5.9
7.4
< assists >
6.4
1.97
< killingSprees >
1.35
149
< cs >
191
0.18
< dragons >
0.12
0.43
< inhibitors >
0.51
16,986
< physicalDamage >
1,030
3,612
< magicDamage >
22,488
4,497
< trueDamage >
307
25,096
< damageDealt >
23,826
21,976
< damageTaken >
27,264
12,323
< goldEarned >
12,154
2.09
< towers >
2.3
0.04
< barons >
0.06
5,110
< heal >
4,602
12,942
< xp >
16,126
21
< visionScore >
19
10
< wardsPlaced >
9
318
< ccTime >
95

How to Counter 符文法师 with 瘟疫之源 in LoL

The stats shown on this page highlight some strategic 瘟疫之源 against 符文法师 counter statistics that may help you explain the distinctions between the pair. As an example, 瘟疫之源’s KDA ratio ([kills + assists] / deaths) of NaN is more than 符文法师’s KDA ratio of NaN, showing that 瘟疫之源 may be more central to his team's team fighting capacity than 符文法师..

瘟疫之源 often has a slightly larger longest killing spree than his matchup does. Typically, he receives less damage than 符文法师. This typically indicates differing health capacities; however, it can also show that the one champion has less agility and thus is not able to flee from further harm when engaged or poked.

championDifferences.title

伤害数据

瘟疫之源
符文法师
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

瘟疫之源
符文法师

championDifferences.whoIsBetter

Both League champions are great. Both have their strengths, weaknesses, and counters. In the game's current meta, 瘟疫之源 usually wins when trying to fight 符文法师, with a 51.2% win rate. Therefore, 瘟疫之源 makes a good counter to 符文法师.

While 瘟疫之源 does have a higher winrate than 符文法师, when on opposite teams, 瘟疫之源 also has a lower learning curve that makes him a less challenging champ to pick up and master. You should be careful when picking 瘟疫之源 into 符文法师.

Additionally, 瘟疫之源 has only a small amount of CC and other utility, a similar amount to 符文法师. This often makes her just as valuable during team fights, especially when fighting champions with a lot of burst damage.

While there is not one best champion in League of Legends, in 瘟疫之源 vs 符文法师 matchups, 瘟疫之源 is the better champ with a higher win rate, less champion complexity, and a similar amount of utility to help out your teammates during teamfights.

瘟疫之源 is a decent counter for 符文法师. Make sure you focus your strategy on increasing your gold and cs and clearing objectives. If you do that, you should do very well as 瘟疫之源 against 符文法师.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

If you would like to learn all of the intricacies of 瘟疫之源 to counter 符文法师 during both the laning and mid / late game phases of League of Legends, you should keep reading to gather a few extra tips and tricks for this matchup. If you listen to the build and stats displayed here, you will grow your win rate significantly and be closer to League of Legends pro players.

瘟疫之源 typically accumulates a similar amount of CS relative to 符文法师. Champs who typically don't get many minion kills often don't have to have much CS to be effective, such as support champions. These kinds of champions are able to scale well off of their skills, stats, and first items alone. Yet, champs with a lot of CS, such as hyper-carries, often have to have many items to be effective. In either case, try to do better than the numbers displayed on this page to do well.

The most important items to prioritize in your 瘟疫之源 versus 符文法师 build include 灭世者的死亡之帽, 纳什之牙, and 影焰. When 瘟疫之源 combined at least these three items in his build, he did much better when fighting 符文法师 than with many other commonly used item sets. In fact, 瘟疫之源 had an average win rate of 51.2% when countering 符文法师 with this counter build.

To have the greatest chance of crushing 符文法师 as 瘟疫之源, 瘟疫之源 players should use the 致命节奏, 气定神闲, 传说:欢欣, 致命一击, 血之滋味, and 寻宝猎人 runes from the 精密 and 主宰 rune sets. Of all the runes we have analyed for 瘟疫之源 vs 符文法师 counterpicks, this composite of runes yielded the highest win rate. Notably, these runes gave a 51.2% win rate overall.

By default, tips, statistics, and builds on how to beat 符文法师 as 瘟疫之源 are given for all ranked divisions. If you want to narrow the stats and builds to an individual rank, you may use the selection menu earlier on the page.