I have macros for each skill check in 4e, but placing them all as token actions clutters the screen. Is it possible at this time to have a macro #check that would call the specific skill check macro depending on input (i.e. #history-check)? The way I thought may work was #?{check}-check, but due to the current order of operations (which makes full sense), first the macro tries to call, finding no macro "?{check}-check" and then the query is run, allowing input, and then printing to chat "#history-check". Though this is cool as a way to show other people what to type to call macros, this is not my desired outcome here. The reason for this is simple: if a macro expands to have a roll query, that query needs to be called, and the simplest way to do this is call all queries after expanding macros (and much of advanced macro/ability usage relies on the expand-before-activating principle). Is there any way to achieve the desired effect within the current system? ----------------------------- Assuming there isn't (I've tried a good bit), some rambling about possible ways to implement: A possible way to change this is to change the order of operations to -Queries are carried out -Abilities are run (the order of operations are run locally on the content of the ability) and output cached -Macros are run (the order of operations are run locally on the content of the macro) and the output cached -Variables are substituted -Inline rolls run -Remaining roll is executed (and outputs put) The only possible problem I see with this solution is inability to do something like #roll + #modifier, but I haven't tested or done anything with this system. I fully understand the order of operations as it is currently, and it allows for some really cool things. Looking again at the above system there may be more flaws than the main draw (query-able macros) due to localized abilities and macros and the current system's focus on non-localized benefits (just expanding, not yet running). A brute-force way to allow this to happen would be just to add a run for queries onto before expanding of abilities/macros. Another way would be to add a specific syntax for queried macros (possibly something like ?# or ?@ to signify a query within the macro/ability. My example/problem above would then be done by ?#?{skill}-check which would parse the ?# as meaning to check the macro name for queries, resulting in the macro #<input>-check being run).
