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

[Razorboi82]

ok you asked for it so i will break it down completely on the original post.



it was that when you were running and started casting a spell you stopped and started casting. after that brief delay you started running again.



now that was removed and you get the annoying message "You can't cast while moving" and not sure why they took it out. if you made it to where casting stops you like it did originally you could let the moving cancels spells stay in since you would stop when you begin casting and then cancel once you move afterwards.



yes, make it to where when i start casting a spell that it does the exact same thing as /facetarget does(stops running and faces the mob)



yes, there is a /facetarget button for the keyboard and i know about it, but i use a controller and the same option of that one button is not there for me.






does that help you out with your reading of the original op? i hope so because next step will be breaking it down word for word.

Sooo... He wants it to go back to the way it was... because he has a controller... From the title it states:

"Thread: Request: When you start casting, make it stop character movement and autoface the mob:
It used to be this way ..." Topic is very important here because it states the issue, which from my point of view is turn it back to the old way. then it continues to say more about his confusion on why they changed it, change it back. "I have a controller and cant be bothered by it so instead of asking for some other solution change it back. Sorry for the short explanation, I have to get to work. talk amongst yourselves on How The topic impacts any further discussion. Just a bunch of change it back is all it is. break it down all you want, I rather enjoy your in depth butchering of his OP. No matter how much you add to it all you want in the end its just a change it back thread.

[Krausus]

when you are standing still and have to cast the same spell multiple times to go off i consider that a glitch. when the spell starts casting and doesn't have the animation to it i call it a glitch. when the charge bar does not show up with a casting animation i call that a glitch.

when a spell doesn't cast because i am moving that is user error.

you are doing something horribly wrong

[Razorboi82]

you are doing something horribly wrong

I'm almost convinced this is a joke thread >.>

[Majidah]

I have no problem with the new changes even with controller i just look @ the 2 blue bars when they stop glowing i can cast... Is this really that hard to do?

Well this isn't a MUD game. I mean, that's a good way to work around a flawed system.

You sound like one of those "I WAS OUT OF THE PLUME" gaiz.

Instead of one of those "Why were you even in the plume" gaiz.

And you don't thik its wrong for a player to be hit by it when he's well far from it?
That one second in casting delay can make a win or lose difference in close call scenarios. Plus its just annoying to get that message when playing casually, honestly. I look at the screen, my character stopped moving. I shouldn't be getting that message. Simple as that.

[darkstarpoet1]

Sooo... He wants it to go back to the way it was... because he has a controller... From the title it states:

"Thread: Request: When you start casting, make it stop character movement and autoface the mob:
It used to be this way ..." Topic is very important here because it states the issue, which from my point of view is turn it back to the old way. then it continues to say more about his confusion on why they changed it, change it back. "I have a controller and cant be bothered by it so instead of asking for some other solution change it back. Sorry for the short explanation, I have to get to work. talk amongst yourselves on How The topic impacts any further discussion. Just a bunch of change it back is all it is. break it down all you want, I rather enjoy your in depth butchering of his OP. No matter how much you add to it all you want in the end its just a change it back thread.

i did to the op the exact opposite of what you did with this post. you butchered your post to where it's a jumble of incoherent thoughts. i hope they don't allow drinking on the job.

anyways i'm done with you because you cannot figure out the old way being mentioned is when you started casting you stopped and then started casting and then you could then run after. they are not asking to be able to run and still cast while moving. they even stated as much.

[Krausus]

Well this isn't a MUD game. I mean, that's a good way to work around a flawed system.



And you don't thik its wrong for a player to be hit by it when he's well far from it?
That one second in casting delay can make a win or lose difference in close call scenarios. Plus its just annoying to get that message when playing casually, honestly. I look at the screen, my character stopped moving. I shouldn't be getting that message. Simple as that.

I would say if a 1 second delay is determining your success rate then you just need some more practice or your group as a whole. No one disagrees that we shouldn't have to work around a delay, but it is there and I agree with the reasons yoshi gave for not being able to implement your idea. We will just have to adjust until 2.0.

[Scarface]

and you don't thik its wrong for a player to be hit by it when he's well far from it?
That one second in casting delay can make a win or lose difference in close call scenarios. Plus its just annoying to get that message when playing casually, honestly. I look at the screen, my character stopped moving. I shouldn't be getting that message. Simple as that.

I think its wrong to be standing in a spot where plume pops. Simple as that.

Waste of time thread.

[Firon]

Well this isn't a MUD game. I mean, that's a good way to work around a flawed system.



And you don't thik its wrong for a player to be hit by it when he's well far from it?
That one second in casting delay can make a win or lose difference in close call scenarios. Plus its just annoying to get that message when playing casually, honestly. I look at the screen, my character stopped moving. I shouldn't be getting that message. Simple as that.

That does not matter they way its implemented does not slow you down tho. You can spam the spell and let go of the run button it will go off when you stop its not like when you start casting the spell when you think it stops and it get interrupted @ 99%. The spell wont go off until you stop moving so it does not slow you down.


Edit about the Plumes: Plumes are a trap if you stand in them too long even if you manage to get out you still take dmg. Being in plumes for more than 1 sec means your gonna take dmg and it's your fualt a lot of ppl seem to think you can stand in them for a while then run away.

[Majidah]

I would say if a 1 second delay is determining your success rate then you just need some more practice or your group as a whole. No one disagrees that we shouldn't have to work around a delay, but it is there and I agree with the reasons yoshi gave for not being able to implement your idea. We will just have to adjust until 2.0.

It isn't determining my success rate, but are you saying that it couldn't in some scenarios?
We'll have to agree to disagree, since I don't think the reasons Yoshi gave are solid. For the sake of spells that aren't even implemented? And why would that have impact in these spells anyway?

[Majidah]

That does not matter they way its implemented does not slow you down tho. You can spam the spell and let go of the run button it will go off when you stop its not like when you start casting the spell when you think it stops and it get interrupted @ 99%. The spell wont go off until you stop moving so it does not slow you down.

Well see, but to me a good battle system doesn't involve spamming and mashing the same spell hoping it'll go through. With XI you'd just look at your timers and know it'd go off in the right moment. It was hitting it once. It was clockwork.

I thought we were through with this after they added auto-attack.