EDIT - Sniped by Will (who's made some really cool stuff, btw), but here's some additional details: It is more like a scripting language than Powercards, with support for creating procedures (that you can optionally pass arguments to), loops, arrays, case statements, creating buttons programmatically, programmatically building commands (based on conditions) for another script that you can trigger, etc. You can have string- or roll-typed variables, and there are a ton of built-in functions to do things like calculate distances between tokens, string manipulation (split, trim, replace, substring, etc.), and writing to the State object to temporarily store variables for use in a subsequent macro. You can pause the macro in the middle of operation to ask for more input, access repeating fields, access the turn order, do things for all tokens on a page, just all kinds of stuff. If you have a bunch of powercard macros that work, no need to touch them! But, if you run into a roadblock functionality-wise, there is a decent chance that scriptcards can do it. Another big plus is that it is actively being developed and Kurt is very responsive, adding capabilities all the time. Anyway, if you have time and if any of the above interests you or gets you thinking, check it out! Here is a fledgling thread where folks are starting to share some of the completed scriptcards they've come up with, which could jump-start your development process. There are also some simple examples at the bottom of the wiki. And of course if you have questions, the main thread is very active with a bunch of folks ready to jump in and help :)