BLM possibly bugged?

When I have 3 stacks of Astral Fire and I cast Blizzard 3, if the spell miss or the target is invulnerable, then I lose the 3 fire stacks but I won't gain the 3 ice stacks. The same thing happens when I cast Fire 3 with 3 ice stacks.

But if you have 1-2 stacks of fire and cast a Blizzard 3 or vice versa, if the spell miss/target's invulnerable you won't lose your current stacks.

I've been noticing this a lot lately especially on fights where the boss temporarily becomes invulnerable such as Atomos and Thanatos on CT or Primals during their huge AOE cast (such as Ifrit's Hellfire).

What do you guys think? Is this working as intended or does the double dip supposed fix actually spawn another bug?

Working as intended.

The entire game works this way, if the damage does not apply, the side effect associated with it won't ably. Example would be ManaWall High Voltage on either of ADS fights, you won't get damaged therefore you won't get paralysed.

Quote:

---

Originally Posted by NeoAmon

Working as intended.

The entire game works this way, if the damage does not apply, the side effect associated with it won't ably. Example would be ManaWall High Voltage on either of ADS fights, you won't get damaged therefore you won't get paralysed.

---

But if the side effect isn't applying, he shouldn't be losing what stacks he already has. . .

Yes I get that you shouldn't get the buff if your spells miss. But my point is you shouldn't lose your current buff either.

The side effect of Blizzard 3 is giving 3 ice stacks AND remove fire stacks. If the spell doesn't work, why do we get the partial side effect?

Quote:

---

Originally Posted by rowrow

Yes I get that you shouldn't get the buff if your spells miss. But my point is you shouldn't lose your current buff either.

The side effect of Blizzard 3 is giving 3 ice stacks AND remove fire stacks. If the spell doesn't work, why do we get the partial side effect?

---

Hmm never noticed that to be honest, you sure it is not just the timer going out? Or maybe the game counting the cast itself as the main trigger for UI & AI cancellation.

Tested it by leashing mobs. When the mob walks back to its original position, it temporarily becomes invulnerable. I had 3 stacks of fire with about 5-6 secs left then swiftcasted Blizzard 3. I ended up with neither buff.

Starting the cast itself doesn't remove the buff since you can move and cancel the cast and you won't lose your current stacks.

Prior to 2.1, Astral Fire and Umbral Ice were only removed and applied when a spell hit. However, in order to fix the double dipping into UI3 that Yoshida stated was allowing Flare to be cast twice, they made it so that the buffs are removed on cast (in the case of going from Umbral/Astral to Astral/Umbral) and applied on hit.

Sucks, but that's how it is.

You lose the buff now when the spell is cast.
But keep in mind you lose it too if you allow the cast to be finished and the spell fails, by facing the wrong direction, having the mob run out of range or hitting an "invulnerable", for exemple.
In other words, you need to pay a lot more attention to where you are compared to the mob you target.

Ive noticed this while going through Coil and doing extremes. 1st time it happened i was like "WTF?!" lol. I started testing it and it even happened when everything was "ideal" (not invulnerable, im facing mob, mob not running to a different spot, etc.). It doesn't happen a whole lot, but when it does....boy do things get slow for a little while xD

Quote:

---

Originally Posted by Adamantium

Prior to 2.1, Astral Fire and Umbral Ice were only removed and applied when a spell hit. However, in order to fix the double dipping into UI3 that Yoshida stated was allowing Flare to be cast twice, they made it so that the buffs are removed on cast (in the case of going from Umbral/Astral to Astral/Umbral) and applied on hit.

Sucks, but that's how it is.

---

Wrong.
It is removed 0.5sec before the spell is cast and it only happens when you are under AF 3 or UI 3.
Test it by yourself, UI 1 and 2 are not removed before the spell hits, only UI 3 does. And that sucks for sure.
Why should our UI 3 be removed before the spell hits ? They could simply work harder and fix the double dip flare without this kind of amateurish fix.
Or at least do the same with Firestarter procs ?

I've been noticing this problem alot as well. Many times Blizzard 3 will go off and connect fine but I notice that for whatever reason it won't regen anything. This is happening very often and I've even tested it out when it happens just standing there and it doesn't regen any mp throwing my rotations off everytime.

Quote:

---

Originally Posted by Louro999

Wrong.
It is removed 0.5sec before the spell is cast and it only happens when you are under AF 3 or UI 3.
Test it by yourself, UI 1 and 2 are not removed before the spell hits, only UI 3 does. And that sucks for sure.
Why should our UI 3 be removed before the spell hits ? They could simply work harder and fix the double dip flare without this kind of amateurish fix.
Or at least do the same with Firestarter procs ?

---

By "on cast", I meant when the spell is finished casting. 0.5 seconds left on your cast time is pretty much finished casting due to the latency in this game. Guess I should have clarified. ;< I don't spend a lot of time in UI/AF 1/2, so I never noticed that issue, but it makes sense considering you don't get halved casting times.

They definitely could have found a different fix, but I think they just wanted to get rid of double dipping in general, and Yoshida used Flare as an example.

I actually really like the newer behavior because now, when casting Fire III right after building up to Umbral Ice III, the cast time reduction doesn't get all snarled up and confused and cause me to sit there for 6 seconds "casting" Fire III with no visible cast bar.

Its because of SE's sloppy "fix" for double flaring. It just happened to break a ton of other things with the class.