Ley lines and AoE

Hey guys, I need some advice about ley lines as I'm struggling to use it effectively for AoE.
My rotation for AoE is (Not including any oGDS in the example)
(opener) F3 - F2 spam - Flare - Transpose
(sustained) F3 - F2x2 - Flare - Transpose - repeat until everything is dead.

The problem I have is that during my main sustained rotation I finish too quickly with ley lines active and end up waiting on my transpose timer. This pretty much completely negates any benefit I get from ley lines in the first place. I want to use it more effectively so how do you guys do it?

If your GCD is below around 2.10 before ley lines you won't get any major benefit due to transpose and 3 second mp regen ticks.

I haven't looked how it math's out but with Leylines I will use Enochian.

F3 ->F2 till however many -> Flare -> Transpose -> B4
F3 -> F2, F2 -> Flare -> Transpose B4

Seems to buy enough time for some MP regen.

In aoe/dungeon situations I only use leylines with raging strikes/convert:

Fire 3 -> Quelling Strikes/Enochian/Leylines -> Fire 2 -> Raging Strikes -> Fire 2 (x2) -> Flare -> Convert/Swiftcast -> Flare -> Potion -> Flare -> Transpose

*Sometimes* I'll use leylines when I can see the melee focusing 1 mob in an aoe situation and I plan on using sharpcast/Thunder in umbral ice (ie. one mob of 3 has much lower health and single target rotation is coming up)

I figure waiting an extra half second to start casting fire 3 after transpose. The amount of time saved casting all those aoes more than makes up for it

All right here is an advanced AOE setup and takes planning. Works great with pulls 5+.

Sprint - Get into position and get decently close in case tanks pull out of range. Blizz 3 - thunder 1 target #1
- Leylines ( I don\\\\\\'t throw this down right away and sometimes wait til after my 2nd thunder 1 in case tanks gets ballsy and pull a couple packs. Aetherial manipulation to tanks while he is pulling helps you get into position faster too)
- thunder 1 target #2
- thunder 1 target #3
- fire 3
- raging strikes and Enochian
At this point I almost always have a thunder cloud proc:
Sharp cast then hit my thunder cloud proc on target #4 giving me an immediate thunder cloud proc again.
- Fire 2

Thunder cloud proc from my previous sharp casted thunder cloud proc target number 5. Now you have thunder ticking on five targets. Very good chance of another thundercloud proc so continue on to target 6 or whatever target has most HP and no thunder on it already.
- Fire 2
- Fire 2
- Fire 2
- Flare
Convert
- Fire 1
Swift Cast Flare
Tanspose
Hopefully got time for a blizzard 4 before Enochian falls off but if you don't no biggie everything is almost dead anyway.

Quote:

---

Originally Posted by verandal

snip

---

Fire II in Astral Fire III does 187.5 potency per enemy;
Thunder does 270 potency if all ticks hit the enemy;
Both have a base cast time of 2.5 seconds.

Using thunder right away as you've described is a definite potency loss:
With 5+ enemies you could do Fire III into Fire II doing 937.5 potency per GCD (versus the 270 potency of thunder - even considering Thunderprocs).

In fact, thunder in aoe situations during Astral Fire is a DPS loss compared to Fire II or Fire I even at 2 enemies.

Fire III -> buffs -> Fire 2 (x2) -> Flare. Period

I've ran into this problem often as well when it comes to Leylines & the Arrow card. Frankly, at this point, I think that Leylines and Arrow are best saved for single target situations. I mean, of course I understand the quicker you can throw out your AoE the quicker things will die. However under the mentality that, as a BLM, you should ALWAYS be casting, waiting like 2-3 seconds for a mana tick sucks.

Honestly, popping Enochian for each pull and Raging like every other (or so) pulls is more than enough power boost to not have to worry about a Sp.S. increase.

May I ask the MP of most lvl 60 Blk? I find during AOE Fire II spams(and I use ThunderI to reserve mp) that I'm too low to SC Flare/Convert at 60, had no prob at 50? am I not running enuff mp or am I doing something wrong?