Incredibly Annoying Black Mage Issue Regarding Thundercloud

[RemoveMateria]

It's still a damage loss for something that wasn't the player's fault. If it's so minor, it should be a quick fix. It's completely senseless as to why anybody would want to waste Thundercloud on Thunder 1 or 2. There's no reason that Thundercloud shouldn't default to Thunder 3 damage even if 1 or 2 is pressed.

Also why is Thunder 2 a thing?

[Rongway]

It's completely senseless as to why anybody would want to waste Thundercloud on Thunder 1 or 2. There's no reason that Thundercloud shouldn't default to Thunder 3 damage even if 1 or 2 is pressed.

That you can use it on Thunder 1 or 2, and have to decide consciously not to use 1 or 2 when you could use it on 3 instead, is as much a part of the job as being able to activate forty mudras before pushing the Ninjutsu button is for Ninja. You have to make a decision as to which one to use. Game design isn't at fault if the one you choose isn't always the right one.

[randysquirrel]

You have to make a decision as to which one to use

That decision is "Do I use the proc that hits for 510 potency, or the proc that hits for 710 potency?"
There is literally never any time it would be a benefit to using the lesser proc. It's not as if they do different things and there is a decision process where you must decide which one fits the situation better, they literally do the same thing, except one hits harder and lasts longer

[Rongway]

it's proccing near mid button press and is being wasted on a skill you meant to cast normally. ._.

That decision is "Do I use the proc that hits for 510 potency, or the proc that hits for 710 potency?"
There is literally never any time it would be a benefit to using the lesser proc.

The problem here wasn't choosing the wrong ability, but choosing any ability too early. If there was time for it to proc before initiating the weaker spell, there was time to wait to see if it would proc before choosing which spell to cast.

We're BLMs. We know that RNGebus is a cruel master, and that he may spite us at any moment. If there isn't already a Thundercloud proc in advance of Thunder 1 time, then play Chicken with the Thunder 1 button. Press it at the last possible instant that lets you start casting without delaying your GCD.

[Shurrikhan]

That you can use it on Thunder 1 or 2, and have to decide consciously not to use 1 or 2 when you could use it on 3 instead, is as much a part of the job as being able to activate forty mudras before pushing the Ninjutsu button is for Ninja. You have to make a decision as to which one to use. Game design isn't at fault if the one you choose isn't always the right one.

The issue isn't the decision. Had Thundercloud not procced in-queue, Thunder III would have likely been the WRONG decision. The issue is simply that it can proc in-queue, or alternatively, in the one event that there is NO decision between I, II, and III, that it should simply use the III rather than opening the player up to annoyances that has nothing to do with BLM decision-making.

The only decision would be, for someone counting server ticks in their head, dare I save .2 seconds of uptime by queuing, rather than letting latency affect my next spell, or should I wait for the server tick to see if I got the proc. And given the positive feedback on the reduced Firestarter delay, I doubt that was some job-favorite concept (praise it's humble birth as client information delay, and may it rest in peace).

[Tarta]

Valid

This is what is annoying about this. Difference is huge after 8 minute fight.