BLM macros

[YanderePrincess]

snip.

There's a fairly significant period of time before your notification of a firestarter proc registers, assuming you're talking about getting the Firestarter proc on the very last Fire, not from the second-to-last Fire. If that's a full half second, only 20 of those would add up to 10 seconds, which would be ~4-5 GCDs. If it's a longer delay, then that's even more GCDs that could be fit in there.

[ViviAnimus]

That's why you preemtively press fire III button. You don't wait for the notification

[Urielparadox]

That's why you preemtively press fire III button. You don't wait for the notification

right but what happens when you do this is that you hard cast fire 3 and it just cost no mp, you don't get the instacast effect.

[ViviAnimus]

I don't hard cast Fire III, mate. You can't hard cast a Fire III when you have only 300 MP left. I press the Fire III button after my last Fire I so when a proc hits it's an instant Fire III, not a hardcasted one. I really don't understand what you mean that it costs no MP at the same time.

1000 MP - Fire I - Preemtively press Fire III button (300)MP
This way it's like just casting a normal Fire I + instant Fire III proc. I do this very swiftly. If there is no proc, I just cast blizzard III and continue my rotation.

[ViviAnimus]

https://www.youtube.com/watch?v=tEPJ3rNBkUA

At 2.05 minutes you see an example of this. Every though I had 700MP left, so pay no mind to that. As you can see, what is being done at 1300 MP is Fire I is casted and BEFORE you are going to regen your mana with Blizzard III, you preemtively press the Fire III button in case a proc pops.
Another example at 3.35

[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.

[scarebearz]

https://www.youtube.com/watch?v=tEPJ3rNBkUA

At 2.05 minutes you see an example of this. Every though I had 700MP left, so pay no mind to that. As you can see, what is being done at 1300 MP is Fire I is casted and BEFORE you are going to regen your mana with Blizzard III, you preemtively press the Fire III button in case a proc pops.
Another example at 3.35

Wow, you see/get the proc's pretty much instantly after the cast O.o

Mine take a lot longer to show up.

[YanderePrincess]

That's why you preemtively press fire III button. You don't wait for the notification

You can't queue up a Firestarted Fire III before it shows as available. You may be spamming the button so that it casts as soon the proc does become available, but you're not saving more than a tenth of a second at most, and you're still suffering the half second or more it takes for the proc to become available in the first place.

You quite simply cannot cast Firestarted Fire III as soon after the Fire I that procs it as you can Bliz III after your last Fire I.

[YanderePrincess]

https://www.youtube.com/watch?v=tEPJ3rNBkUA

At 2.05 minutes you see an example of this. Every though I had 700MP left, so pay no mind to that. As you can see, what is being done at 1300 MP is Fire I is casted and BEFORE you are going to regen your mana with Blizzard III, you preemtively press the Fire III button in case a proc pops.
Another example at 3.35

Yeah, you're doing exactly what I thought. You're not "pre-emptively pressing the Fire III button." You're spamming the Fire III button for over half a GCD period (your firestarter procs come up at about the same time mine do) until the Firestarter proc occurs, which is not only a delay between your Fire and Fire III, but also means that since you do this everytime, you're causing yourself to lose at least that much time every rotation because you wait for there not to be a firestarter proc before you switch over to Bliz III.


also, to adjust my earlier assessment with appropriate time lost in the delay, that's about 1.25-1.5 seconds per proc. With the previously mentioned 20 procs over X amount of time, that's 25-30 seconds of time lost, which is around 10-12 GCDs (going on a 2.5 GCD, more GCDs if you have any significant amount of spell speed). 10-12 Fire I's at 600-700 each (low estimate, I think) gives you 6000-8400 damage, compared to the 5000, I think it was, that you were saying you get from your method? If we estimate an average of 30% of those being Firestarted Fire IIIs (estimating below the supposed 40% proc rate because not every GCD gained will be Fire I necessarily), that's 3-4 Fire IIIs at 1k+ damage each, which adds another 900-1600 damage onto that 6000-8400. On some X time periods, it might come out a bit below that damage estimate because of Bliz IIIs being used in some of the "extra GCDs," but then there can also be Thundercloud procs filling in some of those extra GCDs, too, and the occasional Swiftcast>Flare>Convert as well.

[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.