The Black Mage Rotations

[LetBloodline]

I'm not getting interrupted, which is what you're insisting is happening

I know you are not interrupted, i never thinked that way

But your hit land after the mob is dead => you wasted a cast since the damage you whould have done are wasted anyway on a dead corpse => you should never waste a cast vital like blizzard 3 => cast time of blizzard 3 while in AF3 is ridicusly small and if in that little time frame the mob die and you don't get UI3 it means that you should have switched targets before cast B3

We are not misunderstending you as you beleave. The wasted cast matter is not "getting interrupted" but cast a spell that won't help in the fight (i.e. beating a dead horse ) and come here asking why you didn't get your UI stack. The answer is that that situation must not happen. You have varius way to do so and should adjust your play accordingly

[Adamantium]

...I don't think this is a bug though, its a probably a result of the flare fixes they have done. (much like the fire/ice ticks from 2.0 -> 2.1) Thanks for posting about the change.. but really if three people seem to have misunderstood what you were conveying... eh.

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.

[LetBloodline]

Double post for some reason O.o

[LetBloodline]

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.

At start ppl didn't get that the difference was the remove of UI before the hit and a legend about mana tiks started. Nothing changed in mana tik but you just loosed UI before of when they where used

[Dextro]

I've noticed something similar to what you're talking about, but never on normal enemies.

Back when we had the old Astral/Umbral system, if you were to cast a Blizzard III that lands right as Titan becomes un-targetable and jumps out of the arena, the cast would miss and you'd remain in Astral III. Not a big deal.

However, if were to do the same thing post-patch, not only would you still not receive Umbral III, but your Astral III would be removed also - leaving you with nothing.

This happens because Astral is removed upon completion of the cast, but the Umbral application is dependent upon the Blizzard III actually landing while the mob is still a valid target.

The switch mechanic, which used to be a seamless transition before, now has a slight delay between removal and application, making what you describe possible, albeit extremely rare.
I've reached the character length cap, so i'll explain more in a 2nd post

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

[Dextro]

^Continuing from previous post.

On regular enemies, most of you can probably attest to seeing one of your spells land when the enemy was technically already dead.
The most common and notable instance of this is landing a killshot with Fire, but weaving in a Firestarter straight afterwards anyway, leading to a ton of overkill damage that isn't needed, but is still displayed.

Now, in contrast, there are moments where you may have seen your spell land, but the damage was not displayed, likely due to (but not limited to) an invulnerability mechanic, or instance of leaving the arena.
In this scenario, where your damage was not displayed, is where your Fire III <> Blizzard III transition has the small probability of you being left with neither buff.

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

[YanderePrincess]

<snip>

The thing is, the cast isn't wasted since the primary purpose of Blizzard III is to switch to Umbral Ice 3. The fact that it also can do damage is secondary, as we'd still use Blizzard III at that point in our rotation even if it always did 0 damage. And, there's a 90% chance that the damage from the Blizzard III is, not only not wasted, but crucial to killing the Bulb on time, thus making it necessary for me to cast that spell at that time, which you seem utterly oblivious to.

Look at your "logic" again. You have flatly stated "If there is a 10% chance the spell is not needed, do not cast it." which equates to "If there is a 90% chance you must cast that spell, do not cast it." Do you realize how dumb you sound?

And since it's only 10% of the time the already rare instances that I'm having to cast Blizzard III at that point in the bulb's existence, the chance of the bug screwing me over is low enough to be completely worth the risk since my damage (even from a mere Blizzard III in AF3) is almost always required to finish the bulb on time with our current overall DPS.

So no, contrary to your misguided idiocy, I'm not a bad blm, nor am I playing the situation wrong, nor am I "whining." I'm letting the rest of you know that if you end up with a Blizzard III landing around the time a mob dies, pay attention in case you also get the bug because it can royally screw your rotation if you don't notice it until it's too late. Since I'm aware of the bug now, I can compensate and keep it from completely screwing over my rotation, though it is still an inconvenience on the occasions it happens.

So get over yourself and take information for what it is so that you can be aware of it on the off chance it happens to you, too, rather than being a shitty blm who refuses to be aware of potential issues because you'd rather believe you're superior to everyone else.

[YanderePrincess]

However, if were to do the same thing post-patch, not only would you still not receive Umbral III, but your Astral III would be removed also - leaving you with nothing.

After which patch? 2.1? I've not had that particular issue. Invincible targets simply pop up "invincible" and no change in AF3/UI3 occurs. Though, that's specifically how I remember it being before 2.3, so I'll try testing it again next time someone resets a hunt mob while I'm in Astral Fire.