API command buttons w/ selected and target macros

Whenever I try to create a chat command button in the chat through the API, it seems to always strip out the macros @{selected|attr} and @{target|macro} For example, if I do sendChat('who', '[Do the Thing](!doTheThing @{selected|token_id} @{target|token_id})'); it doesn't process selected or target at all. This only happens if the command is sent via sendChat() or through API command buttons rendered with sendChat(). If I enter in !doTheThing @{selected|token_id} @{target|token_id} manually through the chat, it works fine. Inside the API console, I also get the following error: "ERROR: Unable to find character selected in chat command." "ERROR: Unable to find character target in chat command."

Not sure if this helps, but you could escape the @ signs such that the Attributes are only called when the button is clicked, and not when the button is sent to the chat.

I think it is due to the fact that api command buttons resolve their attribute calls when they are outputted, not when they are clicked (at least this is how it works for roll queries) EDIT: What happens if you do a formatted button (a la using the makeButton function from Aaron's scripts)? I know I've used those with roll queries before, might work for these as well. makeButton = function(command, label, backgroundColor, color){         return templates.button({             command: command,             label: label,             templates: templates,             defaults: defaults,             css: {                 color: color,                 'background-color': backgroundColor             }         });     },

Silvyre said: Not sure if this helps, but you could escape the @ signs such that the Attributes are only called when the button is clicked, and not when the button is sent to the chat. Escaping it by \@, \\@, or encodeURIComponent('@') hasn't worked. Scott C. said: I think it is due to the fact that api command buttons resolve their attribute calls when they are outputted, not when they are clicked (at least this is how it works for roll queries) EDIT: What happens if you do a formatted button (a la using the makeButton function from Aaron's scripts)? I know I've used those with roll queries before, might work for these as well. makeButton = function(command, label, backgroundColor, color){         return templates.button({             command: command,             label: label,             templates: templates,             defaults: defaults,             css: {                 color: color,                 'background-color': backgroundColor             }         });     }, Could you provide a link to wherever his library is in the Roll20 API repo? Roll queries work fine, but I might try this for selected and target as well.

Don't know about his library, I just took that from one of my scripts (either  EasyExperience or  PageNavigator ) which was originally taken from one of his scripts (can't remember which one at the moment).

Stephen L. said: Silvyre said: Not sure if this helps, but you could escape the @ signs such that the Attributes are only called when the button is clicked, and not when the button is sent to the chat. Escaping it by \@, \\@, or encodeURIComponent('@') hasn't worked. Try escaping it using the HTML entities, i.e. @ or @

Silvyre said: Stephen L. said: Silvyre said: Not sure if this helps, but you could escape the @ signs such that the Attributes are only called when the button is clicked, and not when the button is sent to the chat. Escaping it by \@, \\@, or encodeURIComponent('@') hasn't worked. Try escaping it using the HTML entities, i.e. @ or @ Escaping it with & #64; did the trick! Thanks!