I heard some insider news on a ban wave...

#0 - Sept. 3, 2010, 11:26 p.m.
Blizzard Post
<yoink>

Thanks,
Fanged
#1 - Sept. 3, 2010, 11:36 p.m.
Blizzard Post
From what I can see, Fanged, it doesn't appear to be violating any of our policies. Your program isn't changing what the GCD truly is - that simply isn't possible. However, this is something that would be much better discussed in our UI & Macro forum.
#3 - Sept. 3, 2010, 11:48 p.m.
Blizzard Post
First, I did want to make you aware that any rumors you have on actions we may or may not take is questionable at best. Even if such things were announced, they would be kept very close to the breast.

As I mentioned before, the best clarification on this kind of situation would be provided in our UI & Macro forum. I generally try to keep the idea of, "If you have to ask, it's best to avoid it altogether" mentality, but I'm afraid I am unable to provide further information at this point.
#5 - Sept. 4, 2010, 12:31 a.m.
Blizzard Post
The truth of the matter, Fanged, is if you and others were using an exploitative addon, it wouldn't matter if you were using it now or in the recent past. We use the information generated from the game (i.e. our logs) to track policy violations. If action were to be taken in this rumored "ban wave" it would be based on data collected over weeks and months.

Given that you are unable to actually affect the cool-down period of an ability, which is all controlled server side, and the addon you describe seems to simply calculate the latency you are experiencing and use that information to help activate an ability as soon as it comes off cool-down, it doesn't appear that there really is an issue with the addon itself.

As previously stated though, I am not an expert on addons, macros and the like. I have given you my opinion based on what information I have. This would be better discussed with others who have a better understanding of addons.