We interrupt your current server woes to talk about casting

[Rydin]

Here is my thing....

If there is a button that tells the server that I am no longer moving....
Why isn't that same message sent to the server when I stop moving the analog stick?
Why is pressing "Facetarget" a faster way to stop than to just not move or press any buttons?

If there is a LAG FREE way to tell the server I am no longer moving... then why isn't it there when I actually STOP MOVING

I swear to God you didn't just tell me to make a macro TO STOP MOVING????

If that doesn't sound like the most unintuitive game design EVER

[WillRiker]

Here is my thing....

Why isn't that same message sent to the server when I stop moving the analog stick?
Why is pressing "Facetarget" a faster way to stop than to just not move or press any buttons?

I dont normally read posts where people feel the need to caps lock for emphasis, but this man actually has a point here. I struggle with computer programming, and I bet even i could write something to do this.

personally, I dont understand why they just dont make the minimum cast time on spells match a minimum requirement computers "inertia" with half second cast time spells be castable while on the move so inertia isnt an issue.

It takes just a little bit of thinking outside the box, but a variable that toggles between two values. one value for when the toggle is moved, and another for when it isnt. when it toggles to the off position, it sends a notification to the server to let it know spells are castable now. from here, spell cast timers can make up for the remaining inertia. having a face target button is.... an added step, another button.

I thought last casting update was to get rid of extra button pushes, why are they adding more button pushes now?