Difference between revisions of "Skill"
Line 1: | Line 1: | ||
− | + | Each of the character [[class]]es in [[Diablo III]] have a set of class '''skills'''. There are a lot of skills for each character; more than 50 were shown for the Wizard and Barbarian at Blizzcon in October, 2008. Skills are roughly grouped by type and are slotted into three skill trees... though this arrangement is subject to change during ongoing development. | |
+ | |||
+ | While "skills" is the official name, players often refer to "skills" as "spells," "talents," "abilities," and other such terms. These are just synonyms, and are frequently interchangeable in use. | ||
+ | |||
==Known Skills== | ==Known Skills== | ||
− | + | We know a fair number of skills from seeing them in demonstrations, and from taking notes of them at Blizzcon in October 2008. More than 50 skills are known for the Barbarian and Wizard, while fewer of the Witch Doctor's skills have yet been revealed. Click to the appropriate pages to learn the names and functions of all known skills. | |
+ | |||
** [[Barbarian skills]] | ** [[Barbarian skills]] | ||
− | |||
** [[Witch Doctor skills]] | ** [[Witch Doctor skills]] | ||
− | |||
** [[Wizard skills]] | ** [[Wizard skills]] | ||
− | + | ||
− | + | ||
+ | ==Active and Passive Skills== | ||
+ | |||
+ | Diablo III skills are either "active" or "passive." There are many more passive than active skills. At Blizzcon in October 2008 (a very preliminary build of the game), each skill tree was set up in tiers, with 4 or 5 skills per tier. One or two were active and the rest were passive, on each tier. Thus there were many more passive than active skills. | ||
+ | |||
+ | Active skills are used by clicking their icon, and are generally direct attacks; things like [[Spirit_Skill_Tree#Soul_Harvest|Soul Harvest]], [[Battlemaster_Skill_Tree#Hammer_of_the_Ancients|Hammer of the Ancients]], or [[Arcane_Skill_Tree#Magic_Missile|Magic Missile]]. Active skills attack, or cast a protective armor, or stun monsters, etc. | ||
+ | |||
+ | Passive skills grant the characterr some sort of bonus that is always in effect. Passive skills do not need to be cast to activate them; they give a bonus all the time, as soon as points are placed into them. These are skills and spells like [[Arcane_Skill_Tree#Efficient_Magics|Efficient Magics]] or [[Battlemaster_Skill_Tree#Power_of_the_Battlemaster|Power of the Battlemaster]]. (No passive Witch Doctor skills have yet been named.) Passive skills boost the damage of other spells, or or lower the mana cost of casting them, or increase their duration, etc. Passive skills were often called "masteries" in Diablo II, and that term is still applicable to many of them in Diablo III. | ||
+ | |||
+ | |||
+ | ==Signature Skills== | ||
+ | |||
+ | Skills lie at the core of the characters and propel all combat in Diablo III. For the D3 Team, the skills literally define the character. The team sets out to create what they call "[[WWI_2008:_Denizens_of_Diablo_Panel#Signature_Skills|signature skills]]" -- click that link to read much more about this topic from a panel discussion from the WWI in Paris, when Diablo III was announced. Signature skills are active skills that are very distinctive and evocative of the character. For instance, the design goal of the Diablo III Barbarian is to make a huge, powerful, thundering brute of a melee fighter. So his signature skills are things that crush hordes of enemies in front of him, shake the entire screen, rip holes in the earth, etc. Wizards are deadly, reckless mages, so their signature skills are spells that wreak massive havoc upon monsters with fire, cold, and other elements. | ||
+ | |||
+ | Passive skills are never "signature skills" since even though passive skills are essential, they're not sexy or visually impressive. A passive that adds 20% to your character's damage is going to be noticeable and very useful while you're playing, but it's hard to put into a gameplay movie that will impress casual fans. | ||
+ | |||
+ | |||
+ | |||
+ | ==Skills Define Characters== | ||
+ | |||
+ | D3 Lead Designer Jay Wilson discussed how skills drive game development, and vice versa, in a December 2008 [http://www.1up.com/do/previewPage?pager.offset=1&cId=3172030&p=1 interview with 1up.com]. | ||
+ | |||
+ | ::'''1UP: In creating this game, would you say that the character classes and their powers drive the rest of the game, or are their powers created as a result -- or solution -- to problems presented by the game?''' | ||
+ | |||
+ | ::'''JW:''' Probably the best way to describe it is that initially, when we're doing skills for a class, we're not thinking anything except "what makes this class awesome? Why do I care about this guy?" Then you say, "Because he can hit the ground and create a small localized earthquake that destroys everything in front of him." That sounds pretty awesome; that sounds like a guy that I'd want to play. So early on, that's really our fixation: What is going to make this class sing? But that only really drives the first half-dozen skills. After that, we start getting into what mechanics have we put in the game that we want this class to take advantage of. For example, with the Wizard, we gave her a passive skill that causes enemies to drop mana orbs -- just like health orbs. So that's a mana-recovery mechanic for her; it plays into her resource and plays into the health-orb system. | ||
+ | |||
+ | ::So there, we just said, "We need a recovery mechanism for her -- what would work? Well, we can give her something similar that we already give for health." But then that doesn't mean anything for the Barbarian since he uses a completely different resource. For him, we tend to focus on skills that make him play in a way that's interesting. His "fury resource" is designed to drive the player forward, like a Barbarian, because he's very tough and is a close-quarters combatant. He wants to move forward, because the mechanic is "I have a lot of fury, which helps me deliver a lot of damage, but I'm going to lose it just sitting around." It makes him very aggressive, which is what we wanted out of the character. So that was driven by [the concept of] how do we want this guy to play. Very aggressively, and hence we built this mechanic. | ||
+ | |||
+ | ::And lastly, [there's] the monster design. As we get further and further into the game, our goal is to make monsters that we can't figure out how the player can defeat [with the existing skills] and give the player the tools they need to defeat them. So the design of the monsters has a direct relationship to the design of the classes. That's kind of an ongoing thing; we [decide] "Let's create a monster that has really debilitating rooting attacks that just get you stuck when you encounter them." Then we see that this really screws with the Barbarian, so we give him a skill that lets him break out of roots so that he can counter that. Those things are interesting and allow for the player to have a broader, deeper character. On the other hand, we don't want to go too far -- a lot of mechanics of World of WarCraft are based heavily on control, and we want to make sure that Diablo 3 stays mostly a combat game based mostly on attacks. | ||
+ | |||
[[Category:Skills]] | [[Category:Skills]] | ||
+ | [[category:basics]] |
Revision as of 09:30, 26 December 2008
Each of the character classes in Diablo III have a set of class skills. There are a lot of skills for each character; more than 50 were shown for the Wizard and Barbarian at Blizzcon in October, 2008. Skills are roughly grouped by type and are slotted into three skill trees... though this arrangement is subject to change during ongoing development.
While "skills" is the official name, players often refer to "skills" as "spells," "talents," "abilities," and other such terms. These are just synonyms, and are frequently interchangeable in use.
Known Skills
We know a fair number of skills from seeing them in demonstrations, and from taking notes of them at Blizzcon in October 2008. More than 50 skills are known for the Barbarian and Wizard, while fewer of the Witch Doctor's skills have yet been revealed. Click to the appropriate pages to learn the names and functions of all known skills.
Active and Passive Skills
Diablo III skills are either "active" or "passive." There are many more passive than active skills. At Blizzcon in October 2008 (a very preliminary build of the game), each skill tree was set up in tiers, with 4 or 5 skills per tier. One or two were active and the rest were passive, on each tier. Thus there were many more passive than active skills.
Active skills are used by clicking their icon, and are generally direct attacks; things like Soul Harvest, Hammer of the Ancients, or Magic Missile. Active skills attack, or cast a protective armor, or stun monsters, etc.
Passive skills grant the characterr some sort of bonus that is always in effect. Passive skills do not need to be cast to activate them; they give a bonus all the time, as soon as points are placed into them. These are skills and spells like Efficient Magics or Power of the Battlemaster. (No passive Witch Doctor skills have yet been named.) Passive skills boost the damage of other spells, or or lower the mana cost of casting them, or increase their duration, etc. Passive skills were often called "masteries" in Diablo II, and that term is still applicable to many of them in Diablo III.
Signature Skills
Skills lie at the core of the characters and propel all combat in Diablo III. For the D3 Team, the skills literally define the character. The team sets out to create what they call "signature skills" -- click that link to read much more about this topic from a panel discussion from the WWI in Paris, when Diablo III was announced. Signature skills are active skills that are very distinctive and evocative of the character. For instance, the design goal of the Diablo III Barbarian is to make a huge, powerful, thundering brute of a melee fighter. So his signature skills are things that crush hordes of enemies in front of him, shake the entire screen, rip holes in the earth, etc. Wizards are deadly, reckless mages, so their signature skills are spells that wreak massive havoc upon monsters with fire, cold, and other elements.
Passive skills are never "signature skills" since even though passive skills are essential, they're not sexy or visually impressive. A passive that adds 20% to your character's damage is going to be noticeable and very useful while you're playing, but it's hard to put into a gameplay movie that will impress casual fans.
Skills Define Characters
D3 Lead Designer Jay Wilson discussed how skills drive game development, and vice versa, in a December 2008 interview with 1up.com.
- 1UP: In creating this game, would you say that the character classes and their powers drive the rest of the game, or are their powers created as a result -- or solution -- to problems presented by the game?
- JW: Probably the best way to describe it is that initially, when we're doing skills for a class, we're not thinking anything except "what makes this class awesome? Why do I care about this guy?" Then you say, "Because he can hit the ground and create a small localized earthquake that destroys everything in front of him." That sounds pretty awesome; that sounds like a guy that I'd want to play. So early on, that's really our fixation: What is going to make this class sing? But that only really drives the first half-dozen skills. After that, we start getting into what mechanics have we put in the game that we want this class to take advantage of. For example, with the Wizard, we gave her a passive skill that causes enemies to drop mana orbs -- just like health orbs. So that's a mana-recovery mechanic for her; it plays into her resource and plays into the health-orb system.
- So there, we just said, "We need a recovery mechanism for her -- what would work? Well, we can give her something similar that we already give for health." But then that doesn't mean anything for the Barbarian since he uses a completely different resource. For him, we tend to focus on skills that make him play in a way that's interesting. His "fury resource" is designed to drive the player forward, like a Barbarian, because he's very tough and is a close-quarters combatant. He wants to move forward, because the mechanic is "I have a lot of fury, which helps me deliver a lot of damage, but I'm going to lose it just sitting around." It makes him very aggressive, which is what we wanted out of the character. So that was driven by [the concept of] how do we want this guy to play. Very aggressively, and hence we built this mechanic.
- And lastly, [there's] the monster design. As we get further and further into the game, our goal is to make monsters that we can't figure out how the player can defeat [with the existing skills] and give the player the tools they need to defeat them. So the design of the monsters has a direct relationship to the design of the classes. That's kind of an ongoing thing; we [decide] "Let's create a monster that has really debilitating rooting attacks that just get you stuck when you encounter them." Then we see that this really screws with the Barbarian, so we give him a skill that lets him break out of roots so that he can counter that. Those things are interesting and allow for the player to have a broader, deeper character. On the other hand, we don't want to go too far -- a lot of mechanics of World of WarCraft are based heavily on control, and we want to make sure that Diablo 3 stays mostly a combat game based mostly on attacks.