VA macros replace a few manual keystrokes or allows having some bindings tied to voice and not buttons. There is no 'image recognition', automatic playing the game in there.
Your brain is powerful enough to understand that a macro to purchase something every 30 minutes is not an 'alternate keybinding' like saying: request docking'..
What you say is true; However, once macros are allowed, there is a very fuzzy line between 'oh thats a legal macro' and 'that one isn't' - I can think of heaps of things to automate without any screen recognition. VA automates jumping, power to idle and honk. That is apparently acceptable. There is no list anywhere to say what is acceptable and what is not acceptable, for use in macros. VA for example, monitors the logs to see when you have arrived at a destination, so it can send keys to the client to perform the honk. Is it ok for me to write something that monitors the logs and send keys to do something else?
VA uses time calculation to do particular things. And that's acceptable. So... me writing something that waits 30 minutes and then sends keystrokes to buy goods should also be acceptable.
Obviously that's stretching the limits; How-ever; the point is; Whereis the delineation between 'acceptable' and 'not acceptable'?
I'm no way saying VA should be banned from use or anything like that; What I am saying is; Like in my previous reply; FDev as the game developer, really need to specify to us; and indeed, to themselves, what is and what is not allowed. And again like previously; They need to target and watch their assets. (not saying they're not already doing that).