Quote Originally Posted by 'olipcs',index.php?page=Thread&postID=139713#post1 39713

..this comes down to 1 userkeypressing resulting in 2 different client-keypresses, and this is seen as automation. So never ever do that!
I'm not sure if I understand this correctly:

1) you're saying the way I'm doing it is automation and therefor bad, however it only works when I push the button. That's not automation as far as I can find out, I'm not using waits/sleeps or by one press a whole bunch of cogs n wheels start turning and I can go watch a movie.
I'm not doing this, all I'm doing is letting my alts hit an 'assist' macro in conjunction with the key I pressed and only then when I actually hit the key (like /click ActionButton).

2) if what I'm doing is wrong, how is sending shift/ctrl/alt keypresses (in various combinations of these buttons no less) to alts any different, you are sending 1 userkeypress to one screen and different clientkeypresses (which can be any combination usually 1/2 or even 3 other keypresses)to other screens. I don't understand how modifier keys (shift/ctrl/alt) could not be considered keypresses, because these keys definitely need to be pressed (or the alt windows need to think they are pressed) in order for the ftl setup to even function.

As you say, you can even use a '/click ActionButton' in a macro, which would mean that my 1 userkeypress results in 1 keypress that then is followed by another keypress because of it (making it 2 client keypresses). Of course this is being picky and taking the comparing of 2 different ways of doing things to an extreme.

Again, I'm not sure why the way of doing would be automation when the ones suggested are similar to what I'm doing.