False positives on hack/cheat detection

[Googi]

I don't know whether this is a true "v4 bug" or whether it's some kind of RC or server bug, but it seems that Graal (or at the very least, 2K2) is now assuming that if you are running anything programmed in AutoIT, you must be running an automation macro on Graal. Except that doing so amounts to banning an entire programming language. I got disconnected from 2K2 (and presumably logged) for using AutoIT Window Info while running Graal at the same time. I wasn't even using AutoIT Window Info for Graal-related purposes, and AutoIT Window Info is not an automation macro nor is there any possible way I can think of that it could be directly used to automate any Graal tasks or to cheat in any other way on Graal (although, admittedly, I suppose it could be used to collect window information that might have some kind of application in the creation of automation macros for Graal).

Surely there's got to be a better way to go about detecting people using AutoIT macros on Graal. For example, chances are that they're going to have Graal as their active window for a continuous and fairly extensive period of time while the AutoIT program is running. Wouldn't it make more sense to only take action after, say, 10 minutes has passed with the program running and with Graal as the active window. (Obviously, it would be easy for hardcore macroers to find a way around this, but it would still be a good general direction to go in).