I’d like to request that Firestorm be reworked just like the Warlock’s Rain of Fire spell. We should be given the option on the talent tree to select between 2 versions of Firestorm, one where you cast on an area and one where you cast directly on target. I’ve made the same request previously for the Mage’s Flamestrike and the Warlock’s Rain of Fire but, so far, only Rain of Fire has received this much needed modification.
Please consider this request and thank you for your time.
Not going to happen.
Seems like quality of life changes work on a roulette priority system.
See you in 2032.
I would like this as well, if priest can have it for shadow crash, shamans get it for earthquake and locks get it for rain of fire, I can see no reason that this couldn’t have the same type of choice. Let min maxers us the exact targeting reticle, I need to be able to dip dodge duck dive and uh dodge while not putting my firestorm on the ceiling or something
I wouldn’t count on it now that many people are using it in M+ and even in raid to a small extent.
Why not?
It already even happens on the every 9 pyres talent lol
So, you’re saying because a spell is now popular that warrants it not receiving attention? That’s a bit pessimistic. If anything, having a ground-reticle spell become more popular would put it more to the forefront of the developers’ attention for requests such as this.
If Shamans are able to have Earthquake receive this QoL treatment along with Warlock’s Rain of Fire, I firmly believe Evoker’s Firestorm will receive the same options.
The only reason Fire Mage’s Flamestrike has not yet received the same treatment is because the spell is not learned from the talent tree like all the previous examples. Seeing as that is currently their system of offering this choice, they would either need to make a toggle in the options menu to have all ground-reticle operate this way, have a fly-out sub-option for each ground-reticle ability in the spellbook for class abilities only, or slightly reconfigure Fire Mage to have Flamestrike be moved to the spec talent tree in some form or fashion.
I didn’t say it shouldn’t recieve attention, I was saying it is less likely. Appologies for the miscommunication.
Isn’t there some way to make it target a friendly player? Like, /cast [@player] Firestorm ?
Something like that. If so, you could cast in on your tank’s location.
I ended up using the /cast [@cursor] Firestorm command.
I don’t like how AoE centric that build is. I might nuke packs of monsters, but I feel like I’m slapping at the boss.
The difference between Shadow Crash/Rain of Fire and Firestorm is that Firestorm has a cast time unless proc’d. While they COULD make it automatically spawn centered on the target, do you center it at cast start or cast completion? Cast start you’re going to never hit in PvP. People just move too much. Cast completion? Now you’re running in to other issues about balancing.
If proc’d so its an insta-cast, sure. It should automatically center on your current target.
Firestorm should be instant cast. This was always a problem - Snapfire is great, but base Firestorms feels terrible to cast, with the long cast time and lower damage. Leading the target with these casts is more necessary because they can move during the cast.
It should always be instant cast, at least when you are talented into Snapfire. It will always feel wrong that Snapfire procs are so much stronger than base Firestorms. The cast time doesn’t fit with Flameshaper’s highly mobile, instant-heavy aoe rotation. And it makes poor use of Burning Adrenaline procs.
Evoker gameplay mostly allows you to pick a target and stay on them, with Pyre cleaving off them automatically, so we are already dependent on the primary target’s position for our damage to hit. In Dragonflight this made for fun, mobile gameplay in dungeons. Needing to @cursor Firestorm constantly is a jarring break from that. So is needing to hard-cast Firestorm periodically. Both should be addressed, not use one to justify the other.
A pull-out tab in the spellbook for each spell that allows cast-at-target-location is the correct answer. This should be done for all such spells, and the choice talents removed.
Having access to both spells with two different spell ID’s would restore the freedom of choice that players had with @target macros years ago, while limiting it to certain spells. Let players keybind either or both spells, and make macros that switch modes with a modifier key. You shouldn’t have to switch talents to change this behavior, and spells being baseline instead of talents shouldn’t prevent them from having this feature.
I have a feeling we will be getting it back at some point. Testing the 1 button rotation on ptr and its doing it for you with ground spells. Hopefully we can at least macro it like we used to way back or they add an option like you said.