Thanks for the kind words, Jeremy! Happy Thanksgiving, and happy gaming!

Thanks, Vic! Happy Thanksgiving!

Thanks for the kind words! PowerCards and ScriptCards are very similar, but there are some key differences, which are described here. wiki.roll20.net/Script:ScriptCards#What_to_Know_if_you_are_Coming_from_PowerCards I use ScriptCards exclusively now, because I find they're more flexible than PowerCards. I hope that helps, and happy gaming!

@@NickOlivo Sounds like I'm going to have to start using ScriptCards exclusively as well! Thanks, Nick. Looking forward to the next video!

I believe the get /get syntax is being used as an open/close bit, yes. Happy gaming!

Hey, @Dyanosis... that /get and /set syntax is exactly like the closing of a paired HTML tag, but it's only truly required in cases where the muler statement is nestled right up against other text, as a way of letting the parser know the get or set statement is finished. If the statement has a space following it (or the end of the string), Muler will automatically know it has reached the end of the tag. For instance, reading Nick's mule ability called "quotes" on the character "Ydrah" could look like this: !get.Ydrah.quotes.battlecry {&simple} But if you were going to have to bump it against other text, you would need the /get. Like this: !get.Ydrah.quoets.battlecry/get{&simple} Without that space or the /get, Muler will look for a variable named "battlecry{&simple}"... and it obviously won't find it. Even a period following will still be considered part of the variable, since Muler variables can have periods in their name. As an example, Nick could have structured a single "partyQuotes" ability on a central sheet (partyData), and differentiated which character each quote belonged to like this: Ydrah.battlecry=... Ydrah.snark=... Ydrah.lament=... Jolo.battlecry=... Jolo.snark=... Jolo.lament=... And would just require adjusting the get statement slightly: get.partyData.partyQuotes.@{selected|token_name}.battlecry ...with or without the /get, depending on how it sat next to other text. One thing about this usage is that the variables can't have spaces, so you might have to do something else if a character's name had a space. While you *can* enclose the character name portion in quotation marks in Muler syntax: get."Ydrah the Brave".quotes.snark/get You currently can't do that for the variable itself. Most the pity. I'm sure I had a reason for doing that, but I'll have to think it through and remember why. In any case, Nick did a fantastic job (as usual) explaining the script. It's just difficult to get into all the syntax trickerations without bloating the run time. =D