Quote Originally Posted by darkstarpoet1 View Post
way to jump to the ignorant conclusion that this has anything to do with running around and not casting. that is not what it's about at all. when you are in your spot and throw the first 2 items in your combo and haven't moved during the process then get the

you cannot perform the action at this time
you cannot perform the action at this time
you cannot perform the action at this time
you cannot perform the action at this time
it goes off.

that is not anything to do with movement. that is bad coding and implementation. the problem is not the movement, but the bugs and errors that came along with it that should have been fixed before it was put in. yes, they added a work around for the issue(/facetarget), but a work around for a bad game design is still a bad game design regardless.

you sit here and say there's nothing wrong and then say it will be fixed in 2.0..... kind of an ignorant and hypocritical statement because if nothing is wrong then there is nothing to fix.
Truthfully I have no idea what you are talking about. If I stand still and cast...i cast. If I move and try to cast too early, I dont cast. I cannot, for the life of me, understand the problem you are having because its never happened to me or anyone I know. Yes it is ignorant, but you can't really blame me for my ignorance..its never happened, ever. I had NO idea it was even a problem besides the select *few* in this thread. All I can say is, ask ppl who dont have the problem what they are doing differently. Your game isnt coded any different than the next guy's game, so it really must be a user-related error.

I know based on the suggestions in this thread that /facetarget is a solution. Try it. If it still doesn't work, come back and ask for help. This is not a universal problem *obviously* so it is up to you to decide where the problem is occurring. I dont know how you play, what buttons you press, when you press them; the more details you give and the less insults you dish out, the better able you are to solve your issue.

And it was released when it was to give ppl a chance to get used to it. If they waited until 2.0, you'd all be raging and QQ'ing about the sudden change. It was implemented for your benefit, so you had plenty of time to get used to the new mechanic before having to deal with it in 2.0. Its like ppl forget that 1.xx is still a "development" stage. Its where you get to play exclusive content, test upcoming changes, and give feedback. There are obvious server limitations so the 1.xx version cannot match the 2.0 version in terms of smoothness and reliability. Why would they waste resources making it perfect for 1.xx when its already flawless in 2.0. 1.xx is not the finished product, and is being scrapped anyway.

Again, I have no idea what the problem is, so I suggest asking around and figuring out what you're doing wrong. Cuz you are surely doing *something* wrong...or your game just happens to act differently than everyone else's.