BLM macros

[Urielparadox]

your game runs smoother then mine that is for sure. My game doesn't register a firestart proc that fast, so I tried that but it doesn't register on my end the only way I can get a fs proc off like that is to delay casting blizzard.

are you playing on ps4 or pc? I know my pc needs an upgrade but if that's ps4 I might just get that for now.

[ViviAnimus]

I'll do some more testing and come back at you. At the moment I am still doing less DPS. 325 instead of a good 330 (no buffs or anything, just RS). There is only time lost (1 sec) after Fire I without a Fire Proc. But on the other hand, don't you lose time when having to use Transpose? I still it still boils down to the same thing in the end but that I have more damage. Also, if you lose like a second using transpose, like you would lose a second while casting BIII after no Fire Proc, wouldn't you lose more seconds using the transpose method? After all, you always would use transpose while on the other hand there is a 40% chance of a proc hitting and therefore I don't lose any time at all. You can clearly see in the video that by pressing Fire III while my last Fire I is casting, it's just casting like a normal rotation would. Or am I making a mistake here? I can't seem to find another explanation as to why the tranpose method keeps parsing lower.

[scarebearz]

wouldn't you lose more seconds using the transpose method? After all, you always would use transpose while on the other hand there is a 40% chance of a proc hitting and therefore I don't lose any time at all. You can clearly see in the video that by pressing Fire III while my last Fire I is casting, it's just casting like a normal rotation would. Or am I making a mistake here? I can't seem to find another explanation as to why the tranpose method keeps parsing lower.

Depends on when the mana ticks are coming, but if mana ticks are on the faster side I'll use a scathe after thunder and use transpose during scathe's GCD.

[YanderePrincess]

snip.

You don't lose time going immediately into Blizzard III from Fire I without trying to launch a proc'd Fire III. And the time spent on Transposing is negligible, I would say. It depends on when mana ticks come, but you can essentially lose no time on it if your timing is good. Scarebearz' comment about Scathing after Thunder is a good way to negating time loss, though I've yet to have to do that (and I kinda still tend to forget Scathe exists...).

I'm not sure what you mean by "always would use transpose." In my single target rotation, I only use Transpose for boosting the damage on Firestarted Fire IIIs after a Thunder II in UI3 (excluding occasionally screwing up my mana and having to transpose into UI1 to get mana back, cause that's just me being bad lol), so Transpose is only getting used on the occasions that the Firestarter proc happens.

On the other hand, you are -always- taking that 1.25-1.5 seconds of spamming Fire III after your last Fire I "just in case there's a proc" so you're not only losing time when there is a proc, you're losing time when there isn't a proc. This is where the big damage loss would be coming in, honestly. My previous calculation was based just on the delay coming when there -is- a Firestarter proc, but I left out all the extra time wasted when the proc doesn't happen, because you -have- to wait the same amount of time to know whether a proc happens or not every single time you've cast your last Fire I of a rotation.

We mentioned 20 procs over X amount of time. I forget how much X amount of time was, but considering that Fire III is only going to proc on 40% of those "last Fire I" casts, well, 20 is 40% of 50, so that means 50 "last Fire I" casts in that X amount of time (and this is generous since procs from your second to last Fire I will prevent a "last Fire I" proc because of how we do our rotations, so it would in actuality take more than 50 to get our 20). That means that in X amount of time, you're actually wasting 62.5-75 seconds, which is 25-30 GCD casts lost over X amount of time. If all of those were simply Fire Is lost, that'd be (using my previous values) 15,000-21,000 damage lost over X amount of time. Like before, the exact value/range will fluctuate depending on how many of those GCDs would be filled with Fire IIIs, Blizz IIIs, Flares, Thunderclouds, and Thunder IIs.

[ViviAnimus]

Ah, yes, that's true, it's so stupid of me to think it, I realised it just a couple of minutes ago myself. What you say is absolutely true. But for some weird reason my DPS is always lower when I do that! I'll try it over a longer time span! I used to do it for like 10 minutes. I must say though, I really don't think I lose time when pressing Fire III during my last fire III. My reaction is really fast, but I guess it does accumulate and your theory is correct. I don't wait for the proc icon to appear though, so I don't think I lose time when there is a proc. Basically it will be like a naturally casted fire III proc. Cheers for clarifying, I was silly on my reasoning! I'll test it out tomorrow.

I use Blizzard I when I know my mana will not have fully returned when I'm about to use Fire III (Blizzard III - Thunder II - Blizzard I (in case of not enough mana regen) - Fire III

[YanderePrincess]

snip

Something to remember is the Firestarter'd Fire III can't be cast until the proc registers, which is when the icon gains the dotted outline. That's why we "risk" losing out on occasional Firestarter procs by goign straight into another Fire I and then casting the Firestarter'd Fire III if it happened to proc off the Fire I before that.