Request: When you start casting, make it stop character movement and autoface the mob

[Majidah]

It used to be this way ...

I don't know why they took it out. You can keep it so that moving cancels the spell but getting that "You can't cast while moving" message, or having to stop and wait on the server delay is unnerving.

So yes. Please make it so that when you press a spell whilst running the character stops and turns to the mob.

(I know about the face mob button, but I use a gamepad yo! Still seems silly for it to exist..)

[darkstarpoet1]

It used to be this way ...

I don't know why they took it out. You can keep it so that moving cancels the spell but getting that "You can't cast while moving" message, or having to stop and wait on the server delay is unnerving.

So yes. Please make it so that when you press a spell whilst running the character stops and turns to the mob.

(I know about the face mob button, but I use a gamepad yo! Still seems silly for it to exist..)

this would have been a very simple solution to the whole issue.

if you are running and cast a spell it stops you and faces the target it would work for both keyboard users and the controller crowd. if you keep running after you hit a spell it cancels it, but at least it would give the controller users a way to face target without having to use a macro as a work around of a bad game design.

[Saiph]

i hope you get hit by eruptions!

[Klive]

http://forum.square-enix.com/ffxiv/t...940#post589940

From Yoshi

■Casting spells after moving ■

This is in regards to the time it takes before being able to cast a spell after moving, which we have received a lot of feedback on. There are two reasons for this specification.

①The time it takes to communicate between the client and server

　　　⇒This can take up to 0.3 seconds for transferring packets, plus the response time.
　　　　As an online game, this is unavoidable. (In order to prevent cheating, we cannot use the client only)

②Inability to cast due to movement intertia after stopping

　　　⇒We have reduced this spec as much as possible while maintaining the quality of our graphics.
　　　　Similarly to when /facetarget is used, if we reduce the inertia period any more, we would have to remove it. Since inertia is mapped in the server, it is not possible to cast spells during this time.

　　　　With that said, my decision is:
　　　　“If /facetarget is not used, minimize the negative hit to graphics quality”
　　　　“If /facetarget is used, prioritize performance over graphics quality”
　　　
I believe that this is the limit to what we can accomplish before the 2.0 re-launch.

Of course we have considered forcefully stopping the movement of the character’s feet as soon as a spell is cast, but this would be too substantial of a change. Also, we plan on implementing spells that can be cast while moving in version 2.0, so we would like to avoid this idea. (It would also be very difficult to separate spells between those that can/cannot be cast while moving, but we have more time to spend on this issue.)

[Jinko]

(It would also be very difficult to separate spells between those that can/cannot be cast while moving, but we have more time to spend on this issue.)

WHAT !! no its not, you just remove any movement check from the individual spell.

[darkstarpoet1]

i hope you get hit by eruptions!

learn to play your job and you don't have that worry. i didn't get hit by them before when you were stuck in animations and this wouldn't be any different.

it could have just been a mode option not the entire game forced that way if you don't like the idea, but i can assure you it's an option i would have taken in a heartbeat. like it was stated if you kept moving after it started casting the spell it would cancel. it's just like the /facetarget, but that a controller user would not have to map a key using a 3rd person program or use a macro for a work around.

i see zero difference.
running >hit /facetarget(your character stops and turns) >start casting spell > move to cancel
running> start casting the spell > it stops and turns you around > move to cancel

both ways have the same number of actions needed to stop and attack a mob. the second option would work better for a controller user due to it would be completely based on keys already on the controller(no mapping/macros needed).

[Jinko]

How come other MMO's don't have this issue with moving and casting ?

[AceofRains]

Is this autofaces thing and stopping before casting really that hard? I'm just wondering cuz I've had no trouble
I don't know of it's cuz I'm a controller user or what tho.
But you don't HAVE to autoface if that's the impression you get. I think autoface is just meant so you don't get back attacked while casting.

[darkstarpoet1]

Is this autofaces thing and stopping before casting really that hard? I'm just wondering cuz I've had no trouble
I don't know of it's cuz I'm a controller user or what tho.
But you don't HAVE to autoface if that's the impression you get. I think autoface is just meant so you don't get back attacked while casting.

no what they are using /facetarget for is basically nothing more than a stop button. it sends info directly to the server that you are stopped moving and you can directly start casting a spell instead of having the delay while the server figures out your position. all we were asking for is that for a controller user to add a battle mode where we could turn off face target as a key press and make it to where the start of the spell would be a stop.

this method would have a button on the controller to send the info to the server so we get the same delay as keyboard users get. right now there is a difference in response times for a controller user to begin casting spells compared to a keyboard user that actually has a button they can hit to begin instantly.

edit: facetarget is not just turning and facing a target. it tells the server you have stopped moving so you can instantly begin spell casting. we are using facetarget as just the use it has not actually the turning towards the mob. it's just the ability to say you are stopped as soon as you hit it instead of the delay from running.

a keyboard user can be running and hit facetarget and they stop running and turn so they can start casting instantly whereas the controller user runs and stops and then has to wait for the server to register it.

[Klive]

If using a controller, I would make a /facetarget macro. It is not perfect it is better than nothing.