- 【R冲啊——!!!】的施放距离非常可观。试着预判敌方队伍的走位,以便你能驾着斯嘎尔狠狠教训他们一番。
- 【W暴烈秉性】的最后一次命中会造成比前三次命中更多的伤害——一定要打中喔!
- 克烈可通过击杀小兵来产生一些勇气,但会在与英雄作战时产生更多。
- 在生命值较低时,伊芙琳可利用【恶魔魅影】的治疗效果和【伪装】重返战场,打敌人一个措手不及。
- 在潜行时,要注意你是否被敌方英雄所侦测到。你可以通过敌方英雄头上逐渐变黄和变红的眼睛来识别。
- 【引诱】的准备时间也许看上去有点久,但它所具备的魅惑和魔抗击碎效果会为伊芙琳带来极大优势,所以等待是值得的。
The 暴怒骑士 痛苦之拥 synergy stats shown here demonstrate the areas of his gameplay that do better (or worse) when paired with 痛苦之拥, compared to his overall stats. Significant differences are areas of focus that highlight how his gameplay changes when paired with this other champion.
Overall, 暴怒骑士 sees a very large drop in his KDA (ratio of kills and assists to deaths) when paired with 痛苦之拥. His KDA worsened from NaN to NaN. This drop shows that 痛苦之拥 helps 暴怒骑士 perform poorer in competitive League rounds. Yet, the small difference demonstrates that this performance change is not very impactful.
When 暴怒骑士 is paired with 痛苦之拥, he sees a little increase in his total damage dealt. This difference could signal that 痛苦之拥 provides cover for him to dish out more damage or that her allyship also helps increase the match's duration. Similarly, when 暴怒骑士 is played together with 痛苦之拥 on the same side, he usually scores many fewer killing sprees compared to when he plays on his own. This is contrasting evidence that he is worse when playing with 痛苦之拥.
Additionally, when 暴怒骑士 plays with 痛苦之拥 on the same team, he on average receives a little more damage than when he plays alone. Getting dealt more damage may mean that 痛苦之拥 does a poor job of protecting 暴怒骑士 during team fights.
There is no top champion pairing for 暴怒骑士 that will always be his #1 teammate. Yet, overall, 痛苦之拥 is a pretty good companion for 暴怒骑士. By locking into the same side as 暴怒骑士, she raises their win rate by 1.3% to 52.3%. This signals that there is pretty good strategic relationship between 暴怒骑士 and 痛苦之拥 that results in them performing stronger together than without each other.
痛苦之拥 has a greater difficulty than 暴怒骑士. That means 暴怒骑士 players need to be very careful when finding 痛苦之拥 teammates to play with, as they will require a greater level of skill to be able to work well with you.
Working cooperatively, you will likely see an overall large increase in your team’s capacity to dish out massive AD. When paired, these champs should be able to take down targets with auto-attacks and other AD damage abilities.
Although, by bringing 暴怒骑士 and 痛苦之拥 together, you probably will not be granting your side enough tankyness. We recommend you pick other champions on your team that nullifies this relative disparity in this pairing's playstyle.
Regardless of your 痛苦之拥 ally's skill level, you should focus on increasing your gold income, outlasting your enemies, and taking down objectives. If you follow these simple suggestions, you will do well anyway.
If you would like to learn all of the intricacies of 暴怒骑士 in order to pair well with 痛苦之拥 during both the early game and mid / late game phases of League matches, you should keep reading to pick up some more tricks and insights into this champion pairing. If you pay attention to the build and tips presented above, you should grow your win rate by a lot.
The most crucial items to focus on in your 暴怒骑士 and 痛苦之拥 synergy build include 黑色切割者, 巨型九头蛇, and 焚天. When 暴怒骑士 combined at least these three finished items in his build, he performed significantly better as an ally of 痛苦之拥 than with most other commonly used item sets. In fact, 暴怒骑士 boasted an average winrate of 52.3% helping carry 痛苦之拥 with these items in his kit.
To have the best probability of annihilating your oponents, you should equip the 征服者, 凯旋, 传说:欢欣, 坚毅不倒, 骸骨镀层, and 爆破 runes from the 精密 and 坚决 rune sets. Of all the rune builds that we analyzed for this champion pairing, this sequence of runes resulted in the best win rate. Notably, these runes provided a 52.3% win rate overall.
By default, tips, statistics, and builds on how to synergize 痛苦之拥 with 暴怒骑士 are shown for all ranked divisions combined. To narrow the statistics and builds to a distinct rank, you should use the selection menu located at the top of this page.