BLM's Losing Flare> Convert> Flare

[OrionInerghem]

So I get that it was a "buglol" as they are calling it, but taking away a situational trick is really necessary?

You know what will happen? Now people will just take 2x BLM in WP SRs (if that's still viable)


Bard is losing 1 cross-class ability

and BLM is either prob going to have a CD on Flare or lose Convert, Sounds like we might have gotten the biggest nerf.

[Tupsi]

So I get that it was a "buglol" as they are calling it, but taking away a situational trick is really necessary?

Yes fixing bugs are necessary - no BLMs aren't nerfed as they aren't losing anything as an intended function.

[Nura]

What it was a bug? You can only use it like so less. If they are going to nerv that I demand a nerf of the WHM Holy spell. And not only in Damage but CD also. God dang it.

[Starkbeaumont]

eh the bug is that you could actually if timed right could do flare out of umbral ice still get a tic mp and do another fast casted flare. has nothing to do with convert

[ispano]

Yeah, you will still be able to Flare > Convert/Pot/Ballad > Flare, without issue. The bug is as Stark said.

[banned]

So I get that it was a "buglol" as they are calling it, but taking away a situational trick is really necessary?

You know what will happen? Now people will just take 2x BLM in WP SRs (if that's still viable)


Bard is losing 1 cross-class ability

and BLM is either prob going to have a CD on Flare or lose Convert, Sounds like we might have gotten the biggest nerf.

yes indeed

[Ri_ri]

Convert: lose some HP to recover MP.
Flare: use all your remaining MP to deal area damage.
Swiftcast: next spell with a casting time executes instantly.

Where's the bug into using them together? I'm sure everyone thought it was the intended combo, lol.

That was not the unintended use. From what I understand, this is what the unintended use is:

1. Blizzard III (or Blizzard II if you are in melee range)
2. Flare III at the reduced casting time granted from Umbral Ice
3. Because there was a slight delay in Umbral Ice being overwritten by the Astral Fire from Flare, if it was timed correctly you would get a pulse of mp from Umbral Ice after Flare was cast and before Umbral Ice was overwritten. <-- This is the unintended step.
4. Swiftcast if up and cast Flare a second time.
5. Convert if up and cast Flare a third time.
6. Repeat.

That's three flares all within seconds of eachother. Since it is possible to cast a Flare every 7 or 8 seconds, it was potentially allowing two Flares every 7 to 8 seconds, with a third Flare once a minute. What they're doing is removing the capability of doing step 3, since that was unintended. All the other steps will still be there. I.e. It will still be possible to cast a Flare every 7 to 8 seconds and to chain two Flares back to back once a minute.

Ooh, that.

I wonder if they'll be fixing the "abuse" where you can cast two fire spells with increased speed from Umbral III.

[OrionInerghem]

Yeah, you will still be able to Flare > Convert/Pot/Ballad > Flare, without issue. The bug is as Stark said.

Black Mage:
While we focused on buffing the melee DPS classes/jobs for this patch, we do not have any plans to buff the black mage job. On a side note, there was a bug that caused players to be able to use flare twice in a row, but that will be addressed.


Hmm Well I would like some confirmation here, as the 1 tick of ice really doesn't seem that OP to me either

[Anayrie]

If I'm not adding flare in with my fire spells, I'll cast it when about to rehash the cycle and gain mana back. So switch to umbral ice, cast flare and sometimes I'd still have mana and get another a flare in back to back without needing to switch to umbral ice or convert. It usually messes my rotation up so I don't mind a fix.

[Mhaeric]

Convert: lose some HP to recover MP.
Flare: use all your remaining MP to deal area damage.
Swiftcast: next spell with a casting time executes instantly.

Where's the bug into using them together? I'm sure everyone thought it was the intended combo, lol.

That was not the unintended use. From what I understand, this is what the unintended use is:

1. Blizzard III (or Blizzard II if you are in melee range)
2. Flare at the reduced casting time granted from Umbral Ice
3. Because there was a slight delay in Umbral Ice being overwritten by the Astral Fire from Flare, if it was timed correctly you would get a pulse of mp from Umbral Ice after Flare was cast and before Umbral Ice was overwritten. <-- This is the unintended step.
4. Swiftcast if up and cast Flare a second time.
5. Convert if up and cast Flare a third time.
6. Repeat.

That's three flares all within seconds of eachother. Since it is possible to cast a Flare every 7 or 8 seconds, it was potentially allowing two Flares every 7 to 8 seconds, with a third Flare once a minute. What they're doing is removing the capability of doing step 3, since that was unintended. All the other steps will still be there. I.e. It will still be possible to cast a Flare every 7 to 8 seconds and to chain two Flares back to back once a minute.