Macro with lots of modifiers

Is there a way to compile all of the conditions used in a macro into a single pop-up prompt box? Something like a form.

Short answer: No, the prompts are single entry only. Medium answer: You could... well you could fake it by having the query give a list of all available options and the various combinations and then the output do the rest but it would get very messy, very quickly and be a nightmare to write/maintain lol. Long answer: Often these things can be looked at from another angle, such as reusing existing prompts in fun and interesting ways in order to reduce the overall number of queries being used. I've ran high level 3.5e games where the characters attacks could result in numerous prompts every time... experience taught us to reduce or nest the prompts to avoid having to answer things that weren't necessary as well as reuse existing ones wherever we could for that 'one-hit wonder' feel... do you have an example of a currently modifier heavy macro you'd like to streamline?

Sometimes its nice to have a kind of conditionals box on a sheet if you are dealing with that many options in the sheet itself. A player can put in those options before making a roll to have those apply. 

Richard T. said: Sometimes its nice to have a kind of conditionals box on a sheet if you are dealing with that many options in the sheet itself. A player can put in those options before making a roll to have those apply.  I've given this some thought and come up with a notion of a possible solution. Let's say you have instead of a single pop-up box with a single variable that is defined at run-time you have instead a sort of hidden sub-sheet called up whenever the macro is executed. This form (really that's what a character sheet is) would contain all the variables for that macro e.g. weapon_1_attack. Now, because the form-sheet stays with the character, the variables also stay. So all that is really necessary to make this work is a function that calls up this form sheet. The sheet then holds the execution of the macro until the [submit] button is pressed. There would also need to be some sort of validation for the form (or possibly default varibles) but that should not be terribly hard.