3.1

Stocking Up for Ulduar?

by

piggy-bank

Do you find that you have time on your hands lately? Have you been checking on the Ulduar news every hour from work?

If you have extra time in the game, there are things you can do to prepare for the release of 3.1. Stockpiling a few little goodies can distract you from the suspense and even–potentially–improve your raid performance when 3.1 does hit. In addition, I know from experience that prices on many commodities change–in one direction or another–whenever a patch alters their relative value.

As a caveat, though, I’ll tell you that I am directing most of my efforts toward stockpiling just one thing–gold. I’m making as much as I can right now off the sales of flasks, herbs, ore, and bars. Gold is the ultimate stackable quantity, and I don’t have the bank space for some of the other goodies I’ll mention here. As an added plus, gold will let you buy what you need when you need it–quickly. However, there is a potential to make more on some of your auctions if you can wait a bit. I’m no WoW market expert, but based on the information we have about 3.1, here are some of the things whose values stand to change at the release of the patch.

The Winners

The following things, by my best guess, stand to rise in price after the patch. New recipes and profession changes along with an influx of new gear will make some things more coveted than they are now. In addition, everyone’s consumables bill will skyrocket as guilds take on new and challenging encounters.

Titansteel bars
Saronite ore and bars
Blue-quality gems
Arctic furs
Heavy Borean leather
Frostweave cloth
Flasks
Buff food
Potions (Health, Mana, Speed, Indestcructible)
Uncooked meat
Glyphs
Enchanting materials

The Losers

These things will experience some change at the patch. I would expect their price to go down, either a little, in the case of fish (as more people will be driven to fish their own with shorter cast times and the chance at a mount) or a lot, in the case of BoE epics. Many of these items, like Je’Tze’s Bell and the Greatness trinket, will go from being an enormously high-priced item (8,000-12,000g on some servers), to merely outrageously priced (5000 or less). A former best-in-slot will never be as coveted as a true best-in-slot, and I have every expectation that some Ulduar trinket will dethrone these two.

Herbs (nodes will soon yield more flowers per gather)
Raw fish
Nobles cards
Je’Tze’s Bell
BoE Naxx epics
BoE crafted epics–item level 200

So, long story short? Sell your Nobles card now, and buy your Bell later. As for me, the only thing I’m stocking is a few flasks. My guess is that the Flask of Pure Mojo will overtake the Flask of the Frost Wyrm for healers, and I have some that I made for cheap ready for the new market. A further word to those in the Inscription business: I suggest researching commonly-used glyphs now and preparing several stacks for sale at the release of 3.1. Competition will be high among scribes, so prices might not be as astronomical as you think, but the business will dry up quickly as people pick up their second spec. You’ll no longer have repeat business from frequent spec-switchers.

Did anyone see anything I’ve missed? I’d love to see your financial predictions for 3.1.

When a Bonus is More than a Bonus

by

maple-banner

Thanks to MMO Champion and it’s data-ming ways, we now have access to a preliminary version of the Tier 8 set bonuses. It’s anyone’s guess whether these bonuses will actually go live. The bonuses for Resto druid appear to be excellent, though there’s one catch: the 4-piece bonus for Tier 8 is much too good.
t8-prospective-bonuses

Here we have a classic example of a good set bonus and a “bad” set bonus. Lest you grow angry at me for complaining about buffs as well as nerfs, I’ll explain what I mean.

What makes a set bonus good?

The two-piece Tier 8 bonus, which gives a 10% boost to the throughput of Swiftmend, will be nice to have. Swiftmend is a spell almost every healing druid talents for, and it can be used by both raid healers and tank healers alike. The bonus doesn’t conflict with or double the Glyph of Swiftmend, which is a different and even stronger throughput increase which allows Swiftmend to be applied without consuming one of the druid’s HoTs (either Rejuvenation or Regrowth). Moreover, if I had one piece of advice for most Resto druids, it would be to use Swiftmend more. Many forget all about it because it’s a two-step spell–HoT setup plus instant top-off. I find that I perform much better if I use it whenever it’s up. Still, this bonus will never be overpowered, even in combination with the glyph, because Swiftmend continues to be on a cooldown. Druids will get this bonus and enjoy it, perhaps giggling to themselves over their WWS reports. However, it will be a set bonus that the druid can bear to leave behind for whatever Tier 9 gear has in store.

What makes a set bonus bad?

We’ve all seen set bonuses that are lackluster or unusable. The Tier 6 4-pc Resto druid bonus to Healing Touch comes to mind as a particularly useless one. I passed on Tier 6 pants in favor of badge pants because this bonus simply wasn’t one. However, a bonus that goes in the other direction, becoming so good that it overshadows all other gear upgrades, is actually more harmful to the class and the game. Take, for example, the much-lamented 4pc Tier 5 mage bonus, which entirely changed the functioning of Arcane Blast, greatly upping its damage output at an increasing mana cost. I still /spit on this bonus. It caused the four raiding mages in my former guild to hold onto 4-pc Tier 5 until they were able to equip 4 pieces of Tier 6 at once. The consternation this caused them probably cost my guild several extra hours of loot debate. The mages also faced accusations of DKP hoarding as they waited to buy the early Tier 6 pieces. They had much more DKP than they could spend because of their need to hang onto T5. Moreover, the mages themselves didn’t always pay the increased mana cost. Instead, the druid healers Innervated them. We didn’t mind, exactly, because mana was plentiful for healers at that point, but I couldn’t Innervate all four of them, and I always felt bad when I didn’t have any juice left for a player who asked. However, the most pernicious aspect of the bonus had to do with play style. It pigeon-holed mages into an arcane spec and a set rotation, turning three trees into one for a tier and a half of content. I know one determined fire mage who switched to her warlock in Tier 5 because she didn’t like the arcane playstyle. In the end, the T5 bonus was judged to be too strong, nerfed, and finally taken away.

Ghostcrawler has actually said in the past that a tier bonus should be just that–a bonus. I wholeheartedly agree. However, the 4 pc T8 bonus isn’t going to just be a bonus–it’s going to radically change most druids’ rotations.

Rejuvenation has always been a good spell, but its limiting factor is that it doesn’t tick for 3 seconds after it is applied. In essence, that turns it into a HoT with a long cast. Rejuvenation is probably the druid’s most over-written spell. Thankfully it’s also our most efficient. With the bonus, I would get a tiny burst of healing–1997 in Syd’s current gear–when I cast the spell. That’s less than a Holy Shock, but it has a huge impact. With even a small initial heal, Rejuvenation would be “fixed.” It would go from being something that some druids don’t cast, preferring the faster-ticking Lifebloom and Wild Growth, into the raid healing spell. I think this is a very innovative and necessary addition to the spell; however, it doesn’t belong in a set bonus. This “fix” would get druids away from using Lifebloom for every situation, and that’s great. However, if this change is truly imagined as a “fix” to the spell, it needs to be made permanent through talents. Hell, I think it’s worth 5 of my talent points–or even the entire space in the tree occupied by Revitalize and Living Seed. This one little set bonus would give druids what they’ve always wanted–a tool to keep others from sniping their heals.

“Sniping,” for the uninitiated, is the practice of going outside one’s own healing assignment to heal someone else’s target, particularly a target that already has a ticking hot or a slower-casting incoming heal. Typically, players snipe with quick heals–Flash Heal, Flash of Light, Chain Heal, even Nourish or glyphed Healing Touch. As I’ve explained before, healers will never stop sniping–in any case, not until the default UI shows incoming heals and HoTs, mana is as scarce as roses in the Alaskan winter, and healing meters go extinct. Druids are incredibly vulnerable to heal-snipers as most of our healing takes a bit of setup before it starts to work. Ghostcrawler has said in the past that heal-sniping is a valid concern, but it’s not going to be fixed through nerfing mana. Other tools have to be used against it, and the new Rejuvenation is a perfect fit. Healers who play without any incoming heal data will be able to see that the target is covered and consequently will turn elsewhere, even (gasp!) back to their own assigned target.

The change to Rejuvenation needs to be either a talent or a glyph–and I would prefer talent, because then it would correspond to priests’ new talented Renew, which just got a similar front-ended burst. Renew has never been as good as Rejuvenation in the past, but with a small initial burst, it might just be better than Rejuv post-3.1.

In any case, if this tier bonus remains unaltered, druids will wear their Tier 8 until they have 4 pc of Tier 9–and maybe even beyond. This set bonus is more powerful than any one gear upgrade–and I would say, probably more powerful than four. It steps beyond what a bonus is supposed to do. At maximum, I’d say the set bonus for a previous tier should maybe give a player pause about equipping just two pieces of the new tier or item level, as it may be. Not all the best pieces are part of a set. However, when it gets to three upgrades over the stats on the old tier, players should be happy about making a change.

I’m concerned, Blizzard–very concerned. Thinking as both a raiding druids and a guild officer, I’d rather not wrestle with this particular angel, as good as that set bonus may seem when we’re sitting at the beginning, not the end, of Tier 8.

More Shaman 3.1 Changes (With Edit!!!)

by

800px-ketchican_totem_pole_2_phixr

Lodur back again with more Shaman changes on the PTR. There was a recent patch and it looks like this is what we got changed

Restoration

  • Healing Stream Totem range increased from 20 to 30 yards.
  • Mana Spring Totem now restores 91 mana every 5 seconds at max rank. (Old – 34 mana every 2 seconds)
  • Nature’s Swiftness changed to – When activated, your next Nature spell with a base casting time less than 10 sec. becomes an instant cast spell. Nature’s Swiftness shares a cooldown with Elemental Mastery.
  • Restorative Totems now Increases the effect of your Mana Spring and Healing Stream Totems by 4/8/12/16/20%. (Down from 5/10/15/20/25%)
  • Healing Grace has been moved from Tier 3 to Tier 2.
  • Ancestral Healing has been moved from Tier 2 to Tier 3.

Totems

Nature Resistance Totem, Stoneskin Totem, Fire Resistance Totem, Frost Resistance Totem, Strength of Earth Totem, Flametongue Totem, Wrath of Air Totem, Windfury Totem descriptions have been changed to reflect the latest changes, they now affects all raid members. ( But will not Stack with some class buffs)

Healing Stream and Mana Spring totems will not be combined at this time.

So, what do we think about all this?

The Healing Stream Totem range increase is nice, I’ll give them that. Not going to really elaborate on that one.

Mana Spring Totem change brings it to 109 MP5 with talents, making it the exact same mana regeneration as Blessing of Wisdom. To be honest, we knew this was coming since BoW and MS no longer stack. This goes hand in hand with the Restorative Totems Talent

The Natures Swiftness change is more PvP centric. It seems to take down the Hybrid spec people were running around with letting them get Elemental Mastery and Natures Swiftness and then have an “I kill you now!” button.

Healing grace and Ancestral Healing Swapping places does not really affect us, that’s more just housekeeping. You still spend the same amount of points in the tree to get what you want without having to take anything you really don’t.

Totems tooltips were updated, that’s about it for the top part there. The big news here is the decision to not combine Mana Spring and Healing Stream totems. With them tweaking MS, I’m not surprised. As much as I would love to see that combination, I personally think it wont happen, at least not till they figure out how to handle mana regeneration for everyone.

Playing around on the PTR (when the world server is active) Nothing really feels different in the play style. I’m hoping to get into an ulduar group (hopefully the raid invite goes through this time =P ) so I can test it out on some heavier content.

What do you guys think ?

*EDIT*

Restoration

  • Mana Tide Totem: This spell no longer costs mana.
  • Restorative Totems: Reduced to 3 points, down from 5. Increases the effect of your Mana Spring Totem by 7/12/20%, and increases the amount healed by your Healing Stream Totem by 15/30/45%.

There it is. Was waiting for the shift in restorative totems. Could be quite nice.

Image from wikimedia

Further Thoughts on Lifebloom Changes

by

syd-drowns-her-sorrows

Here I am, drowning my sorrows in a glass of Miracle-Gro at my favorite Dalaran tavern. Why all the tragic tree tears?

For those of you who have been under a rock for the last week, the news from the developers is that Lifebloom is about to get a heavy nerf to its healing per mana (HPM). In 3.1, Lifebloom will cost twice what it does at current and return 50% of its cost when it blooms, adjusted for the number of stacks on the target.

What does this mean, you might ask?

Ghostcrawler tells us that the intent is to end the practice of rolling Lifebloom–efficiently–on two or more tanks. Unfortunately, the nerf hits a “good” practice just as hard–rolling Lifebloom on just one tank.

I’ve been following Elitist Jerks and the official Healing Class Role forums, and amid the insane drivel and endless whining, I’ve been able to discern a few things.

What Druids Want

#1: Overwhelmingly, druids want a Lifebloom we can use.

Lifebloom has come to be a spec-defining ability, and its rolling mechanism makes it unique. My own worry, and that of many raiding druids, is that the practice of using Lifebloom as a rolling buffer on one tank will be over. We want reassurance from the developers that Lifebloom will continue to work for us.

#2: Druids want consistency in the way we time the spell.

Most druids agree on one thing: the new bloom mechanism is awkward. A reward for blooming and a punishment for refreshing contradict the mechanics we’ve grown up with. In this topsy-turvy Lifebloom world, what’s good now will soon be bad–you’ll want your Lifebloom to fall off whenever you can afford it.

#3: Druids want a raid role, and we want it to be consistent with what it has been in the past.

Every player, of course, wants to be useful. After all, we want to play the game, and rerolling isn’t a realistic option for most of us. I’ve seen priest and shaman and paladin threads about their raid role as well, and now druids are feeling that anxiety. I’ve also seen the devs reply to these anxieties in dismissive and condescending ways. They always say that they conceive of raid roles differently than the community does. To that, I’ll reply that perceptions matter. Raid invites are based on them, after all.

Druids overwhelmingly believe that their raid role is to add a buffer, a bit of insurance against disaster. Our HoTs are like the priest’s Power Word Shield or the Shaman’s Earth Shield: useless when the content is easy, but essential when the content is hard. If cushioning the MT goes the way of the dodo, many druids may start to feel like the poor man’s paladin. I think Blizzard needs to pay attention to the druid’s historical raid role and make sure it remains intact. In order for a buffer to work, it needs to stay up. Rolling LB will always be the best thing–for the tank. And that’s what we want to think about, right?

#4: Druids want to be less dependent on timers

Druid healing is already very rigid. Unlike other healers, we have a true rotation, and it’s every bit as ugly as an Affliction warlock’s. We have four different HoTs, each of which has a different duration, and one of which stacks. We’re already tied to 3rd-party mods to manage these spells, particularly Lifebloom. Right now, though, all we have to do is roll, and the penalty for refreshing early is slight. However, in a mana-constrained environment, with Lifebloom being our most expensive HoT, we absolutely will not be able to refresh early. The penalty will be huge. In addition, we’ll be having to make a decision about whether to let Lifebloom bloom every 9 seconds or so. That’s a lot of mental bandwidth dedicated to timing one spell. Many druids would rather drop Lifebloom altogether than micromanage the bloom. As it stands now, it looks like we will be more dependent on timers post 3.1 than we are now, and that’s a scary thought.

Alternate Solutions

Everyone has their pet fix for the Lifebloom problem or their favorite way to mitigate the impact of the nerf. I’m going to repeat here a couple of my favorites. I’ve seen each of these ideas posted several times by different posters in slightly different iterations, but here’s my take.

#1. Buff Lifebloom’s HoT slightly and reduce the bloom. A gain in HPS on the part of the spell that’s most useful in PvE would cushion the impact of the nerf somewhat.

#2. Limit the number of active Lifeblooms to 6 per druid. I personally love this solution, and I’d even like it if the limit were three. This would keep multiple stacks of Lifebloom from dominating the healing meters, and even though a raid could ostensibly stack druids, most probably wouldn’t. After all, Lifebloom works best as a sort of damage cushion on the main tank. This is the use of rolling Lifebloom that I’d like to protect.

#3. Remove the stacking mechanism. I’m also in favor of this solution for simplicity’s sake. Lifebloom causes a ton of problems because of its stacks. Why not buff the value for a single Lifebloom and remove the stacking capability? It’s the stacking that causes such rigidity in a druid’s rotation. I doubt many druids will be brave enough to single stack it in 3.1, but that’s looking like a mana efficient way to go. Why not make the decision for us?

I’m interested in knowing what readers think about this problem. As for me, I think I understand why Lifebloom is a target right now, and it’s not a pretty thought. I think that–correctly or no–the developers believe that the 40% nerf to OOFSR regen won’t hurt the druid enough. Right or wrong, it’s seen as a nerf that will hurt the priest more. As such, they’ve changed both the cost and the mechanics of druids’ signature spell in order to force us to run empty. My feeling from reading the comments of PTR testers is that the change is too dramatic. Combined with the new, underwhelming Innervate, the expensive rolled Lifebloom may just not be sustainable even on one target. I’m not looking forward to standing idly by mid-fight with an empty mana bar. Far better than that would be to do without Lifebloom, but I sure would miss it.

Flame Leviathan Thoughts

by

flame-leviathan

Yeah there’s going to be a buttload of spoilers here. You probably don’t want to read any further than this.

Tuesday afternoon, Blizzard announced the new PTR boss testing schedules for the week. Flame Leviathan (Normal) would be open from 4 PM onwards. But it looks like someone was trigger happy and they decided to pop it open an hour earlier. I happened to be on right as it opened up and sounded the alarm on Twitter, my guild, and in the WoW Insider war room. Alex Ziebert, shadow Priest extraordinaire, was able to join me. Once we filled up, we got the ball rolling.

So what kind of vehicle does a big, badass Dwarf drive around when he’s feeling bloodthirsty?

siege

That’s right. It’s the only vehicle fit for a dwarf. It’s big. It’s got rams. And it’s got guns. I let someone else drive while I manned the guns on top. After talking to Bronzebeard, we started the event and the Alliance 1st Armored division rolled out of the garage. The division consisted of two tanks, two demolishers and two choppers (bikes). The two siege engines lead the way absorbing the brunt of the Iron army. Demo’s formed up on the rear and attacked at range while choppers were cleaning up anything else that got behind the siege engines.

1st Armored decided to start off with gunnery training. Most of us had no idea what to do so it made sense to start firing on anything that moved and any structures that were destructible. We literally rolled over the opposition with little difficulty.

WoWScrnShot_030309_152037
WoWScrnShot_030309_152240

Click on pictures to enlarge

I found the gun controls were quite stiff to move. It’s like the engineers forgot to add WD-40 to the damn turrets or something. If you’ve ever done Wintergrasp, the controls for aiming are quite easy. You hold down your right mouse button to aim the direction of the camera and the targeting reticle changes direction accordingly. But it’s different in Ulduar. I found that it wasn’t as fluid nor as smooth.

After clearing out the towers, one of the recon choppers noted what looked like a repair pad on the side. We gathered up and repaired our vehicles to full health. Up ahead there was a gate flanked by two Ulduar Colossi.

WoWScrnShot_030309_152927 
WoWScrnShot_030309_152001

Up: Repair pad
Down: Ulduar Colossus

The Colossus is pretty damn large. But the larger they are, the harder they fall. They more really slow, too. I told my driver to switch with me because I had a hunch the vehicle would have a larger vehicle pool. Blizzard did say vehicles would scale with gear. Sure enough, my tank jumped from ~750k health to ~810k.

Matticus was in the hot seat now.

WoWScrnShot_030309_153816
WoWScrnShot_030309_161105

Left: Matt tries to take on the Flame Leviathan to no avail
Right: Matt flooring it after realizing the above the strategy is not working

“Matt! Run! Hit the gas!”
”WTF do you think I’m doing?! Twiddling my thumbs?!”

We didn’t last much longer after that. But I found it a lot of fun. And it is absolutely nothing like Malygos phase 3. Players who have an aversion to vehicle encounters should definitely give this a try at least. And if they hate it, they’ll hate it. But at least try it with a clean slate. Worse comes to worse, if you don’t like driving or shooting, you can be one of the brave souls willing to be thrown on to the top of the Flame Leviathan.

WoWScrnShot_030309_164623

Pretty neat bug where a demo has grappled another demo. There’s still some quirks to be resolved. Towards the end, Alex grappled me onto his demo. I was unfortunately stuck and had no idea how to eject myself. I don’t think I was loaded into the launching arm.

Our best attempt was around 35% before our live raids forced us to cancel out.

Ignis is going to be available for testing today. Try to be on about an hour earlier to avoid the queues that is going to be prevalent. I’ll be in there at around 3 to see if I can scramble some players.

For Flame Leviathan strategy, try checking out Stratfu.