The Ability to Ready a Spell While Casting - Why Was It Removed?

im playing my CON in a leve right now and its rediculous.
while in passive mode, you have to wait for your arm to go back down to your characters side in order to cast your next ability. this is very unnecessary.
maybe we dont need a que, but we should be able to start our next spell right after the charge bar completes for your previous spell. we shouldnt have to wait for the entire animation from start to finish to start our next spell... then on top of it theres that damned server lag.

I would love to know the reason they took it out. It might be a very good/valid reason, or not.

I agree.
It's really frustrating and feels clunky.

I did not like the removal of this feature, I'm still getting used to it and find myself going "wait what, oh yeah I didn't cast a spell, because the game doesn't register the cast if I hit it before I'm done casting the previous spell".....lame.

I fully support the OP on this.

Quote:

---

Originally Posted by Catapult

I have to concur with the OP.

This is an international game. Unless something magically changes, someone will always be having some form or other of lag issues, be it related to the servers being in distant Japan or their own service being somewhat less reliable.

Being able to queue the next spell ensured that players (myself included) were not disadvantaged as a consequence of the lag. But now, it seems I'm relying on a guess as to whether or not I'm ready to cast a spell or not.

The worst bit is, you can still make the input and without any form of error message. So you may think it was ok to start your next spell, but you don't find out it wasn't until you're realizing that nothing is happening. Things start clogging up, and you get frustrated because that was valuable combat time you could have been making use of to not die in the now harder content.

Something needs to be done. If the queuing is not to be reinstated, then the ability to input in such scenarios needs to at least be visually restricted to make it 100% clear what position your caster is in, regardless of latency. Ironically, the easiest solution to this in my opinion would be to allow a spell queue.

---

Thank you, this is what I mean, you explain it better than me XD

Got to agree, it feels so much slower. Getting used to it though but still not enjoyable.

This bothers me as well, and not just for magic but for all actions. It's more difficult to get into the rhythm of a combat now. It just doesn't flow smoothly anymore. Instead, I now have to wait until after my "turn" comes up, then try to hit the button as fast as I can; but not too soon... Maybe this is somebody's answer to the complaint that FFXIV isn't a "twitch" game like "modern" MMOs (in fact that it *can't* be, ostensibly because of lag.)

The fact is, FFXIV will never be a "twitch" game because Final Fantasy is not a "twitch" game. Lag doesn't enter into it.

Also, it's kind of funny to hear people now saying the ability to "Ready" the next action helped compensate for lag when previously, people were quoting it as a brazen demonstration of lag...
The ever sinking feeling in the pit of my stomach suggests they removed it for just this reason, but that can't be true... The developers would never rewrite game mechanics just to pander to some whiner... right?

Not "ha ha" funny, but... you know... </sigh>

This change makes it very difficult to excel at playing on the Gamepad... On the keyboard it's not so hard to slam the same number key multiple times until it lets the action through, but with the gamepad you have to manage the cursor. I would say that before 1.19 removed this queue, the gamepad and keyboard were more comparable, now it really feels like I am at a huge disadvantage on the game pad. :/

This is VERY irritating, quite a lot of the time I try to cast then it says I can't, so then I have to attempt it again. It's so clunky and I can't smoothly move from casting Scourge to Banish for example, I have to wait for a few seconds in between. It's ridiculous. And my castbar fills up then I seem to have another few seconds of waiting before it actually does anything.