The Black Mage Rotations

[EasymodeX]

Fixing the back-to-back Flares under UI3 has a reasonable chance of resulting in some sort of impact to double-dip mechanics, although any actual impact is still speculation.

[Synovius]

Agreed. Although they've confirmed they are only fixing the back to back Flares, I am a little scared it may "fix" the overall ability to double-dip as you mentioned. If that were to occur then the AoE rotation I've posted would probably need to be scrapped and a Fire II AoE rotation be adopted.

[Synovius]

The Dreadnaughts are more important to kill than the Rooks so convert is reserved for the Dreadnaughts. My team has no issue DPSing the Rooks down and we use Mage Ballad during this so I often swiftly spam multiple Flares without much problem or Convert. There are many different ways to have effective AoE Rotations and often you can work as a team to execute them.

You can kill in any order you want but our FC, in all three groups (soon to be four) kill the Rook first and foremost and then kills off the low Dreadnaught.

[Waliel]

Fixing the back-to-back Flares under UI3 has a reasonable chance of resulting in some sort of impact to double-dip mechanics, although any actual impact is still speculation.

I hope it's only a second or two cooldown added on Flare.

[monochromeMirror]

Not sure if you're attempting to keep the opening post up to date, but you should prioritize Thundercloud procs over Firestarter procs. Either way, you aren't using your next Fire until both are used. Using Thunder III first allows a higher change of procing another Thundercloud. There's no benefit to use Firestarter first under normal circumstances.

[Synovius]

Not sure if you're attempting to keep the opening post up to date, but you should prioritize Thundercloud procs over Firestarter procs. Either way, you aren't using your next Fire until both are used. Using Thunder III first allows a higher change of procing another Thundercloud. There's no benefit to use Firestarter first under normal circumstances.

I am attempting to keep it up to date and may have forgotten this! Thanks for pointing it out. I believe it was discussed several pages back as well. I'll update the OP.

[Allyrion]

Fixing the back-to-back Flares under UI3 has a reasonable chance of resulting in some sort of impact to double-dip mechanics, although any actual impact is still speculation.

But the double dip mechanic is simply based on effects happening 'on impact' rather than right after casting.
The way I see it, it's a small compensation for missing out on all potential Firestarter procs which is caused by the same design.

One will affect the other and I'd certainly give up double dipping to Fire III on every proc. Though I doubt they're going to buff BLMs anymore, especially since they just said that lower dps will be 'brought up to BLM damage' recently.

[Sheapy]

I think this might effect the UI3->F3->(Quick)Fire seeing as how both double Flare and the quick Fire rely on UI staying a bit longer than intended.

[Ferth]

Sorry for jumping in with this thought so far after the fact, but I wanted to pose a question about how people deal with a firestarter proc that happens as you start the umbral phase.

When I get those firestarter procs as I am already casting blizzard 3 I have started using transpose after I cast thunder 2 (and wait for the final mp tick.)

I haven't done any real math with this beyond the straight forward U3+Fire3 damage modifier compared to the A1 Damage modifier, but that in itself feels significant enough to at least make it a viable strategy when the situation occurs.

[Waliel]

That's what I do. If it's better than waiting 0.5 seconds after your last Fire cast to see if Firestarter procs, I have no idea. You might want to consider using Blizzard or Scathe depending on when the last mana tick was, though, rather than just waiting two seconds doing nothing.