At least, not more than once in a row. They've stated that their intention is to force us to avoid spamming a single nuke spell, to make us switch things up. They want pressing the Arcane Blast button once to be a good idea, pressing it twice to be a bad one.
Arcane as a standalone tree:
Currently, Arcane is the red-headed stepchild of the Mage trees. It has a lot of good talents, but they seem to be geared toward augmenting the other trees. Arcane isn't really viable as a standalone tree. Fire is better for PvE, and Frost is better for PvP.Frankly, that's just stupid.
I can understand what they think they're doing here, and I agree that pressing one button over and over again is no fun. The problem is that pressing the button once was never that great, it was ramping up the damage over several casts that was the good part. You ramped up the damage, you took the mana penalty, and you learned to rotate it with other spells so that you could maximize the damage and minimize the mana burn. It was one of the more interesting mechanics we had. It certainly beat spamming Fireball or Frostbolt.
Blizzard even introduced a very fun proc mechanic in this expansion--Missile Barrage--that depends on Arcane Blast spam to function. It provided a built-in break in the rotation, and coupled with Arcane Barrage made for a fantastic, interactive, powerful Arcane spell rotation that just felt right. Now, not only is Arcane Blast too expensive to cast more than once, it's not even really worthwhile to cast the first time. Missile Barrage has been rendered useless, and a spec that was feeling like a very viable standalone spec now has no primary nuke.
We have mass available stock of wow gold on most of the servers, so that we can do a really instant way of wow gold delivery. We know what our buyers need so we offer an instant way of cheap wow gold, buy wow gold fast delivery.
What I hope is happening here, what I pray is happening here, is that they're just over-nerfing a spell for testing purposes, and then gradually reducing the nerf to a more acceptable level. The mana penalty needs to be less than 100%, or the damage increase needs to be increased to match the penalty. Mages will manage the rotation themselves, Blizzard; you don't have to force us to play a specific way by instituting an absurd penalty for casting the same spell more than once in a row. Give your player-base a little credit. If you don't want Arcane Blast to be our primary nuke, what's the spell good for? Also, what spell would you prefer wow gold powerleveling we use? Arcane Missiles is already mana-prohibitive, and Arcane Barrage is an instant-cast spell with a cooldown. That's...well...that's it for single-target Arcane damage spells, really. How would you have us play, Blizzard? If Arcane Blast isn't our nuke, what is?
School-specific Concerns
Arcane Tree
Arcane Blast still sucks:
The 300% I mentioned last week has been reduced to 200%. This means two things: first, the 300% wasn't a typo, and second, Blizzard doesn't want us to use Arcane Blast.
The expansion may just change this. If the resources comparison Arcane Blast issue can be resolved, this tree can absolutely provide a viable PvE or PvP alternative to Fire and Frost. Almost every talent in the tree has been improved, and the news resources comparison talents are almost universally good. The tree has the potential to be very fun to play, and provide viable PvP and PvE damage.
|
