EDIT: Joshua with the ScriptCard ninja from the top rope! That's the sort of ScriptCard solution I mention, below. But, if you want to see the metascript version of using conditionals, read on... Roll20 offers no "built in" conditional syntax. Without a Pro sub, you're limited to workarounds like having 1-item rollable tables for IF result and for the ELSE result. With only 1 item in the rollable table, you know you're going to get it from the table once you arrive at which table to pull from. As you can imagine, that method doesn't scale well. Happily, with a Pro sub, there are other options. If a script (like TokenMod) doesn't allow in-line conditionals, there are still at least 2 options. I'll show the Metascript Toolbox approach, but I'm sure someone more knowledgeable in ScriptCards (the other option) can show you that method. I know that ScriptCards is its own thing, and can either modify the token, directly, or issue the TokenMod command to do it. On the other hand, the Metascript Toolbox is a way to give functionality to other scripts (like giving conditional evaluation to TokenMod) so it will work right in the TokenMod line. One thing about your starting line, however... I think you lost a line break somewhere along the way. I think the TokenMod command should be on a different line from the report that players see. That's how I'm going to approach it, anyway. That means this is the command I'm starting with: !token-mod --set statusmarkers|+Condition_Sleep_02::6592706 @{selected|token_name} fell asleep. So, since there are two lines that will *both* need to be conditioned, I'll put them in a batch and use the same conditional check for them both: !{{
{&if ?{Are you sure you want to fall asleep?|No|Yes} = Yes}
!token-mod --set statusmarkers|+Condition_Sleep_02::6592706 @{selected|token_name} fell asleep.
{&end}
}} About the Batch These conditionals will work in a single line, and you can use the same query response across different commands even outside of a batch... ...if you feel the "but" coming, you'd be right. First, just to make sure it's clear what I'm saying, you can enclose conditional logic in the TokenMod line: !{&if ?{Are you sure you want to fall asleep?|No|Yes} = Yes}token-mod --set statusmarkers|+Condition_Sleep_02::6592706{&end} That will remove all of the TokenMod verbiage from that line if the conditional doesn't check out, leaving the TokenMod code nothing to detect in the message when it gets a chance at it. Then, you could similarly do, in the reporting line: !{&if ?{Are you sure you want to fall asleep?} = Yes}@{selected|token_name} fell asleep. {&simple}{&end} Again, you're using the same query response (the second -- and subsequent -- time(s) you reference a query you don't have to include the possible responses), and the conditional is all contained to that one line. If the condition check returns "false", nothing will be left of the command, and no message will hit the chat. So what about that "but"? First, notice that we had to duplicate all of the IF conditional language. The only part that was shortened was the query (leaving off the responses), but there's still a lot of extraneous stuff. Also, notice how the second line had to start with a bang (!) and end with a {&simple} -- the bang allows the metascripts to get to work, and the {&simple} tells them to output the resulting text when they finish. That's even *more* verbiage. But the bigger problem is the dropped line bug that's still lurking about. Sending separate commands through the chat at the same time (multiple, separate commands) makes it possible that one or more would be dropped along the way. Typically you don't drop the first command, so in your case you might get the TokenMod command to run, putting the marker on the token, but then you wouldn't get the second command, reporting that the token has fallen asleep. Here's a simple example. I ran this command through my game to confirm that the same query could be used across lines. There are two lines, and each should output something to chat, based on what I choose from the query: ! First line {&if ?{Yes or No|Yes|No} = Yes}yes{&else}no{&end} {&simple} !Second line {&if ?{Yes or No} = Yes}Yes{&else}No{&end}{&simple} I ran that twice in my game. The very first time I ran it, though, I had a dropped line. Running it twice should have output 4 lines (a "first line..." then a "second line...", then repeated). Instead, I got: All of that to say that THAT is why I went with the batch. It simplifies the amount of verbiage you need and makes sure both command lines are sent and handled.
