Quote Originally Posted by Ughmahedhurtz View Post
I think you're missing the point. Which is, we'd rather not have the tool itself hard-coded to use in-game mechanics that may or may not exist in a future version of WoW (or any other game for that matter). Having user-created "helper" scripts that CAN account for useful in-game behavior is a different matter.

And I think we're all well aware of where the line is regarding ToS violations.
Yeah, I got that point. I was just trying to say that what he was saying was somewhat implying that we should ensure that the program is removed enough from WoW to be able to use the program to do things that Blizzard has intentionally removed, which I don't like hearing.

I don't think there's any question that the tool shouldn't be hardcoded to use in-game mechanics. I haven't seen anyone say anything to the contrary, and I can see a lot of negative things coming from that. As mentioned several times previously, we have Jamba for managing in-game mechanics (as so far as Blizzard will allow).