[Chatsetattr] Found an oversight in syntax

!modbattr does not allow for the use of --sel.  To get around this I used !setattr --sel --mod.  I dunno if !setbattr or !modattr have a similar issue.  

Are you sure? I use the --sel option with modbattr all the time, for a bunch of different macros calling ChatSetAttr, and I've never had a problem.

I've already lost the exact sequence it happened with, but I do recall that it was in a macro that also asked for targets for /fx and !token-mod so maybe that is why it was throwing the error.  I can't properly provide the context now so I guess I revoke the issue.  

DM Eddie said: I've already lost the exact sequence it happened with, but I do recall that it was in a macro that also asked for targets for /fx and !token-mod so maybe that is why it was throwing the error.  I can't properly provide the context now so I guess I revoke the issue.   Ah. I think the issue is that ChatSetAttr doesn't play well with other API scripts in a macro. I've tried many times to create macros that use both ChatSetAttr and Tokenmod, and they always fail in some (weirdly irregular) way. One will fire, the other will fail silently, and vice-versa.

You can't transfer token selection from one API to another, I think Aaron or someone explained that to be the main reason in some recent thread related to powercards + ChatSetAttr.

Actually you can , but no one seems to have added this to their scripts. Timmaugh made it as easy as possible for scripters, too. Ahhh damn. Was going to bump the thread, but it's just auto-closed.

Oosh said: Actually you can , but no one seems to have added this to their scripts. Timmaugh made it as easy as possible for scripters, too. Ahhh damn. Was going to bump the thread, but it's just auto-closed. Oh man, totally forgot about SelectManager. I hope other scripters start adding that support.