[dev1149] Please bring back the queuing of actions!

[Catapult]

Everyone complained that you could,

SE takes it out.

Now we are going to complain you cant?

I have no recollection of this. Where did this happen? I want to smack those who partook.
If you don't like spell queuing you could have just not queued your spells.

Once the latency between client and server is eliminated, you won't miss queueing so much.

Which will never happen to a sufficient standard for people living outside Japan.
Here in Australia, I still get a 0.5-1 second ping delay when pinging Tokyo and that's before server and client processing time is taken into account. It's wishful thinking.

Summing up my post in the last topic, if you are going to remove the ability-queuing, there needs to be a clear visual indicator of when it is possible or not possible to input an action. Currently, I can input an action and get the same response regardless of whether or not it was a successful input. I don't find out I was unsuccessful until I see my character just standing there dumb doing nothing while the people around me die.

[Rane]

It's not the distance that's causing the lag, it's the game. When I was living in Japan I occasionally played WoW on U.S. east coast servers. My ping was usually about 200 milliseconds or so. No noticeable lag while playing.

I think that we need the UI to do a better job of telling us when actions can and can't be used. It would be best if abilities were slightly grayed out while readying or performing an action. That way it would be obvious if you tried to enter a command too early. I'm guessing that they can't do this at the moment since you need to be able to hit spell buttons two times in order to cancel casting. However, it might become a viable system after they add ESC key and jump button spell cancelling.

I really didn't like ability queuing because it often stuck me in an ability chain, preventing me from reacting quickly to changing battle conditions. I find the battle system to be smother without queuing.

[feint2021]

After doing the beast camps the battle system seems to be very clunky now. It's hard to see what your character is even doing when you're fighting 5 giant mobs with another 4 spamming on top of your party of 8. It's almost like when we had to keep spamming 11111111111111 to attack except it's with every other skill now. Maybe it's just going to take some adjusting to but as of right now it's a bit annoying.

[Bahn]

+1 to bring back ability queuing. That needs to be there because of the inherent UI latency (or what others call lag). It's the best way (short of reprogramming the game from scratch to not include that stupid input latency) to compensate for it. Seeing how Yoshida and co. said that that is something they can't easily remove from the game, queuing is the best thing we can have to overcome that.

[BeePee]

Yup, before you could execute a weaponskill, and press/click on the next action. Bam, went off nice and smooth.

Now, it's either press/click an action and wait wait wait for the animation to finish, and then do your next.
Or even better, press/click for the action, then button mash / click spam until you finally get the next one to go.

So clunky now.

[Misteyes]

Also in favor of bringing it back. Not a "queue" but at least a single combat action ready.

In the past, it was slightly inconvenient to ready a switch to passive mode after entering active mode by double-tapping F by accident, but that's not half as inconvenient as this new lack of a system.

[Echo]

The complaints I recall about this feature is how certain abilities overlapped with one another, which was a purely cosmetic problem. I did not mind, and never had an issue with it, because it made combat flow so much more smoothly and reduced the appearance of client-server latency. This is a classic case of be careful what you wish for. Spellcasting in particular has become a lot more difficult. With how carefully you have to manage the party's HP, your MP, and the timing of skills like Spiritsong (formerly Spiritbind), every single second counts. Also, I don't know about other healers, but I'm constantly busy and juggling three different ability bars. Between casting debuffs, healing, buffing and everything else going on... that's a lot of repeated skill use. Losing the queue not only makes combat flow less smoothly, it detracts from the fun of the game and introduces difficulty from outside the scope of the game in the form of fighting with the client to do what you want it to do.

[Catapult]

The complaints I recall about this feature is how certain abilities overlapped with one another, which was a purely cosmetic problem. I did not mind, and never had an issue with it, because it made combat flow so much more smoothly and reduced the appearance of client-server latency. This is a classic case of be careful what you wish for. Spellcasting in particular has become a lot more difficult. With how carefully you have to manage the party's HP, your MP, and the timing of skills like Spiritsong (formerly Spiritbind), every single second counts. Also, I don't know about other healers, but I'm constantly busy and juggling three different ability bars. Between casting debuffs, healing, buffing and everything else going on... that's a lot of repeated skill use. Losing the queue not only makes combat flow less smoothly, it detracts from the fun of the game and introduces difficulty from outside the scope of the game in the form of fighting with the client to do what you want it to do.

This.

Fight the mobs, not the interface. A well built combat interface makes you forget it is there (without wanting to touch the immersion subject).

[Answa]

Not queueing is fine. I don't feel it being clunky at all. Took me all of... 10 minutes to get used to it. It's just different, which people love to instantly assume means it's bad.

People loooove to bitch.

[Tiraelina]

If they want to have a worldwide market the game needs to have at minimum a 1 skill deep queue. It's the only way to get around the latency issues for players outside of Japan. Forcing network latency into when you can *start* using your next skill has nothing to do with skill.

There's already enough issues with the cast bar and cooldowns being a lie.