Sounds like we should pass on this one
I think that, given the reaction, we should probably not implement this feature at this point.
To summarize:
Blizzard will not comment on a given application. They take the view that functionality can change (both in the app and in their software) so this prevents them from commenting.
Their stance is that as long as one key causes no more than one action, it is OK. Automation seems to be defined as when an application takes an action with no user input.
According to the above, what we propose would be "legal" but Blizzard also say that it is up to the individual to decide on whether the application they use is acceptable. This is our issue.
So far we have been extra careful to ensure that our application cannot be used to break TOS. GCP was build from the start to be a legal multi-boxing program. We could have bolted our management functions on to existing platforms, but that would have removed our ability to ensure that this remains true. In that sense we have spent time and money on ensuring this compliance.
Everything that we do in GCP can be achieved in other products - GCP just makes it easy.
Based on this thread, it would seem that adding this functionality would enter a grey area, and we should probably avoid that. We feel that preserving our exclusive "can't break the TOS" feature is probably more important, even if we lose out on some potentially cool functionality.
You people have helped clarify this for me, and I'd like to thank all the people who have so far responded to this.
Once again, thanks for the feedback