The Ultimate Black Mage Resources with Damage Calculator

[Adamantium]

To round out my previous posts, I went and recorded myself performing this fireweaving business for a minute. Sorry for the crappy sound, but I had been listening to music and it got flagged by Youtube so I had to remove it. https://www.youtube.com/watch?v=zMbG...3QYjZYPiCCz0aQ

Still not fond of it because we use a lot of cooldowns doing this, but hopefully this will clear up some misinformation and theories about how game mechanics work.

[Umero]

You could weave and it could also not proc at the same percentage chance... Your wording is not bad, but your logic is flawed. Please consult this image if you have more questions http://puu.sh/8VIsD.png

I'm sorry but I have no idea how to read that image... or rather, it seems to explain something else that not what I was trying to explain. I think my word indeed was bad and you took it into something else...

[HitoYuudai]

so many cute lalagirls around here!
I wanna /pet you all <3

[YanderePrincess]

<inane failure to prove anything>

I activate abilities quite frequently between casts of Fire simply because that's when they need to be activated. Doing so does not increase the speed at which the firestarter proc registers. That is a simple fact. I have firestarter procs register before my spell hits the target at max range all the time, and they don't register any faster when I'm at melee range such as on Rafflesia.

[YanderePrincess]

How can this be "Proof" when those macro's wont even work the way your intending them.

Then just do /wait 3 and you get the same exact result.

And the math still applies. The gap needed to know if you have a firestarter proc is .5s, regardless of what you've done or how far from target you are or what the spellcasting animation is doing.

[HitoYuudai]

I guess the kitties and hyurs need some /pet aswell!
<3

[YanderePrincess]

And I love how people continue to blatantly ignore the fact that you're losing out on .5s of casting for -no gain- 60% of the time you attempt to fireweave, which is 30 seconds lost out of every 100 attempts to fireweave. And as was said, you have a .16% chance of firestarter procs back to back (and thus losing one of the procs under normal casting methodology), which further reduces the benefit of fireweaving with OGCD abilities. As for doing it on "last Fire cast," then you gotta find out if that 30 seconds of time lost for nothing is made up for by the 40% of the time you get a full AF3 Fire III instead of the AF1 Fire III you get by not fireweaving (I would assume the .5s lost to fireweaving when you have procs is countered by the .5s you would presumably lose by transposing for the current method of doing it).

[Adamantium]

I activate abilities quite frequently between casts of Fire simply because that's when they need to be activated. Doing so does not increase the speed at which the firestarter proc registers. That is a simple fact. I have firestarter procs register before my spell hits the target at max range all the time, and they don't register any faster when I'm at melee range such as on Rafflesia.

Dear lord.

You are the one that claimed that I was wrong for telling you that spells travel at the same speed regardless of your distance to the target...

All spells take the same time to hit no matter what range you're at, and the bolt hitting is what triggers Firestarter.

Edit: This weaving concept is a bit similar to how many other skills will have their effects applied instantly(at least visually) when you use another skill immediately after it. When you use a Firestarter proc immediately after casting Fire 1, your Fire essentially hits immediately along with Firestarter. Weaving just expands this idea and tries to weave in other off-GCDs in an attempt to get Firestarter procs to show up faster, react to those procs, and munch less of them as a result. I, personally, would not go through all that trouble for something that would likely be a minor DPS increase.

Wrong on both accounts. Also wrong on your edit, as firestarter does not appear any faster by activating an OGCD ability.

...and you are the one that implied that they did, stating that Firestarter HAS to be on its own timer (0.5 seconds after the Fire cast) because it doesn't show up instantly if you're in melee range of the target.

Actually, it's not. His has nothing to do with whether or not the bolt has hit (and the bolt hitting is NOT what triggers it showing a firestarter proc, as proven by the fact that we don't get them instantly when we're at point blank range).

Except, you're wrong. The FS proc appears at the end of .5s either way.

Fire 1 registering as having hit, regardless of whether it has visually struck (in the case of normal casting) or not (in the case of weaving), is what triggers Firestarter. Using an OGCD speeds up the registration of the hit and makes Firestarter show up sooner. I gave you straight up video evidence proving that there is a noticeable difference between when a Firestarter proc shows up when casting normally (a good half a second or so) versus when throwing in a skill immediately after (almost instantly), especially in the first two videos, and you're really just going to call it an "inane failure to prove anything" and continue believing that Firestarter always procs at the same interval?

It's become very clear to me that anyone who continues to debate with you is wasting their time. Never have I seen someone stick so adamantly to their stance despite all the evidence against it.

Edit: I will link my recent Fireweaving video again and this will be the last time I bother with this discussion. If you can sit there and tell me that there is a 0.5 second delay on these procs, I don't know what to tell you. https://www.youtube.com/watch?v=zMbG...3QYjZYPiCCz0aQ

[YanderePrincess]

It's become very clear to me that anyone who continues to debate with you is wasting their time.

No, debating with you is wasting time, but I'll continue to correct your misinformation for the benefit of others. The spell registers as hitting before the fireball ever lands, even at melee range, because the spell registers as hitting when the spell finishes casting, as far as the actual game mechanics go. You're mistaking animation fluff for game mechanics. You're also 100% wrong when you claim that fireweaving speeds up the firestarter proc appearing.

Read puro's post -again.- It's .5s regardless. OGCD abilities simply give us something that by default will fill that .5s gap, meaning we don't have to try to guesstimate it's been long enough not to receive a firestarter proc the way we would if we simply waited doing nothing after each spell.

[SeraviEdalborez]

If you want an example of the exact same situation with a much easier-to-understand time reference:

Trial 1) Use Holy. Observe that "+Stun" and the damage pop up almost 2 seconds after cast finishes (when the holy ball "explodes").
Trial 2) Use Holy, and weave anything (lets say Divine Seal). Observe that "+Stun" pops up near instantly (long before the ball "explodes").

The actual timing of when the "+Whatever" and the damage do not change by weaving; in the Holy example the Stun and damage will still occur "later". But by weaving you see the actual proc sooner.

If you still don't understand that concept after the videos provided, I have to believe that you're being intentionally dense and obstructing discussion for no real reason.