@Michael... SelectManager is going to track the selected tokens from the last time you sent a message... the idea being that when you call an API, you would have tokens selected, and when that API called another script, the downstream script would have forgotten the selected tokens but SM would be able to restore them. Using any kind of @{target} construction in the same macro (or character ability) as the lead-off API means that there are no selected tokens for SelectManager to track and hand off. If this is the case, we can still work around it with new functionality in SelectManager v1.0.0, but we just have to know what we're working with. Can you post the full text of the macro, as it stands now? FYI, if you want or need to use the @{target} call elsewhere in the macro (you can't get around it), then you can virtually select a token by use of a {& select} construction, and telling the forselected to escape its downstream command line. You do this by enclosing the escape character in parentheses as the last thing attached to the forselected handle: --@forselected(\)|Spawn _name|Giant Ape _qty|1 _size|2,2 {\& select @{target|...}
^ ^
^ ^
-------------^-------------- ------------^------------
| declare escape character | | use escape character |
---------------------------- ------------------------- Make sure your @{target} is the same as what you used elsewhere in the macro so that you only have the one prompt. The above will work for you because you have only one target you want to affect with the forselected call, however... I am also seeing a fix I need to put into SM... like I said, this will work for you, but for future use (or for people looking at this later and wanting to replicate), if you have multiple virtually-selected tokens, you would want the {& select} statement to be outside of the forselected, so that it was able to establish the pool of tokens forselected should iterate over. That connection needs to be added, and I will get that into a v1.0.1 before the weekend is out.