* ''Disambiguation: '''Diablo II Fury:''' {{iw|Fury_(skill) Druid skill Fury}} or the {{iw|Fury_(runeword) Runeword Fury}}.''

'''Fury''' is the [[Barbarian]]'s [[resource pool]] in Diablo III. Fury is generated by dealing and taking damage, and spent when skills are used. Barbarians expend Fury when using skills, but may regain as much or more than the skill cost, if it deals a lot of damage.

==Diablo III Fury==

This feature was introduced in the [[BlizzCon 2008]] demo build, and is not present in the gameplay footage from earlier that year, in June at the [[WWI 2008]] when the [[Barbarian]] made his debut.

==Fury Related Skills and Traits==

Various [[Barbarian skills]] and [[Barbarian traits]] assist in Fury generation or slow Fury drain.

==Fury's Evolution==

The visual representation of how much (or little) Fury a Barbarian has accumulated, and that display's connection to the function of the resource, has undergone numerous changes during the development cycle. Changes that will no doubt continue right up until the game's release.

===April 2009===

::'''Mike:''' Let's see... if I had to use a cruel comment, one that I made myself as I was making it, oh "It's the fury traffic light". Because it's three spheres stacked vertically, and no we’re not making them three different colors, but you know as I was doing it I was like oh great, it pretty much well assures us that we are not doing different colors because it will well indeed look like a traffic light. But that's the gist of it, because when you're playing hopefully your vision is in the center of the screen, and this is going to be to your right and down below. So you need to see a very bright graphic that kind of flashes to let you know, that even if you flick your eyes down there you'll see I've got two or three of whatever that is to spend. Really that was the goal. Hopefully Julian and his team will ramp it up, so that, because we want it to catch your eye while you’re doing it, but not be a distraction.

===August 2009===

[[Image:Furydamage.png|thumb|right|250px|The first idea to change the fury system, which was dropped.]]

==Fury Gameplay Issues==

Though we've not seen that much official information yet about Fury, and how this property functions is sure to change during development, some insight into the [[Barbarian]]'s designed play style can be gleaned from analysing how Fury works and reading over the [[Barbarian Skills]].

===Fury Only In Combat===

As the [[D3 Team]] has commented, the D3 Barbarian is designed to be [[melee]] brawler. He's strongest while in [[combat]], and has various skills that increase his powers when he's dealing with multiple enemies, or that only trigger when he scores [[critical hit]]s. Fury ties into this design theme in obvious fashion. The [[Barbarian Skills|Barbarian's Skills]] require Fury to cast, and he can only build up Fury during combat, and Fury drains away quickly when he's not in combat. Hence a Barbarian will want to be in combat as often as possible, and will be at his strongest while fighting. It's a nicely-designed feedback loop.

===Killtrain?===

In a related issue, if Fury drains away quickly after a fight (as it did in the [[BlizzCon 2008]] Demo), Barbarians will want to hurry from battle to battle. This is a big change from the {{iw|Barbarian D2 Barbarian}}, who almost always starts off a fight with his [[mana]] fully charged and his biggest skills ready to go.

===Too Powerful?===

Ironically, Fury might enable skills to be more powerful. If some of the biggest Barbarian skills cost a lot of Fury, that would effectively limit how frequently they could be cast. This would mean the [[D3 Team]] could make those skills massively destructive, compared to a skill that could be used all the time and would be overpowered if it were too strong.

===Bad start - Useless in PvP?===

If Fury is needed to use Barbarian skills in combat, he will be near useless early on, having to resort to auto-attack until enough Fury has built up. This would not only make each encounter less fun, but also be a massive impairment in [[PvP]] combat. Not being able to do anything the first 10 seconds of combat would equal death. [[Bashiok]] has commented on this:[http://diablo.incgamers.com/blog/comments/blizzard-on-fury-and-equal-opportunities/]

::Well there are skills that generate fury, as was said, and there are skills that don’t require any to be used. It's not going to be a situation where you get into a game and have to lumber around using your normal attack until you have enough fury to actually start dealing real damage. That wouldn’t be very fun, and we don’t like things that aren’t fun.

==Hands on Report==

The most detailed report yet filed on Fury comes from a [http://www.diii.net/blog/comments/barbarian-game-play-and-skill-tree-discussion/ BlizzCon Barbarian gameplay report by Flux], posted on [http://www.diii.net/ Diii.net]. A quote:

==World of Warcraft Influence==

The D3 Barbarian's Fury works much like [http://www.worldofwar.net/wiki/Warrior#Warrior_Abilities the "Rage" property] of the Warrior class in ''World of Warcraft''. This isn't surprising, since the D3 Team has frequently cited WoW as a major influence on their design concepts in ''Diablo III'' just like WoW had heavy inspiration from Diablo II.

==Other Resources==

There are not yet any gameplay movies showing Fury in use. In the WWI debut movie from June 2008, the Barbarian had mana, since the bulb was blue and could be seen refilling when no skills were in use. Fury wasn't added into the game until later in 2008, and the Blizzcon gameplay movie was shot from a Wizard's PoV.

==References==

* [http://diablo.incgamers.com/blog/comments/updates-on-fury-instability-and-other-resources/ "Fury balls" are out]. August 4, 2010

* [http://diablo.incgamers.com/blog/comments/blizzard-on-fury-and-equal-opportunities/ Blizzard on Fury and Equal Opportunities]