You've hit probably the most common problem people encounter when they start using queries. First, a query will assuming any | is a row end, any comma is a divdor within a row, and any } (not part of an attribute/ability) is the macros end. Second, the Order of Operations: when you have something like this ?{Choose a Roll|ST, %{Myrius|ATT-ST}|DX,%{Myrius|ATT-DX}} It's natural to assume that roll20 will ask for your choice, then run that abillity. But thats not what happens. Roll20 first expands all abilities, and calls any attribute values, outs them into their place in the query, and then runs the query. So lets say this ability %{Myrius|ATT-ST} includes some special characters, like a comma: Myrius makes a Strength attack, and shouts menacingly So you run the macro, roll20 expands the abilities, so you end up with ?{Choose a Roll|ST, Myrius makes a Strength attack, and shouts menacingly|DX,Another ability} Now look at that middle item: notice there are two commas. In a query, commas (and |, and } ) have special meanings, and so this breaks the query. To avoid this you have three options: 1) Edit the original abilities to handle the special characters following the rules here . This will often render them unusable as individual macros 2) copy their text into a single macro, and edit them there. 3) Abandon dropdowns and use a Chat Menu instead. This works with the original macros, and is really simple to implement.
