FlashFire BW Tactic

[wonshot]

Hello, after the latest change to Flashfire I came across something that seemed a little strange or at best disappointing.

I understand how the old Flashfire was too strong, and I like the new version and would still run the tactic if it wasnt for this one problem that I find happends too often:

An enemy disrupt and I proc my flashfire, I try to cast a long casttime spell like Fireball on a target, but if I fail to finish the cast the Flashfire proc will be consumed. Even if the target is breaking Line of Sight to me. It happends alittle too often and leaved to me unslot the tactic since I found it required to much micromanagement watching for procs, and trying to actually get them off being afraid they would get consumed without the spell connecting to it's target.

My suggestion, or topic of conversation is:
Should Flashfire procs not be consumed unless the spell consuming the proc hits a targets(can get defended)

Thank you for your time.

[Telen]

Its bugged. Procs arent consumed until casts complete.

[Bozzax]

It is not as good as you bws want it obviously.

The real question is it so good in it is current form that it is mandatory?

[Reesh]

It is not as good as you bws want it obviously.

The real question is it so good in it is current form that it is mandatory?

It never was mandatory and never will.

[Scrilian]

It's a matter of when a newly introduced bug associated with a nerfed tactic would be fixed, sigh.

[Khrum]

Is all about to get use to it.

Proc is consumed as tactic just cut cast time, rest is just skills mechanic

If enemy leave range your spell will fail, LOS and disrupt same, but that all is skills mechanic not tactic

Spells used after old FF also have same conditions

New tactic allow you cast on move so with bit practice you can prevent target getting out of range or use LOS

[Scrilian]

No, that's simply not true.
Old FF allowed you to continue recasting your spell until you are able to actually cast it and only then consuming the proc. Anyway, no proc in the game currently outside of bugged FF is consumed on the cast start - therefore I see no reason for it to behave this way.

[dansari]

No, that's simply not true.
Old FF allowed you to continue recasting your spell until you are able to actually cast it and only then consuming the proc. Anyway, no proc in the game currently outside of bugged FF is consumed on the cast start - therefore I see no reason for it to behave this way.

Precisely this. It doesn't matter if it "is still way too strong lulz why complain sorcs have no mirror order bias" it's still a bug.

[Tesq]

if it's a bug it goes to the bugtracker...

cit unknown