Black Mage Casting Glitches

[JackFross]

I mean...

I haven't hit 60 on my BLM yet, but I'm fairly certain that every issue in this thread is solved by simply... dealing with it?

1- You can't F3>F4 so just do F3>F1>F4. It doesn't change much *and* gives you the potential of a F3 proc, which lets you use an additional F4 before having to cast another AF spell.

2- Firestarter isn't a thing at 60, since you should never be doing F1>F1 anymore. If you are, you lost Enochian, which is another way of saying "you messed up." Punishment for failing to properly execute your class.

3- You should really not be casting Fire that late in AF that you are left wondering which state you'll be in. It all depends what the state is when the cast finishes. If you don't have enough time left to finish the cast, don't cast it. Easy. Or just... don't get yourself in that situation. Swiftcast is a spell you have.

4- AF doesn't run out during Transpose. It runs out before you clicked Transpose. You need to be quicker hitting it, though I'm honestly very curious as to when this would ever be an issue, since your AF/UI should never be close to 0s when you use Transpose.

5- You shouldn't be casting B4 or F4 if your UI or AF or Enochian is going to wear off during the cast. You should have been using B4 a cast sooner. You should have been in UI two casts ago to re-activate Enochian. You should have been casting F1 or F3 a cast ago (or this current cast) to maintain stacks.

All of it is solved by simply dealing with these intended consequences for screwing up the way you're playing the class.


As for Chako above - no. That shouldn't be happening. The only reason it does is because you cast your F1 and waited for the proc to activate before hitting F3 immediately, which, besides being the wrong way to play the class, can result in the above issue, since you hit it in the time between "i saw the proc" and "the server registered the proc." The game functions on a heartbeat. You see things happen in real time, but the server only updates the information that i has once every 400-ish milliseconds. This means that, if your proc appears at the start of a heartbeat, you have 400ms where IF YOU HIT IT, the server will think you did not actually have that proc.


And last - Transpose and Convert sharing a cd is the absolute worst possible idea. Convert on a 12s cooldown would allow you to stay in Fire literally forever by just constantly using Convert, casting more fire spells, waiting a couple seconds, and converting again. Like - it should probably have a somewhat shorter cooldown, sure, but not the same length as Transpose - and Transpose shouldn't be any longer than it is, due to the reason you use it and how frequently you need to use it at lower levels to not be shit.