So, the api. When you use a token macro that includes api chat commands (for example: "!DoStuff"), and that macro is a token macro, the api call will be able to use msg.selected (assuming msg is the message object), to access the token. It would seem fairly obvious that a token macro would produce a selected token. Now, the problem is, that when that same macro includes a call to @{target|something}, the token is deselected before the api recieves the call - no matter the order in which the lines in the macro is written. This seems like a bug, as one would expect the following: !DoStuff <-- call api with currently selected token included in the /em I attack @{target|name} <-- write out the emote, using the target information I understand how this could work behind the scenes, so that it would result in the current behavior, but that does not mean I agree with it. Also, it does not seem unreasonable that a token macro, calling the api, would alway include itself (or the corresponding token) as parameters. - Toke
