I agree that DLTool is the script you're looking for, but, as the author of Fetch, I should clarify. Fetch uses parentheses as the outer boundaries of the text formations, so something like this: @(selected|has_bright_light_vision) It doesn't have to be a pipe character separating the property from the character identifier (the "selected")... it could instead a use a period. That's the way I use it, typically, so that it's another visual indication: @(selected.has_bright_light_vision) Now, how do you see the value? Metascripts are specifically aimed at changing the message object -- altering the command line or adding data that scripts can later use. The point is that your ability to see the result of a Fetch construction (for instance, retrieving the "has_bright_light_vision" setting of a token) amounts to changing the command line. This: @(selected.has_bright_light_vision) ...becomes: true (or false) Now, while a mod script can take action on a message that is simply intended for the chat output (that is, it doesn't begin with an exclamation point so it just gets output to the chat), we can't interrupt the output that hits the chat panel. That is, we can't use a script to change what is in the message *before* the user sees the original message. We could, at best, output a second message after the first that would contain our changes. That's not very helpful. So, in order to use metascripts, the requirement is that you begin your command as if it were intended for a script -- start it with an exclamation point -- even if you don't intend to invoke a script like TokenMod, Spawn, ScriptCards, etc. Even if you just want to output text to the chat, but you want that text to include information retrieved/constructed by the metascripts, start it with an exclamation point. That keeps something from hitting the chat initially and gives the metascripts time to do their thing. Now we have a message that we're able to change, but it won't hit the chat. So how do you actually see it? That's where ZeroFrame (the organizing metascript) comes in. Specifically, using the {&simple} tag. That tag tells the metascripts that, whenever their work is done, they should output the now-altered message to chat. All of that together means that you could do something like: !The value is @(selected.has_bright_light_vision){&simple} ...or... !&{template:default}{{name=Proof of Concept}}{{Bright Vision=@(selected.has_bright_light_vision)}}{&simple} ...if you wanted the look of a template.
