Why didn’t they make Flameshaper around Firestorm instead of adding Engulf? It’s such a cool and good looking ability, it has a whole talent side for it but it’s weak? Wasn’t it the perfect opportunity to make it good?
4 Likes
Because Flameshaper is also for Preservation, they can’t build it around an ability Pres doesn’t have.
Also abilities that require you to keep mobs/bosses in one small area for their duration kind of suck.
1 Like
I’ve seen this suggestion elsewhere, so not taking credit for it, but why not make firestorm attach to a target and then jump to the next target if the first one dies and so on for the duration of the spell?
1 Like
Some hero talents are built around different abilities for each spec (e.g. Voidweaver), so they definitely could have done that for Flameshaper. It’s more that Preservation only has the fire abilities shared by all specs. If they wanted to build Flameshaper around a spell, Breath probably would have been the best option. It would be cool if one of the Flameshaper talents affected Firestorm though.
firestorm is an ability that needs to go. its baaaaad
1 Like
This! They could’ve made it about Temporal Anomaly while Devastation would be Firestorm, since both are “throwable” abilities and have talent nodes just for it. Creating a new ability that, in all honestly, only works for the healer spec (the amount of hots are insane) it’s weird to me. I never saw devastation Evoker a “dot” spec to be completely honest.
Firestorm is a underrated ability that looks cool, cool idea but severely bad cause numbers and mchanics. Seems like Blizzard didn’t learn anything, Consacration and Quaking used to be “bad” too before they made QoL changes for them.
Flameshaper is already clunky enough, the whole play style is like playing the old aff warlock…
1 Like
It does feel a bit like BfA Deathbolt Aff but (somehow) worse. They did rework Hunter and Pally’s hero talent so maybe they do the same with Flameshaper? Ideally they just make Engulf a Preservation talent and then rework the tree to work for Devastation too.
1 Like
Firestorm cannot work as a talent.
It needs to be baseline and have a few offshoot/choice nodes that buff it.
The opportunity cost for taking it will either never be worth it or they will have to make it so strong that it’s beyond busted.
1 Like
not another button!
Honestly I’d rather firestorm become an optional upgrade to firebreath or eternity surge as an empower than a seperate button entirely, part of the beauty of evoker imo is just how few buttons you have
1 Like
What they should do for firestorm is this:
1: Essence burst on a higher chance than flame or azure strike, guaranteed during dragonrage
2: Proc only ability like missiles for arcane mage, or always insta also with a proc, in other words, no cast time
3: The proc condition is disintegrate and pyre, not pyre and living flame, 15% for pyre is mostly fine, but for disintegrate it would obviously need to go up a bit, burnout at 50% chance is also a good alternative, but i would prefer to keep it disintegrate and pyre.
4: It’s a reticle but follows the target like ravager, or it’s straight up cast on target and it rains fire on the target, and everything in a circle around it and follows it wherever it goes.
And now you have an amazing ability, you’re welcome blizzard.
This can’t happen because something giving guaranteed EB that can be providing it while all your gcds go to disintegrate would be FAR too strong, and would also require it in single target.
If it were only the cast that have EB that would be fine, but it absolutely can’t happen every time the damage ticks lol.
Firesstorm should just be a passive proc out of something. Like every firebreath or every pyre you have a chance to have a firestorm popping.
We dont need more abilities to press
1 Like
I mean we don’t have a lot of abilities to press, lol.
Like far less than most dps specs.
That said, I wouldn’t hate this idea.
No it wouldn’t.
You’re not getting more, you’re just replacing a few casts of azure strike or living flame with firestorm.
And outside of dragonrage you would get a few more. Due to the higher proc chance, but what i was thinking was not like 70% proc chance, more like 30 to 40%. Which is reasonable considering the proc rate.
Ofc, the essence burst wouldn’t proc on every tick, that would be far too strong, i don’t know why you assumed that, it’s almost like you’re trying to make the argument as ridiculous as possible. In the same line of logic why doesn’t disintegrate proc the refund every tick? It doesn’t make any sense, obviously the essence burst instance would only be when you cast it and nothing else.
I assumed it because you gave zero explanation whatsoever.
Well i mean, it’s a bit of an absurd assumption, like why would you jump to that conclusion?
Obviously if it can proc on every single tick it would be broken op, that’s probably not what i meant, get what i mean?
Any conclusion I had would have been one that I jumped to as you gave no context,lol.
It’s amusing that you didn’t explain your idea at all and then got pressed about someone having to guess at what you meant just because said guess wasn’t accurate.
I trust people to use a little logic and not come to absurd conclusions, ill just leave it at that.