All posts in this series can be found here.
As promised at the end of my last post on Warlords heals, the next step would be to analyze more complex rotations involving multiple spells. This post will go into single-target healing rotations for each class, building on the overview of individual spells I did previously. Single-target rotations are only one slice of the healing picture, but one of the more readily quantifiable ones, making them a good place to start. Also, the need to directly heal tanks is expected to be a much bigger part of Warlords than it was in Mists.
On Modeling Healing Rotations
One difficulty in expressing numerical results of combined healing spells, especially cross-class, is that healers don’t use “rotations” in the same way DPS do. They’re constantly reacting to the demands of the encounter and modulating output based on that. A model of a pure max-output rotation akin to DPS is slightly informative, but rather limited because that’s an unusual mode of casting. Since you spend nearly all your time somewhere in the middle of the sliding scale of mana usage vs. healing output, it’s hard to nail down exactly what numbers to measure or model. We can choose cases to model that are informative, but it takes more thought to motivate the decision of what those are. The assumptions also have to be made clear so people understand what the numbers represent.
The usual way I approach this is anticipated by earlier posts in this series, and should also be familiar to anyone who used my TreeCalcs sheet in Wrath/Cata/Mists (for this post, I actually put the heal chart from the prior post into the WrathCalcs/TreeCalcs shell). I assume a certain subset of spells are used whenever possible: on cooldown, whenever a HoT expires, or whenever procs/resources allow. All available cast time that’s left over is for “filler” or no-cooldown/spammable spells. In the case of the single-target model, the filler time is divided between a) the cheap direct heal, b) the expensive direct heal, and c) casting nothing. This flexibility in how to allocate the filler time is needed for two important purposes:
- One class filling all time with its cheap heal (for example) may not be parallel to another class filling with its cheap heal. The first class might do less healing but also use less mana in that comparison, but then equal the other class in both healing and mana consumption if it mixed in the expensive heal some. Every class has a different mana vs. healing profile, and being able to adjust spell usage allows more sensible comparisons.
- It provides a basis for evaluating mana. As discussed extensively in the post on mana, mana usage affects your use of non-cooldown heals much more than it affects your use of cooldown-bearing heals. In a more concrete framework like a rotation model, you can evaluate exactly what mana lets you do by varying the spell usage correspondingly. The conceptual chart in the final section of that post, describing healing done as a function of mana, will be revisited in this post.
This is of course idealized, as is unavoidable when theorycrafting healing, but it’s useful in a lot of ways. In particular, while in various low-healing situations you might use spells more in isolation and not nonstop like in a rotation model, we already have HPCT and HPM info on individual spells. Those can be looked up anytime on the spell chart form the last post. Models of rotations let us find out more about what happens when cooldowns and cast time become a limiting factor in how much healing you can do.
I’ve not yet modeled every talent and glyph combination for every class, but I’ve tried to include the ones that were especially relevant to the current analysis.
I’ve been doing a lot of in-game testing of spells lately, as a part of making spreadsheets and other projects. In particular, with the new beta, I’m more inclined to vet the info for any spell I look at by measuring in-game, rather than simply putting the coefficient from wod.wowhead into a spreadsheet, because:
- The designers are changing spells a lot, and tooltips are out of date much more often than on live.
- The passives, talents, and Draenor Perks aren’t all familiar, and you have make sure you know what all needs to be multiplied in between the coefficient in the data and the final damage amount.
- There are frequent bugs on beta, and actually testing means you can help catch/report them.
There are a lot of various techniques and tricks you get used to for doing this stuff quickly, but I wanted to dash off a quick post on one that both saves work and is mathematically interesting. It looks like Theck is starting a series on general concepts of theorycrafting, and while I don’t expect to do anything that elaborate, I do want to write down ideas that are familiar to me but might be helpful to people who are just getting into it.
Just in case anyone reads this blog other than being linked to it from my twitter or anywhere else, I should mention that I co-wrote a post today, with Dayani from Healiocentric, that’s over on her site. Go take a look.
All posts in this series can be found here.
I’ve been waiting since alpha started to sink my teeth into the numbers of six new healing toolkits. Rather, I’ve been doing so for a while, but trying to get the information to the point where I can write about it in an organized way. I’ve been assembling a large spreadsheet of 6.0 heals since even before alpha started (since we had spell data). It’s mostly for my own purposes, to have a good reference for the properties of all the spells. I’ll post it here for people who want the full detailed background, while using the post to discuss various interesting points. The goal for this, and ensuing posts, is to work both for people who don’t peruse the actual sheet and just read the post (so I copy various numbers and such into the post), and also for people who want to look further into the sheet after I use a post to highlight some interesting points.
This is the sheet (download).
It’s more utilitarian than user-friendly; as I said, it’s mostly an easy place for me to store/compare numbers (it’s not a character setup tool). The main focus for each heal is to compute an index for their HPM and HPCT (healing per unit cast time). In some cases, for non-spammable heals, HPCD (healing per cooldown time) is used to measure how much healing is added if the spell is used as often as possible. Some notes:
- All of these are in unusual units, which is fine since they’re only meant to be compared against each other. For people who want details, HPCT and HPCD are in units of (spellpower coefficient)/seconds, and HPM is in units of (spellpower coefficient)/(% base mana cost).
- All heals use the haste, crit, mastery, and multistrike values from the top of the sheet (Multistrike affects all spells equally so is not that interesting, except that Holy Priest heals get 25% more benefit).
- Mastery is also in unusual units. “0.2″ means, the amount of mastery stat that’s equivalent to 20% crit, or what was once called “20 points of mastery.”
- The main computation in each row is to combine a spell’s spellpower coefficient from wod.wowhead.com with haste/crit/mastery/MS, any class passives or other auras, and any Draenor perks or other bonuses, to compute an overall effective spellpower coefficient.
- I make assumptions as needed about talents, glyphs, and other variables. Usually the guideline is, a spell’s row in the sheet represents whatever case I was most interested in when thinking about how it would be used in practice.
- Similarly, sometimes a spell has multiple entries if I want to see e.g. both glyphed and unglyphed, or if I want to see a combination of spells in a single row.
- Blanket disclaimer: the beta build is changing often, changes aren’t always documented, some spells’ behaviors don’t match their tooltip data, and so on. I got some help from Dayani of Healiocentric, and we vetted all of the rows against in-game behavior in beta builds 18505 or 18522 (often with the techniques described here), and are continually updating them.
On to some of the interesting patterns. Continue reading
Previous posts in this series can be found here.
This is an interim update covering a few loosely related topics about 6.0. Not exactly a normal post in this series that analyzes some point of theory in detail, but I wanted to catch up on a few issues, and I figured most of the same people who read this series will be interested in this.
6.0 Regen Math
Now that I’ve gotten to play the alpha some, I have some more concrete numbers on regen in 6.0.
As a reminder, regen currently (5.0) consists of base regen and spirit regen. Base regen is an amount of MP5 equal to 2% of your max mana (6000 MP5 currently). Spirit regen is 0.564 MP5 per Spirit, in combat.
Two important things are happening to Spirit in 6.0:
- Each point of Spirit is worth substantially more MP5 (2.061 MP5 in combat). This increase is even more dramatic when you consider that mana pools will be smaller by factor of around 2. Adjusted for this deflation, the real value of Spirit (proportional to the size of your mana bar) is about 6.85 times stronger in 6.0 than it is in 5.0.
- You will have much less Spirit, even after controlling for the item squish. This is because you will only have it on a few slots: rings, necks, cloaks, and possibly trinkets.
The end result is that these two effects, roughly speaking, cancel each other out. The amount of regen you get from Spirit, controlling for the changed size of your mana bar, will be in the same ballpark as it is now (i.e. at a comparable gear level, your mana bar will “look” like it refills at around the same rate).
My first post when the new Moonkin patch notes were revealed was about explaining them and giving the highlights, but not too much in-depth analysis (read that one first if you haven’t, though). But I’ve been thinking about the details of the rotation a good bit. To the extent possible on paper that is, without an actual alpha to play, but I got pretty far on a reasonable WrathCalcs model. So here are some more detailed observations on how this rotation will play. You can think of this as, how the basics of my Moonkin guide would look if this rotation were going live right now.
A few things have been mentioned by Celestalon on twitter since the last post.
- The cycle will now be 40s long instead of 30.
- The DoTs are now 40s and 20s long to correspond to that (instead of 32 and 16).
- The cycle will pause briefly at the top. Instead of a sine wave oscillating from -100 to 100 energy, it will go from -110 to +110, but with a cap on the bonus at 100. This will result in roughly a 5 second pause at the peak of each Eclipse.
- Starsurge will be instant cast.
Moonkin are preserving one aspect of gameplay that is otherwise being removed from most classes for causing too much complexity: DoT snapshotting (DoTs will snapshot their Eclipse bonus, and presumably their mastery level at cast, but not other stats like spellpower). Unsurprising then, that some of the more finicky bits of timing that are likely to appear in the new rotation are related to snapshotting.
After a conspicuous lack of Balance changes in the 6.0 notes before now, the newest update shows what they’ve been working on: a complete rework of the class.
There is still an Eclipse bar, but it’s changed in two important ways:
- Its movement is no longer affected by your casts at all; it cycles on its own between the two endpoints, making one complete loop every 30 seconds.
- Your Arcane and Nature damage bonuses vary continuously based on the Eclipse marker. At the midpoint, you get half of your mastery bonus to either element, and at an endpoint, the full mastery bonus to one element only.
So, some things stay the same. Your Eclipse cycles back and forth regularly, and you cast Starfire half the time and Wrath half the time. You use Starsurge regularly (see below) in either half of the rotation, since it’s buffed by either bonus. You maintain DoTs, and casting them when you have a high Eclipse bonus is still beneficial (even though DoTs will no longer snapshot most effects, they will still snapshot Eclipse).
The reason cited for the change is that Moonkin was daunting to initially learn, but relatively easy to play well once you understood it (which is the reverse of what you usually want in a class). I think this is generally correct, subject to some details of Eclipse management at the highest levels of play. Eclipse is confusing to explain and understand at first, to new players to the class, and the new version hopefully won’t have this problem.
In addition to the stated problem related to the learning curve, the 5.0 Eclipse had some issues that commonly caused frustration among players. I tended to pinpoint the problem as being related to Nature’s Grace–a major DPS buff that lasted a fixed amount of time and whose uptime was determined by your ability to race between Eclipses as quickly as possible. This made the class somewhat reliant on haste to avoid being stuck outside of NG, and severely penalized the class for any time not spent advanced in the Eclipse bar, in particular, movement and AoE. Even before seeing these changes, I’d suggested to the devs that they remove Nature’s Grace in 6.0. With the new constantly-oscillating Eclipse, they are not only removing Nature’s Grace, but making it so that your choice of what to cast doesn’t even effect the uptime of an Eclipse bonus. This should make the performance of the class much more stable.
Previous posts in this series can be found here.
This is the first post in this series that’s explicitly about new mechanics in Warlords. As a general disclaimer, at the moment there is not yet a public alpha, so all we have to go on is information in patch notes and spell data. So I while I will be going into some numbers in this post, keep in mind that anything can change. The point will be more about how to understand active mana regen, and not as much, in particular, about comparing the relative strengths of each class’s new mechanic.
The Active Regen Spells
- Druid: Innervate. The Druid casts Innervate (2 seconds), which lasts 8 seconds or until the Druid spends mana on a healing spell. If it runs for the full duration, it regenerates 5% mana.
- Shaman: Telluric Currents. Lightning Bolt casts return 1.25% mana.
- Monk: Crackling Jade Lightning returns 2% mana after a full-duration channel, which takes 4 seconds. Monks also still have Mana Tea.
- Paladin: Divine Plea costs 3 Holy Power, and returns 7% mana.
- Disc Priest: Penance, when used offensively, returns 1.1% mana per hit (and no longer Atones).
- Holy Priest: When in Chastise, Smite and Holy Fire each return 0.75% mana. Notably, Chakra shifts have a 10s cooldown.
The idea behind these is pretty easy to see: give every healer an ability that lets them choose to regain some mana, at the cost of giving some opportunity to heal. This is a response by Blizzard to the problem that current mana-related abilities tend to involve little or no decisionmaking; you generally simply use them on cooldown. They were prime candidates for removal during the ability-culling process, and that is what happened at first. And while there was no huge problem with that (mana is still interesting due to the inherent choice in choosing how to spend it), abilities whose purpose is to regain mana are definitely a place to add something to healer gameplay.
My last post discussed the basics of picking gear in the Loot 2.0 system. It emphasized that a max level character can be geared up rapidly with good rares if you know what to look for and make use of the enchanting system. I want to add a few small points that can make a big difference in how effectively you can use enchanter, especially with limited resources.
A rare item has up to 4 primary affixes and 2 secondary, as discussed before. Each slot has a pool of primary affixes from which it can draw its 4. This is a helpful resource I linked before to see what they are. When you enchant a primary stat, the item can draw the new stat from the usual primary pool (you can click the “?” icon at the enchanter to see all the possibilities in advance). However, the full array of possible affixes is not always available, because certain affixes are mutually exclusive.
In particular, an item can’t have two +skill bonuses or two +element bonuses. So when enchanting a particular stat, if one of the other stats being left on the item is a +skill or +element affix, all of those will be removed from the enchanting pool. This can be used to your advantage when enchanting. Conversely, if an item does not have a +skill or +element affix (except possibly for the one being enchanted), and those are available in the slot, there will be a very long list of possible reforges. This works against you, even if it’s not the +skill or +element that you’re going for. In that situation you might reconsider enchanting the item unless you are willing to spend a large amount of gold and materials rolling the stat you want out of a large pool.
Edit: added a little bit more to this, in a separate post here.
The “Loot 2.0″ system that is the centerpiece of Diablo 3 2.0 makes acquiring gear both more fun and more interesting. The addition of a few new stats, and the enchanting system in particular, means that a little bit of understanding of the system goes a long way in helping you gear up quite quickly once you hit max level. I’ll first give an overview of important stats, and then some practical tips on how to go about putting it all together. In particular, the “Damage” and “Toughness” scores, while they have their uses in making evaluations, can limit your gear progress if you rely on them too much without understanding the underlying stats.
Your character sheet’s “damage” score takes into account your weapon damage, primary stat (“Main”), crit chance (“CC”), crit damage (“CD”), and attack speed (“IAS”) bonuses. Since all damaging skills also scale with those stats (some exceptions for IAS, see below) it is a good starting proxy for how much damage you can output. However, there are some important reasons not to simply rely on the Damage score when looking for upgrades. Here are the most prominent ones:
- The “[Element] skills deal X% more damage” affix. This works exactly as advertised, and if your build does most of its damage with skills of a particular element, adds a lot of damage that’s not reflected on your character sheet. This gives a strong incentive in Reaper of Souls to try to choose builds that focus on one elemental damage type. If you do all your damage with one element, and you mouseover a pair of bracers with +15% to that element, then even if they show a -5% Damage loss in the comparison, you should think of them as a 10% damage upgrade.
- The “Increase [Skill] damage by X%” affix. Similarly, you can probably imagine how to use this. It’s sometimes hard to leverage if your damage is spread between a few different skills, but value it highly if you use a certain skill for most of your damage.
- IAS is factored directly into your damage score. But depending on your class and build, IAS may be more or less useful to you. If you are primarily resource-capped (if combat often consists of dumping a whole energy bar into an expensive spender such a Frozen Orb), IAS actually does very little for you, as it doesn’t change the number of casts you get before you run out. Similarly if you use a lot of cooldown-based skills. Conversely, if you generally spam a resource generator (Monks, often), IAS could be better than it appears. Don’t rely on the Damage score when evaluating IAS; think about whether attacking faster is useful in your build.
- A more subtle version of the IAS issue is weapon speed. A 1.2 speed weapon and a 1.5 speed weapon might do the same DPS, but one hits much harder per swing and the other attacks faster. The same logic from the IAS discussion applies; one or the other may be much better for you even if they have the same Damage score.
- Some stats are not reflected at all in Damage; notably, cooldown reduction and resource cost reduction. Many of the types of builds that don’t like IAS like these stats, because they let you use your attacks more often in practice. Don’t worry about the fact that favoring these stats and disfavoring IAS makes your Damage score look lower.
- The CC/CD engine. While these are reflected correctly in Damage, that can be deceptive at low gear levels. The value of each of these stats depends on the other one, so when both are low (when you’re just starting out), CC and CD affixes might show up as weak in your Damage score. Trust that once you accumulate enough of both of them, the synergy is very strong, and a key part of doing high damage. Even if CC/CD items look weak at first, consider saving them because the effects will snowball as you get more.