Background Image
如何赢得翠神与荆棘之兴的对抗赛翠神 is in the s tier of champions

翠神 vs 荆棘之兴

如何在LoL中以翠神的身份击败荆棘之兴翠神 is in the s tier of champions
SupportMage
MageSupport

如何击败荆棘之兴成为翠神

based on 1,707 翠神 vs 荆棘之兴 matchups
胜率
49.8 %
kda
3.08
受欢迎度
4.2 %

How We Analyze LoL Champion Counters

We get our counter statistics from the millions of recently rated League rounds that we analyze every week. This guide on how to beat 荆棘之兴 as 翠神 resulted from an evaluation of 1707 ranked matches where both champions engaged each other. This counter matchup is somewhat uncommon. 翠神 has to counter 荆棘之兴 in only 4.2% of his rounds.

翠神 vs 荆棘之兴 Matchup Summary

翠神 does a average job of beating 荆棘之兴. On average, he wins a acceptable 49.8% of the time the champs fight each other in. In 翠神 vs 荆棘之兴 games, 翠神’s team is 0.0% more probable to obtain first blood. This implies that he most likely will get first blood against 荆棘之兴.

counterTitle

物品

第一项

期望时间
踏苔蜥幼苗生命药水

下一个项目

5分钟
红水晶明朗之靴

Core 翠神 Items

22分钟
舒瑞娅的战歌救赎月石再生器

可选项目

中娅沙漏炽热香炉黎明核心米凯尔的祝福

Summoner Spells

summonerflash summoner spell D
summonersmite summoner spell F

技能顺序

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

符文

巫术召唤:艾黎灵光披风超然水上行走
主宰眼球收集器无情猎手
Ability HasteAdaptive 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 荆棘之兴

- 使用【W揠苗助攻】来埋下伏击的伏笔!

- 尽量用一记精妙的【Q根深敌固】接【E种豆得瓜】来帮助友军。

- 小菊可以格挡技巧射击并拖延敌人。使用她来为你的友军阻挡伤害!

Advice to Win Against 荆棘之兴

- 如果婕拉把植物放在过于远离她自己的地方,贴到她身边将是个明智的举动。

- 把战斗转移到一个不同的地方,就能让婕拉无法有效利用她积累的种子。

- 植物会从攻击和效果中受到固定伤害,类似守卫。它们本身也会快速消亡。

- 婕拉的【W狂野生长】所播下的种子更大一些,颜色也有所不同,并且会为她的团队提供小幅视野。

- 你可以通过踩掉婕拉的种子来摧毁它们。如果她想在你要这么做时把种子长成植物,那么就在最后关头撤退。

翠神 vs 荆棘之兴 Counter Stats

翠神 Image
winRate
49.8 %
VS
winRate
50.2 %
荆棘之兴 Image
2.4
< kills >
3.4
5
< deaths >
5.9
13
< assists >
10.1
0.52
< killingSprees >
0.74
19
< cs >
54
1.08
< dragons >
0.11
0.49
< inhibitors >
0.47
2,765
< physicalDamage >
1,004
6,027
< magicDamage >
18,940
1,027
< trueDamage >
898
9,821
< damageDealt >
20,843
18,359
< damageTaken >
17,794
9,943
< goldEarned >
9,505
1.74
< towers >
1.8
0.34
< barons >
0.02
6,550
< heal >
2,014
12,878
< xp >
10,932
26
< visionScore >
59
7
< wardsPlaced >
25
267
< ccTime >
291

How to Counter 荆棘之兴 with 翠神 in LoL

The stat comparisons provided here clarify some valuable 翠神 vs. 荆棘之兴 counter statistics that may help you explain the distinctions between the two. 翠神’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 荆棘之兴..

翠神 usually has a similar longest killing spree as his opponent does. Typically, he takes a similar amount of damage to 荆棘之兴. This is usually reflective of differing health capacities, yet it can also imply that the one champ has less mobility and thus is unable to escape further harm when engaged or poked.

championDifferences.title

伤害数据

翠神
荆棘之兴
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

翠神
荆棘之兴

championDifferences.whoIsBetter

Both League of Legends champs are great champions. Both have their strengths, weaknesses, and counters. In League's current meta, 翠神 usually fairs equally well when facing off against 荆棘之兴, with a 49.8% win rate. Therefore, 翠神 makes an ok counter for 荆棘之兴.

While 翠神 does have a lower win rate compared to 荆棘之兴, when on opposite teams, 翠神 also has a greater level of difficulty that makes him a more challenging champ to learn and master. You should be careful when picking 翠神 into 荆棘之兴as his relative depth means you may not be able to reach his full potential without a lot of practice beforehand.

Moreover, 翠神 has some amount of utility and CC, a similar amount to 荆棘之兴. This makes her just as valuable during teamfights, especially when facing champions with a ton of burst damage.

While there isn't one best champion overall in League of Legends, in 翠神 vs 荆棘之兴 matchups, 荆棘之兴 is the better champ with a similar win rate, similar champion depth, and a similar amount of utility to help out your allies during teamfights.

翠神 is a somewhat poor counter to 荆棘之兴. Focus your actions on keeping up your CS and taking out objectives. If you can do that, you should hold your own as 翠神 against 荆棘之兴.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

To learn all of the intricacies of 翠神 to counter 荆棘之兴 during both the early game and mid / late game phases of League of Legends, you should keep reading to learn a few extra tricks and insights into this matchup. If you mind the build and stats presented above, you will increase your win rate by a lot and be closer to League of Legends pro players.

翠神 most often racks up less CS compared to 荆棘之兴. Champions who on average don't get many minion kills typically don't require much CS to be valuable teammates, such as support champions. They are capable of scaling well off of their abilities and first items alone. Yet, champions with a lot of CS, such as hyper-carries, typically require many items to be effective. In either situation, try to surpass the values displayed here to do well.

The ideal items to use in your 翠神 versus 荆棘之兴 build include 舒瑞娅的战歌, 救赎, and 月石再生器. When 翠神 bought at least these three items in his build, he did significantly better when facing 荆棘之兴 than with most other commonly used counter builds. In fact, 翠神 boasted an average win rate of 49.8% when playing against 荆棘之兴 with this build.

To have the highest chance of vanquishing 荆棘之兴 as 翠神, 翠神 players should take the 召唤:艾黎, 灵光披风, 超然, 水上行走, 眼球收集器, and 无情猎手 runes from the 巫术 and 主宰 rune sets. Out of all the rune combinations we have analyed for 翠神 vs 荆棘之兴 clashes, this order of runes resulted in the best win rate. Moreover, these runes provided a 49.8% winrate overall.

By default, tips, statistics, and builds on how to beat 荆棘之兴 as 翠神 are presented for all skill levels combined. If you would like to filter the statistics and builds to a specific rank, you should use the selection menu earlier on the page.