Card potencies (class specific)

[FunkyBunch]

He's blatantly wrong. The bulk of BLM damage in mob pulls is in the Fire 2> Fire 2> Flare portion of the rotation, as should be obvious. Making that bit go faster, means more DPS. As for making Fire 3's cast time under 3 seconds, any competent BLM is going to be putting Leylines on cooldown as often as possible without compromising it for the boss encounter. It's 90s cooldown means it should be up for every other pull or so. With Leylines, they have to hold off on that next Fire 3 for a bit, anyways.

No. No. No. No. No.
Making the fast part of the rotation faster doesn't make overall DPS go up when you still have to wait the same amount for the MP tick.
EG-1000 potency over 15s is 1000 potency. 1000 potency over 14 seconds with a 1 second wait is still 1000 potency per 15 seconds. (please don't worry about the numbers, I know they're not accurate, the principle is the same because math)

You don't ever use Ley Lines in AoE. You still can't get enough SS to knock down the server tick wait. Using LeyLines just makes you look busy.

[FunkyBunch]

While that's true, that's not all there is for BLM AoE. On 3 targets you can safely use a sharp cast thunder and the extra SS would help you weave those TC procs. Not to mention the overall versatility of having faster cast times if you have to move or dodge an AoE. In the end of the day, if you dont like it you can always click it off.

Why would you ever us TC on the AoE rotation?
That costs you TWO F2 times (one for the T1 and one for the T3 proc because GCD is still GCD).
T1+TC proc=980 potency
2xF2=1080 potency on 3 mobs.

PLUS (most importantly) it slows down your Flares. Which is the entire purpose of the AoE rotation.
That is not a net gain on any day of the week. Furthermore, clicking off a buff is a pain in the butt on the PS4.

[Lilyth]

Why would you ever us TC on the AoE rotation?
That costs you TWO F2 times (one for the T1 and one for the T3 proc because GCD is still GCD).
T1+TC proc=980 potency
2xF2=1080 potency on 3 mobs.

PLUS (most importantly) it slows down your Flares. Which is the entire purpose of the AoE rotation.
That is not a net gain on any day of the week. Furthermore, clicking off a buff is a pain in the butt on the PS4.

A GCD is a GCD?
While two fire IIs take 6 seconds to cast (not taking into acount SS), a Thunder plus a TC proc only takes 5. And even then you're ignoring the possibility of another TC proc'ing for another 745.5 potency which is highly likely to happen with 2 mobs having Thunder (this is particularly fun to do when a known tank is still moving forward pulling mobs so you can keep moving with him and casting TC procs instead of scathes). I find 100 potency on an AoE pull is worth sacrificing for a chance of having a higher DPS, but that's just me.

Also you're not really losing any flares. You should always end the AoE pull with a Flare regardless of your MP so you'd only realistically lose a Flare if you delayed the rotation for around 10 or more seconds. And Fire II is only really a filler used until transpose comes off CD. You can easily swap a Fire II for a TC proc and still gain DPS (on 3 targets) while not delaying your rotation.

[StouterTaru]

A GCD is a GCD?
While two fire IIs take 6 seconds to cast (not taking into acount SS), a Thunder plus a TC proc only takes 5.

That's the heart of the issue, a GCD isn't the main factor in BLM Flare AoE. Your 2 GCD casts of 2.2 seconds each doesn't add 4.4 seconds to the rotation, it adds 6.0 seconds. Your rotation doesn't change from 15 seconds to 19.4 seconds, it becomes 21 seconds due to server side 3 second MP ticks.

(this is particularly fun to do when a known tank is still moving forward pulling mobs so you can keep moving with him and casting TC procs instead of scathes)

That is part of the pull, not part of the AoE rotation. Thundercloud works during the pull, at the start of a rotation to weave in RS/QS, and sometimes after that first Flare > Transpose while waiting on the first MP tick. After that first Transpose > Fire 3 it's a dps loss.

[FunkyBunch]

A GCD is a GCD?
While two fire IIs take 6 seconds to cast (not taking into acount SS), a Thunder plus a TC proc only takes 5. And even then you're ignoring the possibility of another TC proc'ing for another 745.5 potency which is highly likely to happen with 2 mobs having Thunder (this is particularly fun to do when a known tank is still moving forward pulling mobs so you can keep moving with him and casting TC procs instead of scathes). I find 100 potency on an AoE pull is worth sacrificing for a chance of having a higher DPS, but that's just me.

Also you're not really losing any flares. You should always end the AoE pull with a Flare regardless of your MP so you'd only realistically lose a Flare if you delayed the rotation for around 10 or more seconds. And Fire II is only really a filler used until transpose comes off CD. You can easily swap a Fire II for a TC proc and still gain DPS (on 3 targets) while not delaying your rotation.

Okay, I have now calculated it out. And there are three caveats to the data:
It assumes the PIE buff, and you get 4 (including sharp cast, which is around one more than statistically likely) TC procs over 63 seconds (without the PIE buff you literally cannot still cast the optimal F2s in the opener as you only have 85 MP left over with it) and it assumes you don't swiftcast->convert->flare.
It gets you 11402 potency over 63 seconds vs 10876 over 63 seconds. (these are some tough bloody mobs! but I needed rotations that balanced out).
These numbers were corrected for server side MP ticks. (EG-all portions where there was zero MP the time was rounded to the NEXT 3 second multiple).

Technically you appear correct, in that it's slightly better (potency wise) to use TC with 3 and only 3 mobs. IF you get 4 TC procs.
With that rotation though, you do lose out on 1 F3, 2 F2s and one Flare. So while strictly a minor potency increase, you lose out on 7 crit chances by having five extra single target spells. So I'm not sure the potency difference will actually make a DPS difference. Further, adding single target spells like TC will only serve to make it more likely one mob dies early even with proper target rotation which would again decrease potency.

To me it seems just like a way to make it seem busier with no real net benefit and rather large potential downside (losing an AoE target early) since there's no real group of 3 mobs that will take 63 seconds to kill.

[Saseal]

.....so, in other words - I'm not going to hit a BLM with arrow, again. o_o
I guess AoE-ing arrows with a BLM in the party would be the only thing >_>

[FunkyBunch]

.....so, in other words - I'm not going to hit a BLM with arrow, again. o_o
I guess AoE-ing arrows with a BLM in the party would be the only thing >_>

Single target rotation (EG- on a boss) give me an arrow as a BLM, otherwise thank you for not ^^

[Saseal]

Single target rotation (EG- on a boss) give me an arrow as a BLM, otherwise thank you for not ^^

Aha, thanks for the clarification!
(I...... got lost in all the math and abbrevs and skills.... and having no experience playing BLM... only Thaum for SC.... x.x;; )

Single target pew-pewing only... got it! +_+

[Aryn_Lastrov]

I ... don't get how arrow on blm's aoe rotation is not a dps increase?...

Your entire damage is sped up except for the umbral ice phase where you are dependent on server ticks. Your whole fire phase is sped up. I do not see how this is not a dps increase. It's not as good as a balance would be, but it's still a blatant dps increase.

I hate to say it, but if your reasoning for it being a dps loss is that it messes with your fire 3 back into astral fire and you only get 1 mp tick, git gud and learn to wait that extra fraction of a second.

[Rongway]

I ... don't get how arrow on blm's aoe rotation is not a dps increase?...

To do Fire III > Fire II > Fire II > Flare, you have to get two MP ticks during the Fire III. Arrow guarantees that you will only get one tick, and therefore not have enough for two Fire IIs. Any haste on the AoE rotation forces Fire III > Fire II > Flare or (wait or waste an action)> Fire III > Fire II > Fire II > Flare.