/me not working when marco is called via roll query marco

I'm having trouble using a roll query which calls macros. Here is a macro which I'm using  Glaive-GWM /me slashes furiously with thier glaive with an overwhelming force /roll 1d20 + @{Lougrozu Sted|strength_mod} + @{Lougrozu Sted|pb} -5 and it works normaly like it should. This is the roll query macro I'm using  ?{what type| Stanard , #Glaive-stanard | Standard GWM, #Glaive-GWM | Advantage, #Glave-Ad | Advantage GWM, #Glaive-Ad_GWM | Disadvantage, #Glaive_Dis | Disadvantage GWM, #Glaive-Dis-GWM    } However it prints the following  /me slashes furiously with thier glaive with an overwhelming force rolling 1d20 + 5 + 6 -5 ( 20 ) +5+6-5 = 26 How do I fix this issue ?  

try moving the /me command out of your individual macros and place it before the query /me ?{what type| Stanard , #Glaive-stanard | Standard GWM, #Glaive-GWM | Advantage, #Glave-Ad | Advantage GWM, #Glaive-Ad_GWM | Disadvantage, #Glaive_Dis | Disadvantage GWM, #Glaive-Dis-GWM } Also, you might want to use an inline roll to tighten up the output...? #Glaive-GWM slashes furiously with their glaive with an overwhelming force [[ 1d20 + [[ @{Lougrozu Sted|strength_mod} ]][str] + [[ @{Lougrozu Sted|pb} ]][pb] - 5 ]]

Unable to test at present but it could be because your query result has a space before the macro so your /me is actually resolving to  /me Try removing the spaces before your #

Couldn't resist testing and taking the space out worked a treat for me, bear in mind that if any of your macros have troublesome characters in them (pipes, commas and end curly braces (that aren't part of an attribute call!) you'll need to make a decision about whether or not to give them the html treatment, sanitise them or have them only work via the query drop down... more on that later if needed ;) I also found that you need to make sure there is a space between your final macro call and the query end } otherwise that last macro will only output #whatever rather than the macro... strange but true. Yours is likely fine since it is on a new line but just worth noting for reference :)

Thanks for the replys. I removed the spaces as suggested by Ziechael and it works perfectly now. Thanks for the help