Dachimotsu wrote:And "common macro" is a term I found in MapTool itself. When you highlight multiple tokens that share a macro, the shared macros appear at the top of the "selection" window, under a category called "Common Macros".
Oh, ok. That's for when you have the macro on both tokens and it's one that they have "in common".
You could, for example, make a GM token with your monster creation macros on it (like this one). Impersonate it and use the macro from the impersonate window. Select your new monster tokens, and then run the HP generator on them. That way you would not need to have this macro on each monster token.
Or you could just put this macro in your Campaign Macros and run it from there on your monster tokens.
Either way, if you're going to be doing it this way a lot you might want to have a more general monster creator macro that you could run from your Campaign Macro window or a GM token.
Something like:
Code: Select all
[h:status=input(
"junk|<html><b>Monster Setup</b><br><br></html>|<html>Tooltip Text Here</html>|LABEL|SPAN=TRUE",
"hitDice|0|Hit Dice",
"armorClass|0|AC"
)
]
[h:abort(status)]
[h: monsters = getSelected()]
[h, FOREACH (monster, monsters), CODE:
{
[h: setProperty("AC", armorClass, monster)]
[h: rolledHPs = eval(hitDice)]
[h: setProperty("Hit Points", rolledHPs, monster)]
[h: broadcast("<b>"+getName(monster)+"</b>", "GM")]
[h: broadcast("Hit Points: "+rolledHPs, "GM")]
[h: broadcast("AC: "+armorClass, "GM")]
}
]
This way you could add new input lines for additional data to be generated on the tokens.
Note that you *would not* use "Apply to selected" with this macro because you're "getting the selected" tokens from within the macro itself.