Firestarter Management

[chidarake]

That's even worse. When you get a proc right before you start bliz 3, save it for when mp's full, transpose, use proc.

Agreed transposing at that point is a good thing and something I forgot to add in, thx for the correction.

That being said sometimes its not available due to aoe rotations and the like and you used it during a double / triple flare.

[Ferth]

The only time I cancel for firestarter is when I have already started casting blizzard 3 to replenish mp but the proc hadn't appeared before hand.

The obvious reason being the fire 3 will be under astral fire and if I waited till after blizzard 3 I may have to wait on mp tick to use it.

However I do also sometimes keep them depending on if its a boss because I will usually reapply lightning after blizzard whilst I wait on the mp tick assuming its not instant.

I can't imagine this hasn't been addressed yet, but rather than interrupting b3, finish casting it, do your umbral phase, and then rather than blowing firestarter from u3 hit transpose. Then you are starting your astral phase with an A1 instant cast fire 3.

[Maero]

Exactly what others have said, do not cancel out a spell cast just because you get firestarter, many of times you can even get a few fire 1's in there.
Too many people freak out about loosing the proc if not used right away, but you do have time

[SeraviEdalborez]

There are 0 situations where canceling cast to use FS is better unless you would have cancelled that cast anyways to dodge or you know you will need that FS for something (burning an add, whatever) within 1 GCD. Canceling for procs during Raging Strikes is even worse.

If you are that concerned about "wasting" a proc, look into fireweaving.

[Cynfael]

There are 0 situations where canceling cast to use FS is better unless you would have cancelled that cast anyways to dodge or you know you will need that FS for something (burning an add, whatever) within 1 GCD. Canceling for procs during Raging Strikes is even worse.

If you are that concerned about "wasting" a proc, look into fireweaving.

Not to start the whole fireweaving debate from scratch, but wouldn't that just increase your time spent effectively not casting, similar to interrupting the next Fire I to use FS? The reasons given for not interrupting casts seem to support not attempting to fireweave since using an OGCD consumes a fraction of a second each time, or am I missing something here as well?

[SeraviEdalborez]

Not to start the whole fireweaving debate from scratch, but wouldn't that just increase your time spent effectively not casting, similar to interrupting the next Fire I to use FS? The reasons given for not interrupting casts seem to support not attempting to fireweave since using an OGCD consumes a fraction of a second each time, or am I missing something here as well?

You're right that the two aren't really related. But "never interrupt for Firestarter procs" is a golden rule regardless. If one is legitimately concerned about consecutive procs, they can fireweave to assuage their conscience. If their reflex is good enough to do so.

[Sessurea]

Got your firestarter proc, but already cast bliz 3? Thunder, transpose--->Fire3 ( proc )

Can't really think of anything else to say regarding this.....Thundercloud>Firestarter, if both were available.

[HaroldSaxon]

Got your firestarter proc, but already cast bliz 3? Thunder, transpose--->Fire3 ( proc )

Can't really think of anything else to say regarding this.....Thundercloud>Firestarter, if both were available.

Generally yes, although always use a proc AFTER a F1 cast

[Kazard]

Nope, i disagree with Thundercloud > Fs if both are up. If you use FS first, you can use you TC proc to weave the next Fire1.

Puro Strider (gratz to him for his work) cames up with some interesting numbers about it:
"Let's look at pros and cons of Weaving with Thundercloud:
Pros
*Eliminates 60% fail rate of Firestarter when Fire Weaving, which would result in loss of 538.6 potency (Converted from Current BiS Fail amount of -0.840 DPS per weave)
*Not losing 1 DOT tick from previous Thunder I/II (35 * 1.3 = 45.5 Potency)
Cons
*Miss 5% Chance to add 396.5 potency [(60 + ((35 * 8 ) * 1.3)) - 45.5 (from clipping 1 DOT from previous thunder)] from 1 tick while casting Firestarter first + Fire I.
So, we would gain 142.1 potency (538.6 - 396.5) by Fire weaving with Thundercloud instead of using it first in a no-man's land with the RNG God bestowing you with 5% proc for that one tick :P
Converting this to damage and DPS using current BiS; we would gain +392 total Damage or +1.63 DPS"

[MetaRed]

I agree with pretty much what most people have been saying here. In general you never want to interrupt a cast to use a firestarter, and you can fire weave if you are really that concerned about missing a proc chance.

That said, as a blm that does 6-9 each week as a blm (without swapping to smn on some turns which is popular) fire weaving isn't always practical in all fights and all situations during combat. Some of the off GCD spells are very useful and should be held back for specific uses ( manaward to mitigate damage from briars or fireballs, manawall to mitigate meteor stream, etc) what I have been doing is using some off GCD spells or actions I won't have any need for in a given fight (lethargy and potent poisoning potions are some I commonly use to weave and will fire weave with them when they are available, if I don't have an off GCD ability or spell that I don't value for it's use somewhere else in the encounter, I still would not interrupt a cast to get out a firestarter.