Moving will be made to interrupt spellcasting at a point in time...

[Eldaena]

Because it adds more flavor~ to the battles. It makes fighting in groups more interesting. Before this change, people in parties were able be off in their own world, doing their own thing like they're soloing. Of course they were able to do this for other reasons too, but one factor that contributed to this happening was that healers were able to easily run around and support reckless gameplay. Now that we can't, the people that continue to play recklessly not thinking about position are going to die and think the healer's bad. And then the healers that feel like they're flawed because they can't do the impossible whine about not being able to do their job.

In other words, the ability to cast while moving was not balanced. Not just for pvp, but for anything that is done in parties. Why? Because it allowed people to do things they shouldn't be allowed to do.

"Should" and "shouldn't" is left up to the developers. They may have changed the system, but that doesn't mean things weren't working as intended before. I've run with a lot of different groups of people recently, helping with job quests and such, and I can accurately say, people are still in their own world even if they are aware of the spellcaster's new dismay. I play white mage and I just plant myself somewhere and heal. The limitations of people being too far away are still the same as before the change, but I feel like overall this change has given us less options in combat, rather than more. Also, to me it feels unfair if I accidentally inch myself forward my spell cancels, yet melee classes are just going to town on a mob and running all over, not restricted at all. Like I said before, maybe the developers think this is balance, but I felt more on par with other combat classes before, now I feel less useful in general.

[Reaujien]

"Should" and "shouldn't" is left up to the developers. They may have changed the system, but that doesn't mean things weren't working as intended before. I've run with a lot of different groups of people recently, helping with job quests and such, and I can accurately say, people are still in their own world even if they are aware of the spellcaster's new dismay. I play white mage and I just plant myself somewhere and heal. The limitations of people being too far away are still the same as before the change, but I feel like overall this change has given us less options in combat, rather than more. Also, to me it feels unfair if I accidentally inch myself forward my spell cancels, yet melee classes are just going to town on a mob and running all over, not restricted at all. Like I said before, maybe the developers think this is balance, but I felt more on par with other combat classes before, now I feel less useful in general.

(Regarded what I bolded in your statement) - Did you just make that up?

Have you played a melee class both before and after this update? They still can suffer from the same consequences as before - that is, chasing a mob who's right in front of you on your screen but not according to the server and not being able to attack. And then as soon as it stops some other person (be it a DD mage, healer, or tank) pulls hate from the other side of the battle field and then the chase happens all over again. This is one of the [bigger] reasons why ARCs do SO much more DD in fights similar to the Moogle fight than any other physical DDer simply because they don't have to follow the mob around as much as melee do. As it is right now, LNC/DRG don't have it so hard when mobs move around but that's only because they have the longest range for melee DD but they can still find themselves lol-ingly chasing the mob, whereas MRD/WAR and especially PGL/MNK have to really be on the mobs' ass' in order to ensure they'll always be in range. Of course, that's one of the trade-offs between melee vs. range.

How balanced was it that mages could be in range to attack the mob 100% of the time even when it's moving? And even if the mob starts to move out of range during mid cast you could have still moved and it wouldn't interrupt... and that's "fair"?!

(... and before anyone wants to mention that melee/physical DD doesn't have to worry about MP, they would do well to remember 1) PGL/MNK do for their auto-attacks, and, most importantly, 2) they do have to manage/use the TP just as strategically as mages do their MP)

[Eldaena]

(Regarded what I bolded in your statement) - Did you just make that up?

Have you played a melee class both before and after this update? They still can suffer from the same consequences as before - that is, chasing a mob who's right in front of you on your screen but not according to the server and not being able to attack. And then as soon as it stops some other person (be it a DD mage, healer, or tank) pulls hate from the other side of the battle field and then the chase happens all over again. This is one of the [bigger] reasons why ARCs do SO much more DD in fights similar to the Moogle fight than any other physical DDer simply because they don't have to follow the mob around as much as melee do. As it is right now, LNC/DRG don't have it so hard when mobs move around but that's only because they have the longest range for melee DD but they can still find themselves lol-ingly chasing the mob, whereas MRD/WAR and especially PGL/MNK have to really be on the mobs' ass' in order to ensure they'll always be in range. Of course, that's one of the trade-offs between melee vs. range.

How balanced was it that mages could be in range to attack the mob 100% of the time even when it's moving? And even if the mob starts to move out of range during mid cast you could have still moved and it wouldn't interrupt... and that's "fair"?!

(... and before anyone wants to mention that melee/physical DD doesn't have to worry about MP, they would do well to remember 1) PGL/MNK do for their auto-attacks, and, most importantly, 2) they do have to manage/use the TP just as strategically as mages do their MP)

Server response is a big reason people do not like the new changes to casting. It's the same for melee too that server response hinders you. I didn't mean to attack you with what I said, if you feel that I have, but my point was I see people running around a lot AND hitting things as melee, and not running around and not hitting things as you have described.

[Krausus]

Server response is a big reason people do not like the new changes to casting. It's the same for melee too that server response hinders you. I didn't mean to attack you with what I said, if you feel that I have, but my point was I see people running around a lot AND hitting things as melee, and not running around and not hitting things as you have described.

really because it literally took less then half a second for my game to register that my character stopped moving after letting go of the joystick, if people are having major issues with it then they are doing it wrong.

[Eldaena]

really because it literally took less then half a second for my game to register that my character stopped moving after letting go of the joystick, if people are having major issues with it then they are doing it wrong.

I do not use /facetarget and I do not wish too. However, if I move, as soon as I stop I try to cast something.... oh but wait! The server has to catch up with me. lol Usually I can't cast immediately after stopping, so I am waiting for my spell to happen, then realize it hasn't gone off... lol. Then I have to click it again. =p I know in time I will be used to the wait, but this is what I'm talking about and how it conflicts with us casters.

[Krausus]

I do not use /facetarget and I do not wish too. However, if I move, as soon as I stop I try to cast something.... oh but wait! The server has to catch up with me. lol Usually I can't cast immediately after stopping, so I am waiting for my spell to happen, then realize it hasn't gone off... lol. Then I have to click it again. =p I know in time I will be used to the wait, but this is what I'm talking about and how it conflicts with us casters.

I dont use /facetarget either since I use a controller but like I said it takes very little time to register your character has stopped moving. If I can do it without issue and still be great at healing and have a 12 pack in me I'm sure most people can do it as well it just takes getting used to and remembering to not rely on casting being the thing that stops you, watch the arrows for a bit to help ya out. Its just an adjustment period.

[Eldaena]

I dont use /facetarget either since I use a controller but like I said it takes very little time to register your character has stopped moving. If I can do it without issue and still be great at healing and have a 12 pack in me I'm sure most people can do it as well it just takes getting used to and remembering to not rely on casting being the thing that stops you, watch the arrows for a bit to help ya out. Its just an adjustment period.

Well, maybe I'm mistaken, but isn't it like this now?

Example: A melee and a mage both start running from point A to point B. When they get to point B, the melee will be able to use a weaponskill as soon as they get there, or even before. A mage however, cannot cast before they get to point B and when they get to point B they either have to use /facetarget or wait a bit longer than a melee would have to, to use a weaponskill, before a mage can begin casting. Then, when a mage is able to cast and does so, that too takes casting time, whereas a weaponskill is used automatically. <--- Shiggysonson this is why it feels a little unfair to me.

Edit: Example with full MP, full TP, and no instant spellcasting spells.

[Shiggysonson]

I do not use /facetarget and I do not wish too. However, if I move, as soon as I stop I try to cast something.... oh but wait! The server has to catch up with me. lol Usually I can't cast immediately after stopping, so I am waiting for my spell to happen, then realize it hasn't gone off... lol. Then I have to click it again. =p I know in time I will be used to the wait, but this is what I'm talking about and how it conflicts with us casters.

/facetarget is the temporary solution for the exact problem you're complaining about. If you refuse to use it for whatever reason, you shouldn't really be complaining at all. And a white mage that clicks spells... maybe there are other reasons why you're having issues playing effectively....

[darkstarpoet1]

/facetarget is the temporary solution for the exact problem you're complaining about. If you refuse to use it for whatever reason, you shouldn't really be complaining at all. And a white mage that clicks spells... maybe there are other reasons why you're having issues playing effectively....

yeah the issue is horrible servers and bad design and programming in putting it in game. hey, if that's the excuse of why everything the original team put in that didn't work right then it fits here too.

[Reaujien]

Server response is a big reason people do not like the new changes to casting. It's the same for melee too that server response hinders you. I didn't mean to attack you with what I said, if you feel that I have, but my point was I see people running around a lot AND hitting things as melee, and not running around and not hitting things as you have described.

I didn't feel you were attacking me. I just don't understand why players think that melee have some sort of magical advantage over mages now that mages can't run while casting... (or heck, maybe they thought that before 1.21 :/). Also the client-server communication issues effects everyone equally; just in different ways. For as many times I have had a mob run out of my range while casting (pre 1.21) even though it appears to be in range of my spell I can say has been nearly the same amount of times (give or take) as I've had to chase a mob while not being able to attack all while it appearing right in front of me the entire time...

Clearly the dev's thought it was unbalanced that mages could cast while they run - which is why they made the change in 1.21 and gave us [temporary] tools to mitigate inabilities to cast spells immediately upon stopping until 2.0 comes out.