Background Image
如何赢得风暴之怒与含羞蓓蕾的对抗赛风暴之怒 is in the s tier of champions

风暴之怒 vs 含羞蓓蕾

如何在LoL中以风暴之怒的身份击败含羞蓓蕾风暴之怒 is in the s tier of champions
SupportMage
FighterMage

如何击败含羞蓓蕾成为风暴之怒

based on 5,634 风暴之怒 vs 含羞蓓蕾 matchups
胜率
47.6 %
kda
3.24
受欢迎度
5.9 %

How We Analyze LoL Champion Counters

We at MOBA Champion evaluate millions of recently ranked League of Legends games each week. In our dataset, 风暴之怒 engaged 含羞蓓蕾 5634 times. Having so many games with 风暴之怒 vs 含羞蓓蕾 gives us confidence in our capability to provide actionable stats and a recommended build to suppress 含羞蓓蕾. This counter pairing is fairly uncommon. 风暴之怒 encounters 含羞蓓蕾 in only 5.9% of her rounds.

风暴之怒 vs 含羞蓓蕾 Matchup Summary

Unfortunately, 风暴之怒 does a poor job of beating 含羞蓓蕾. On average, she wins a lowly 47.6% of the time the champs fight each other in. In 风暴之怒 against 含羞蓓蕾 matches, 风暴之怒’s team is 0.0% more likely to obtain first blood. This implies that she probably will be able to get first blood versus 含羞蓓蕾.

counterTitle

物品

第一项

期望时间
生命药水云游图鉴

下一个项目

5分钟
增幅典籍班德尔玻璃镜

Core 风暴之怒 Items

22分钟
救赎流水法杖月石再生器

可选项目

黎明核心米凯尔的祝福炽热香炉帝国指令

Summoner Spells

summonerexhaust summoner spell D
summonerflash summoner spell F

技能顺序

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

符文

主宰丛刃恶意中伤僵尸守卫无情猎手
巫术迅捷焦灼
Ability HasteAdaptive ForceArmor
风暴之怒's passive ability p
风暴之怒's q ability q
风暴之怒's w ability w
风暴之怒's e ability e
风暴之怒's ultimate ability r
1
W
2
Q
3
E
4
W
5
W
6
R
7
W
8
E
9
W
10
E
11
R
12
E
13
E
14
Q
15
Q
16
R

Guide to Countering 含羞蓓蕾 as 风暴之怒

Tips for Playing as 风暴之怒 against 含羞蓓蕾

- 迦娜的终极技能可以将敌人从受伤友军身边推开或者甚至打散敌人。

- 风暴之眼可以用于友方的防御塔。

- 快速发出飓风呼啸(不要蓄力)可以很好的控制对方队伍。

风暴之怒 vs 含羞蓓蕾 Counter Stats

风暴之怒 Image
winRate
47.6 %
VS
winRate
52.4 %
含羞蓓蕾 Image
1.4
< kills >
6.1
4.9
< deaths >
5.2
14.5
< assists >
7.8
0.25
< killingSprees >
1.39
27
< cs >
46
0.04
< dragons >
1.4
0.55
< inhibitors >
0.45
987
< physicalDamage >
774
6,462
< magicDamage >
15,661
445
< trueDamage >
4,632
7,895
< damageDealt >
21,069
17,507
< damageTaken >
40,378
8,328
< goldEarned >
11,954
2.17
< towers >
1.39
0.01
< barons >
0.34
8,008
< heal >
23,211
10,585
< xp >
14,087
63
< visionScore >
21
27
< wardsPlaced >
6
179
< ccTime >
427

How to Counter 含羞蓓蕾 with 风暴之怒 in LoL

The stat comparisons shown here show some vital 风暴之怒 versus 含羞蓓蕾 matchup stats that may help us figure out the differences and similarities between the pair. As an example, 风暴之怒’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 capability than 含羞蓓蕾. This observation is largely fueled by the differences in assists.

风暴之怒 usually has a significantly smaller longest kill spree than her enemy does. Typically, she receives less damage than 含羞蓓蕾. This often reflects differing health capacities; however, it can also show that the one champ has less agility and thus is unable to escape additional damage when poked or engaged.

championDifferences.title

伤害数据

风暴之怒
含羞蓓蕾
物理伤害
魔法伤害
真实伤害

championDifferences.playStyle.title

风暴之怒
含羞蓓蕾

championDifferences.whoIsBetter

Both LoL champs are great champions. Both champs have their pros and cons. In the game's current meta, 风暴之怒 usually loses when trying to fight 含羞蓓蕾, with a 47.6% win rate. Thus, 风暴之怒 makes a bad counter to 含羞蓓蕾.

While 风暴之怒 does have a lower winrate than 含羞蓓蕾, when facing one another, 风暴之怒 also has a lower level of difficulty that makes her a less challenging character to pick up and master. You should expect to face a difficult match when picking 风暴之怒 into 含羞蓓蕾as her relative depth means that you may not be able to reach her full potential without a significant amount of practice beforehand.

Additionally, 风暴之怒 has a great deal of utility and CC, a similar amount to 含羞蓓蕾. This often makes her just as valuable during team fights, especially when facing champions with a ton of burst damage.

While there is not one best champion overall in League of Legends, in 风暴之怒 vs 含羞蓓蕾 matchups, 含羞蓓蕾 is the better champ with a lower win rate, less champion complexity, and a similar amount of utility to help out your allies during late stage team fights.

风暴之怒 is a bad counter for 含羞蓓蕾. You will do well by focussing your actions on increasing your gold income and clearing objectives. If you do that, you should hold your own as 风暴之怒 against 含羞蓓蕾.

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

additionalInformation.readMore

To truly master 风暴之怒 to counter 含羞蓓蕾 during both the lane and mid / late game phases of League of Legends, you should continue reading to gather a few extra tips and tricks for this matchup. If you listen to the build and stats displayed here, you will increase your win rate by a lot and be that much closer to League of Legends pro players.

风暴之怒 typically racks up less CS as 含羞蓓蕾. Champions who on average don't get much CS typically don't require much CS to be effective, such as support champions. They 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, usually have to have several high cost items to be effective. In either case, try to exceed the numbers shown here to do well.

The ideal items to prioritize in your 风暴之怒 versus 含羞蓓蕾 build consist of 救赎, 流水法杖, and 月石再生器. When 风暴之怒 combined at least these three items in her build, she did significantly better countering 含羞蓓蕾 than with most other common item sets. In fact, 风暴之怒 boasted an average win rate of 47.6% when countering 含羞蓓蕾 with this build.

To have the best probability of annihilating 含羞蓓蕾 as 风暴之怒, you should take the 丛刃, 恶意中伤, 僵尸守卫, 无情猎手, 迅捷, and 焦灼 runes from the 主宰 and 巫术 rune sets. Out of all the rune combinations we have analyed for 风暴之怒 vs 含羞蓓蕾 battles, this order of runes yielded the best win rate. Moreover, these runes averaged a 47.6% winrate overall.

By default, tips, stats, and builds on how to beat 含羞蓓蕾 as 风暴之怒 are displayed for all ranked divisions combined. If you would like to scope the statistics and builds to a distinct player tier, you can use the selection menu at the top of this page.