Ok, so now that I'm at home and on my computer here's a brief example of nesting drop-down queries and chat command buttons. Let's get the hard one out of the way first; roll query example: ?{top level query|
Option 1, Does thing x + ?{2nd level query|
2nd level option 1,@{selected|attack-1} [[1d8 + @{selected|STR}]]|
2nd level option 2,@{selected|attack-2} [[1d10 + @{selected|STR}]]
} |
Option 2, Does thing y + ?{2nd level query2|
2nd level 2 option 1,2nd level 2 value1|
2nd level 2 option 2,2nd level 2 value2}
} You need to replace the three problem characters; bars (|), commas (,), and end curly braces (}) with their html code &124;, ,, and }. The reason you need to replace these is because the query ends at the first end curly brace it sees, separates between an option name and its value at each comma it sees, and separates between choices at each bar it sees. The exception to needing to replace these characters is attribute and ability calls * . NEVER replace these characters if they are part of an attribute or ability call because of the order of operations * that the dice roller/chat parser uses. First abilities and attributes are expanded up to 99 levels deep, then roll queries are executed to 99 levels of nesting. This means that by the time the roll query exectues, those attribute/ability calls are no longer @{keyword|attributeName} or %{keyword|abilityname}, they are whatever text is contained within the ability/attribute. The further down you nest, the more you need to escape the problem characters (generally by replacing the & in the html code with &, this is also how you get the forums to properly display html code). *Note on ability calls: note that many abilities, especially sheet generated ones, have these characters inside them so generally don't put an ability call in a roll query unless it's something basic you created *Note on order of operations: There is currently an error in the wiki. The wiki states that attribute/ability calls and roll queries are recursed through simultaneously. This is not in fact the case; attributes/abilities are recursed through up to 99 times and then roll queries are recursed through up to 99 times. Now for ability command buttons. These are really simple and will take about 1/8th as much to explain. So, normally when you call an ability, like a sheet roll button that you want to access via token button, you would simply put %{CharacterName|ability name}, %{selected|ability name}, or %{target|ability name} in a new ability on your character's attributes/abilities tab or perhaps in a global macro. To make an ability command button, you simply modify that syntax a little and merge it with a mardown link type syntax: [Button Label](~CharacterName|ability name) And that's it. I don't know which sheet you are using, but if you are using the 5e OGL sheet, you might find this thread useful for creating a spellbook macro for each character. If you are using the 5e shaped sheet, it has pregenerated spellbooks available (see that sheet's documentation for more info). If you are using the community sheet, you'll have to make your own. Hope that helps, Scott
