BLM DPS!!!

[Tanthalus]

Just curious if you've considered the cast time of Thunder III. After Blizzard III, by the time you get Thunder III off your MP is full and there's usually a good second or two there before you can cast Fire III. Thunder II avoids that lull. Also, Thunder II falls off right when your rotation is ready to cast another Thunder II. Thunder III will show an additional few seconds which aren't needed as you'll be casting another Thunder. This is what I've noticed. I do use Thunder III to start a fight/phase though and I'm PC with a Naga mouse so that is a bit of a difference as well.

Yep and I've actually tried to implement Thunder II into my rote but the difference was almost non existent so I went back with what I like.
That and I always get my first Thunder off with a quickcast and hope to ride the procs.

[Kael_Raiju]

There are no "lull times" in using a proc. The recast time is the exact same as Fire I.

When you hit your proc your character literally pauses and stands there. Maybe this is the game's way of ensuring you only get a damage increase on a proc but to me it should be insta cast and the ability to start casting your next Fire I without any pause. I can't be the only one who notices this. Either way... I typically save my procs for the sole purpose of movement. I'm not saying I never cast them in the middle of my rotation but my rotation is heavily reliant on the boss we're fighting. Every cast is based on the current situation. I never stick STRICTLY to any rotation. I.E. Boss is about to jump, there will be an AOE I'm at 1800MP, time to cast a Flare and hope for a great crit. This would be a good example.

[YoloSwaggins]

snip...

The reason you just stand there is because it's cast instantly, but it is still on the GCD. A regular fire I spends that GCD casting, whereas a Fire III proc goes off instantly and then gives you the cooldown after, like DoW skills. There are times where it might be better to hold on to it, but otherwise you should cast it as soon as possible.

[AniCelestine]

I saw people saying "if you have thundercloud proc + first starter proc -> Fire III - > Fire I -> Thunder III "

Please explain that please.

Because from my reasoning, since thunder cloud proc could happen every 3 sedond you have thunder applied on a target(s) so if you don't use it as soon as possible (assuming no movement required anytime soon, so no need to save it) you could potentionally loose a proc because you waited longer than 3 sec and got 2 thunder procs in row.

So, why would "Fire III -> (potentially losing a thunder proc) Fire I -> (potentionally losing a thunder proc, but could get a new fire proc) [Fire proc came so Fire III(based on the earlier Fire III procs > Fire I > Thunder III we're going to use fire I again](potentionally losing a thunder proc) -> Thunder III" be better than "Thunder III ->(potentionally a thunder proc) Fire III -> (potentionally a thunder proc) Fire I" if you are in a situation where you have both procs up.

Note: if you'd got the thunder proc right after you used thunder III proc, you'll already be casting your Fire III/Fire I(assuming you're following the "always be casting" guideline) before it registers to you, so you're mostlikely not going to be doing Thunder III -> Thunder III -> Thunder III and then losing your AF III stack and thus fucling up your rotation.

[Maero]

Really thundercloud proc should take priority over firestarter. Also i really am not certain of those of you starting off with T3, just curious and has Puro crunched numbers with it?
I rather only use T3 when i get thundercloud in those situations. Or at times were i get some lag and such and mana does not fill up after Ice 3, then the cast time of T3 allows mana to be refilled by then

[Synestr]

To get great and sustainable DPS, >>> ABC <<<

Always
Be
Casting

Firestarter and thundercloud procs are nice and definitely help, but you generate NO DPS if you aren't casting anything. Thundercloud procs come from a 5% chance on a DoT, not much we can do to control that one, RNGeesus owns it.

Firestarter is a 40% chance to activate on a successful hit. There are times in my astral rotation where I have gotten 4/5 firestarter procs, and others where i have gotten nothing or just 1. Accuracy might help here, due to the wording of successful hit. Crit is nice as if and when it does pop you have a good chance of getting the big numbaz on it. I usually don't Raging Strikes until after the first fire is cast when in astral, cos I want that proc, if it does happen right away to be juicy.

[Garotte14]

Really thundercloud proc should take priority over firestarter. Also i really am not certain of those of you starting off with T3, just curious and has Puro crunched numbers with it?
I rather only use T3 when i get thundercloud in those situations. Or at times were i get some lag and such and mana does not fill up after Ice 3, then the cast time of T3 allows mana to be refilled by then

The reason most ppl start off with T3 for their opener is because of the extended DoT time. This allows you to get off your Swiftcast/Flare/Convert/Fire1 while the Dot is still ticking. For example if you were to use T1 or T2, it will fall off before the end of your opener giving you a few seconds where thunder is not ticking. At least thats what I think. I personally do not start off with thunder at all. I just start with Fire3>Raging Strikes>Fire1, etc. With not casting a Thunder spell, it allows me to get an extra fire spell off with the Raging Strikes buff. This is just my preferred method.

[Synestr]

Really thundercloud proc should take priority over firestarter. Also i really am not certain of those of you starting off with T3, just curious and has Puro crunched numbers with it?
I rather only use T3 when i get thundercloud in those situations. Or at times were i get some lag and such and mana does not fill up after Ice 3, then the cast time of T3 allows mana to be refilled by then

I disagree slightly, but only with thundercloud procs taking priority. You have 12 secs to use it. When it pops I toss out a fire, most time it procs(or has procced same time or shortly close to thundercloud). SO usually I go, Firestarter > Fire (if procs use again) > Thundercloud.

I only go this way due to Fire having a larger proc rate.

I agree with not starting with T3. Should be using T2 most of the time to start if you start with it. The difference is only 3 secs on duration and the initial difference of 10 potency. Waste of MP for little gain, and longer cast time keeping you from entering AF.

But again just my opinion.

[scarebearz]

Really thundercloud proc should take priority over firestarter. Also i really am not certain of those of you starting off with T3, just curious and has Puro crunched numbers with it?
I rather only use T3 when i get thundercloud in those situations. Or at times were i get some lag and such and mana does not fill up after Ice 3, then the cast time of T3 allows mana to be refilled by then

The DPS difference between using thundercloud proc right away and weaving it, is minimal, as is the difference between starting rotation.

The real difference between BLM's is how people handle their movement, while dealing with boss mechanics.

[AniCelestine]

Really thundercloud proc should take priority over firestarter. Also i really am not certain of those of you starting off with T3, just curious and has Puro crunched numbers with it?
I rather only use T3 when i get thundercloud in those situations. Or at times were i get some lag and such and mana does not fill up after Ice 3, then the cast time of T3 allows mana to be refilled by then

If you start with T3 you might not have the mp to F1x5 so you'd dps on your starting Rotation before next AF 3 (especially if you are using RS+ pot)