timmaugh said: I sometimes find that multiple-tables trick to be a bit cluttering to my game. Here is a solution that uses metascripts: ! &{template:default} {\&global ([theRoll] {&if ?{%Roll|20%|50%} = '20%'} [[1d100>20f<20]]{&elseif ?{%Roll} = '50%'} [[1d100>50f<50]]{&end} )} {{name=Miss Chance}} {{Chance= ?{%Roll}}} {{Roll=theRoll}} {{Result={\&if theRoll.value = 1}Success!{\&else}Failure!{\&end}}}{&simple} And the output: A couple of notes, though... your roll can produce 3 different values: -1, 0, or 1. If you just need it to roll over a certain number to know if it is a success, you can drop the "failure" portion of the roll... so the 20% roll would become: [[1d100>20]] Also, structuring your query options to include the % symbol means that you can't use them in a roll equation. If you remove it (and include it in the template where you need to report the Chance percentage), your command line gets a whole lot simpler. Because inline rolls are processed after roll queries, you'd have a single roll to worry about. Provided you'd already supplied the answer for the ?{%Roll} query in your command line prior to this point (see my example, below), your roll would be either: [[1d100>?{%Roll}f<?{%Roll}]] or [[1d100>?{%Roll}]] ...depending on your answer to whether you need the "failure" number to provide a potential -1 value to the roll. That would let your new command line become: ! &{template:default} {{name=Miss Chance}} {{Chance= ?{%Roll|20|50}%}} {{Roll=[[1d100>?{%Roll}]]}} {{Result={&if $[[0]] = 1}Success!{\&else}Failure!{\&end}}}{&simple} ...and it would produce the same sort of output as pictured, above. Required Scripts ZeroFrame, APILogic This is helpful but testing it, it seems to say 'Success!' regardless instead of 'Failure!'
