- 种子可以为你的队伍提供视野,请好好利用。
- 在你的技能施放之后,再往你的技能路径上播下种子,可以确保你的种子能够百分百变成植物。
- 婕拉是一个出色的伏击手——寻找时机,然后在草丛里布下陷阱,再诱引敌人进来。
- 只有中了劫的影分身的【E影奥义!鬼斩】才会被减速,而中了劫的【E影奥义!鬼斩】则不会。
- 劫的【Q影奥义!诸刃】如果在命中敌方英雄之前,穿过了其它单位的话,那么它的伤害值会降低。
- 提升攻击力的装备能提升劫的整体输出,因此在对抗劫时,护甲的作用将非常明显。
- 在劫使用了他的【W影奥义!分身】之后,他将陷入最无力的状态,因为他的伤害、减速、和机动性都依靠这个技能。
The stat comparisons shown on this page highlight several strategic 荆棘之兴 versus 影流之主 matchup statistics that can help you understand the differences and similarities between the pair. For instance, 荆棘之兴’s KDA ratio ([kills + assists] / deaths) of NaN is greater than 影流之主’s KDA ratio of NaN, demonstrating that 荆棘之兴 may be more central to her team's team fighting effectiveness than 影流之主. This observation is largely caused by the differences in assists.
荆棘之兴 normally has a significantly smaller longest kill spree than her matchup does. Typically, she takes less damage than 影流之主. This typically indicates differing health capacities, yet it can also imply that the one champion has less mobility and thus is not able to escape further damage when poked or engaged.
Both League champions are great champions. Both champs have their strengths, weaknesses, and counters. In League's current meta, 荆棘之兴 usually wins when taking on 影流之主, with a 54.3% win rate. Thus, 荆棘之兴 makes a great counter for 影流之主.
While 荆棘之兴 does have a much higher win rate than 影流之主, when they face off with one another, 荆棘之兴 also has a greater learning curve that makes her a more time consuming champion to develop with. You don't need to be too worried when picking 荆棘之兴 into 影流之主as her relative depth means you may not be able to unleash her full potential without a significant amount of practice beforehand.
Additionally, 荆棘之兴 also 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 for every situation in League of Legends, in 荆棘之兴 vs 影流之主 matchups, 荆棘之兴 is the better champion with a noticably higher win rate, similar champion depth, and a similar amount of utility to help out your team members during late stage team fights.
荆棘之兴 is a great counter to 影流之主. Focus your actions on keeping up your CS and clearing objectives. If you do that, you should be able to stand on your own as 荆棘之兴 against 影流之主.
To truly master 荆棘之兴 in order to counter 影流之主 during both the early game and mid / late game phases of League of Legends, you should continue reading to learn a few extra tips and tricks for this matchup. If you pay attention to the build and suggestions displayed above, you will grow your win rate by a lot and be closer to League of Legends pro players.
荆棘之兴 on average picks up less CS relative to 影流之主. Champs who typically don't earn many minion kills typically don't have to have much CS to be effective, such as sup champs. They are capable of scaling well off of their skills, stats, and first items alone. Yet, champs with large amounts of CS, such as hyper-carries, typically require several high cost 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 荆棘之兴 combined at least these three pieces in her build, she performed significantly better countering 影流之主 than with most other commonly used builds. In fact, 荆棘之兴 had an average win rate of 54.3% when playing against 影流之主 with this build.
To have the best probability of coming out on top against 影流之主 as 荆棘之兴, 荆棘之兴 players should equip the 奥术彗星, 法力流系带, 超然, 焦灼, 无情猎手, and 血之滋味 runes from the 巫术 and 主宰 rune sets. Out of all the rune combinations players used for 荆棘之兴 vs 影流之主 counterpicks, this combination of runes resulted in the highest win rate. In fact, these runes averaged a 54.3% win rate overall.
By default, tips, stats, and builds on how to beat 影流之主 as 荆棘之兴 are given for all skill levels, merged. If you would like to filter the stats and builds to an individual skill level, you should use the selection menu located at the top of this page.