The Black Mage Rotations

[Xisin]

I've seen mention of these changed mana ticks ever since 2.1 dropped, but I've never noticed them myself. Can you elaborate on what's changed with the mana ticks specifically since 2.1? The only difference I saw was mana ticks being missed because of the delay in the application of Umbral Ice, and not so much a change to mana ticks themselves.

In 2.0 the ice to fire phase was fairly seamless with perks, you never really had to wait out an interval of time or use filler... it just transitioned cleanly into Af everytime w/o fail. A better perk to th 2.0 ice phase was that the first fire (if buffered after fire 3) got the benefit of umbral ice 3 casting speed (like 1.6ish seconds on a fire) with all the potency of an AF3 cast. in 2.1 they changed how ice/fire phases worked via when the buff was applied, the last tick of ice was essentially removed if you just didn't stop casting during the ice phase, this is when the filler spell practice started.

[Adamantium]

In 2.0 the ice to fire phase was fairly seamless with perks, you never really had to wait out an interval of time or use filler... it just transitioned cleanly into Af everytime w/o fail. A better perk to th 2.0 ice phase was that the first fire (if buffered after fire 3) got the benefit of umbral ice 3 casting speed (like 1.6ish seconds on a fire) with all the potency of an AF3 cast. n 2.1 they changed how ice/fire phases worked via when the buff was applied on cast, thus ending this and resulting in a dps loss for blm.

Right. I remember this, and I do miss it from time to time, but I've grown accustomed to it despite it feeling less fluid than before.

It's just that ever since 2.1 dropped, I would read posts from other people stating that mana ticks had been altered in some way, but to me it wasn't a direct change to the mana ticks themselves, but the altering of how AF3/UI3 were removed (switched to on-cast from on-hit like you stated) that resulted in the potential to miss mana ticks you would have previously received. Like Bloodline said, it felt more like a myth than anything.

I guess I was just being nit-picky and specific.

Edit: Clarification cause I'm silly.

[LetBloodline]

You are missing the big point.
B3 cast is halfed. So it's not even a GCD. There is no way that a bulb your party could kill in that spam time 10% of time with 0 dps from you NEED your b3 damage to die. We are not talking about 20% hp here. You didn't see that bulb's hp where much lower and that you where not needed. You took wrong target. And if your party have trouble with bulbs use a well timed SC + flare since a) it hitting 2 targets will make up for not having convert b) make bulb die faster

[YanderePrincess]

You are missing the big point.
B3 cast is halfed. So it's not even a GCD. There is no way that a bulb your party could kill in that spam time 10% of time with 0 dps from you NEED your b3 damage to die. We are not talking about 20% hp here. You didn't see that bulb's hp where much lower and that you where not needed. You took wrong target. And if your party have trouble with bulbs use a well timed SC + flare since a) it hitting 2 targets will make up for not having convert b) make bulb die faster

You really are illiterate, aren't you? I said very clearly that the mob is over 50% hp when I start my cast. Normally, it takes at least a full Fire I cast to finish the bulb, with the damage from my spell figured in. But on rare occasions, my party gets their damage spikes through crits/bloodletter procs/etc and gets killed significantly faster. It's a very rare occurance, but it does lead to the bug happening when it happens. Eventually, as my static's gear improves, this'll be less likely to occur, but it's still a bug that can on occasion cause problems and people should be aware of.

Now, get over yourself and stop accusing me of doing things wrong when I know for an absolute fact that I'm doing what needs to be done for the situation, and accept the warning about the bug for what it is.

[LetBloodline]

You really are illiterate, aren't you? I said very clearly that the mob is over 50% hp when I start my cast. Normally, it takes at least a full Fire I cast to finish the bulb, with the damage from my spell figured in. But on rare occasions, my party gets their damage spikes through crits/bloodletter procs/etc and gets killed significantly faster. It's a very rare occurance, but it does lead to the bug happening when it happens. Eventually, as my static's gear improves, this'll be less likely to occur, but it's still a bug that can on occasion cause problems and people should be aware of.

Now, get over yourself and stop accusing me of doing things wrong when I know for an absolute fact that I'm doing what needs to be done for the situation, and accept the warning about the bug for what it is.

Why you are the only one who get his rotation screwed? Ask that to yourself

[Synovius]

So I just read through 2-3 pages of the argument behind LetBloodline and YanderePrincess. After the 10 minutes or so it took to read through it all, I've determined your argument is retarded. You're literally arguing over whether it's okay to end a fight with Blizzard III or whether you should Scathe instead and then just Transpose. I mean, thanks for the bumps, but for @#^!s sake...

[YanderePrincess]

So I just read through 2-3 pages of the argument behind LetBloodline and YanderePrincess. After the 10 minutes or so it took to read through it all, I've determined your argument is retarded. You're literally arguing over whether it's okay to end a fight with Blizzard III or whether you should Scathe instead and then just Transpose. I mean, thanks for the bumps, but for @#^!s sake...

Actually, we're arguing about whether or not a fairly significant (though rarely occurring) bug exists. What you said we're arguing about isn't even -remotely- what we're arguing about, so maybe you should look in the mirror before you call anyone else retarded.

[Synovius]

Actually, we're arguing about whether or not a fairly significant (though rarely occurring) bug exists. What you said we're arguing about isn't even -remotely- what we're arguing about, so maybe you should look in the mirror before you call anyone else retarded.

I didn't call you or anyone else retarded. I called your argument retarded. It is.

[YanderePrincess]

Why you are the only one who get his rotation screwed? Ask that to yourself

Her, not his. And I highly doubt I'm the only one. However, it is a rare occurrence, even for me, and the times when it's most likely going to happen are times when it doesn't really make a big difference/can easily go unnoticed (such as thinking you simply let AF3 run out). A lot of people who have encountered it very likely just wrote it off without really caring what happened. When something in my rotation goes wrong, however, I seek out the cause and try to find a fix for it or at least understand why it's happening so I can know when it might happen and be prepared for it. The fact that it also happened in a situation where it caused a significant issue just made me more determined to find the cause.

[LetBloodline]

Her, not his. And I highly doubt I'm the only one. However, it is a rare occurrence, even for me, and the times when it's most likely going to happen are times when it doesn't really make a big difference/can easily go unnoticed (such as thinking you simply let AF3 run out). A lot of people who have encountered it very likely just wrote it off without really caring what happened. When something in my rotation goes wrong, however, I seek out the cause and try to find a fix for it or at least understand why it's happening so I can know when it might happen and be prepared for it. The fact that it also happened in a situation where it caused a significant issue just made me more determined to find the cause.

Easy answer. You miscalculated remaning life of mob