You are almost certainly running into the nested query problem described here: <a href="https://wiki.roll20.net/Macros#Advanced_Usage_for_Roll_Queries" rel="nofollow">https://wiki.roll20.net/Macros#Advanced_Usage_for_Roll_Queries</a> The firstt hing to understand: when you have a macro calling another macro, they dont happen in sequence. When you run a macro, the first thing roll20 does is scan for other macro calls, get their text, and insert them in place in the calling macro. So say you had this simple macro: /roll 1d20 + ?{Attack Type|Physical,#Physical|Magic,#Magic} And in the Phsycial and Magical macros you had these two: ?{Which Physical Stat?|STR, @{STR}|DEX, @{DEX}} ?{Which Magical Stat?|INT, @{INT}|WIS, @{WIS}} Now, wen you run that first macro, you might expect that roll20 sees the attack querie, pops up a choice for you, and then when you pick, say Physical, it runs the Physical query. That's not what happens. What actually happens, is you run the macro, roll20 immediately scans it, finds those two macro collas, grabs their text and fills in the main macro, and then tries to run that. So it creates this: /roll 1d20 + ?{Attack Type|
Physical,?{Which Physical Stat?|STR, @{STR}|DEX, @{DEX}}|
Magic,?{Which Magical Stat?|INT, @{INT}|WIS, @{WIS}}} And then when it tries to run that, it immediately hits a problem: on the physical line, after Which Physical Stat? , it encounters a | symbol, which looks like another query separator (because it is). But roll20 has no knowledge of nested macros, so it thinks that separator is for the first query, and so it breaks. The way to get around this is described on the linked page: you have to replace certain characters (commas, pipes, and close curly brackets) with their html entity. But never replace the symbols in attribute calls. here's the second problem: if you replace the symbles in the nexted macros, they will no longer work on their own. They will only work when called from the master macro. So you may as well go ahead and combine them into the master macro directly. If we do that with the macro above, we end up with this very ugly construction: /roll 1d20 + ?{Attack Type|
Physical,?{Which Physical Stat? &#124; STR &#44; @{STR} &#124; DEX &#44; @{DEX} &#125; |
Magic,?{Which Magical Stat? &#124; INT &#44; @{INT} &#124; WIS &#44; @{WIS} &#125; } This is really ugly and with complex macros gets really hard to deal with, so sensible people usually give up on nested macros completely, and turn to Chat Menus ( see here ). With chat menus, you keep your separate macros, and just print buttons out with the attack that they can be clicked to roll on. It's much, much simpler.