Asherons Call: An Important Note About SpeedHack Detection !

srand just posted this on our Game Issues board about SpeedHack Detection. Her post can be found here.

srand stated:

However, you have said several things here that I feel I should clarify.

To the best of my knowledge, Ken Karl has never stated that I should be publically addressing any issues. I'd be pretty surprised if he has, since this isn't part of my job description. Now, I do think that he trusts me when I decide to answer questions and provide information for the players -- at least, he hasn't asked me to stop yet -- but I am in no way the official go-between from CoD to Ken Karl, nor an official mouthpiece for either Turbine or Microsoft.

On this particular issue, I have been very properly not commenting because this is Microsoft's issue to comment on. (I will say, however, that I have every confidence that they will take swift action regarding this situation, if indeed they haven't already.)

As for the other issues you mentioned in your first post, I have addressed most of them before but I can sum up for you again if you like.

Speed hack detection works just fine. However, due to concerns about false positives, automatic enforcement is currently disabled. When any speed hack type program is detected, a permanent record is made of that fact on your account, and the detection is logged for later action by the admins.

Most so-called fast-casting is actually just animation breaking. Yes, it still has an effect on PK, and yes, we'd like to fix it, but animation breaking is an entirely different phenomenon than true fast-casting. If true fast-casting still exists, no one has yet been able to give us a reproducible method for it. Speaking of animation breaking: Much of the animation breaking situation cannot be fixed in the AC engine, but we are investigating ways to ameliorate the effects of this on PK.

We are aware of the problems that jump-spin is causing for some players, and we are investigating the situation. Again, this isn't an easy thing to fix properly, but we are doing what we can.

An interesting piece of info. It seems as though it's still there silently logging.