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!

[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).

[Saiph]

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).

i know how to play my job. dont need any face target buttons or forced spellcasting to cast spells.

[Krausus]

learn to play your job and you don't have that worry.

ohhhh the irony

[darkstarpoet1]

ohhhh the irony

that was in response to getting hit by eruptions because of getting stuck casting. if people weren't getting stuck before then the change suggested wouldn't have changed that if the person played properly.

you avoided them just like everyone else.

just saying that if you cast while running on a controller it registers you as a stop button just like /facetarget does for keyboard users then if you continue running it cancels you wind up with the same system for controller users that keyboard users have. the only difference is for controller users is they do not have the /facetarget button on the controller so it does need to be added.

we're not asking for it to be completely removed, but to have the bad design fixed so it works for both types of players.

[Razorboi82]

that was in response to getting hit by eruptions because of getting stuck casting. if people weren't getting stuck before then the change suggested wouldn't have changed that if the person played properly.

you avoided them just like everyone else.

just saying that if you cast while running on a controller it registers you as a stop button just like /facetarget does for keyboard users then if you continue running it cancels you wind up with the same system for controller users that keyboard users have. the only difference is for controller users is they do not have the /facetarget button on the controller so it does need to be added.

we're not asking for it to be completely removed, but to have the bad design fixed so it works for both types of players.

Actually the thread asks for the old way to be re-instated. in all seriousness though this guy always complains about Everything in game that doesn't make things better for him, then gets butt hurt when people see some flaw in his rage. Much better to start a thread with the proper wording for what you are trying to say. Power Ranger shouldn't be taken seriously.

[Krausus]

that was in response to getting hit by eruptions because of getting stuck casting. if people weren't getting stuck before then the change suggested wouldn't have changed that if the person played properly.

you avoided them just like everyone else.

just saying that if you cast while running on a controller it registers you as a stop button just like /facetarget does for keyboard users then if you continue running it cancels you wind up with the same system for controller users that keyboard users have. the only difference is for controller users is they do not have the /facetarget button on the controller so it does need to be added.

we're not asking for it to be completely removed, but to have the bad design fixed so it works for both types of players.

It's ironic that you are telling someone else to learn to play when you yourself rage about not being able to effectively adjust to recent casting changes.

[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.)