Useful Macros for Adventures

This is a place to collect and share various Macros that would be useful for our particular, modified 2e game.

Thieving Macros (Dynamic) I put together some dynamic macros (DM approved) to help those with thieving abilities. I even made ones for attacks. They're dynamic in that they pull from the character sheet tables, so changes to your attributes and abilities only need to happen on the character sheet, not the macro. Because let's face it, why change data in two places when you don't have to? Lockpick Macro /me slides a lockpick into the mechanism /r d100 Success on [[@{Mora(Jennifer)|olb}@{Mora(Jennifer)|olr}@{Mora(Jennifer)|old}@{Mora(Jennifer)|ola}@{Mora(Jennifer)|oll}]]% or less Traps Macro /me attempts to ?{Find or Remove?|find} a trap /r d100 Success on [[@{Mora(Jennifer)|rtb}@{Mora(Jennifer)|rtr}@{Mora(Jennifer)|rtd}@{Mora(Jennifer)|rta}@{Mora(Jennifer)|rtl}]]% or less Atack Macros (Dynamic) Attack Macro (with Dagger) /me swiftly swipes at ?{Enemy|foe} with her dagger To Hit, I'm... /roll d20@{Mora(Jennifer)|thaco}+?{Modifier|0} If it connects, deal [[1d3]] damage. Attack Macro (with Crossbow) /me lets loose a bolt at ?{Enemy|foe} with her crossbow /roll d20@{Mora(Jennifer)|thaco}@{Mora(Jennifer)|dexmissile}+?{Modifier|0} If it hits, deal [[1d4]] damage Simply replace Mora(Jennifer) with the exact contents in your Character Sheet's Name field, and change the die to fit your weapons. I'm happy to create ones for other abilities if anyone is wanting. A note about the attack macros, since we use a modified THAC0 system, you need to add a place to store that variable. It's simple. Just go to your Character Sheet > Attributes & Abilities > click '+' next to Attributes at the top. In the name field, put thaco (all lower case) and the value (e.g. +2 ). Also, if you have a Strength Modifier (unlike Mora), then add this bit of code @{Mora(Jennifer)|strbonus} right before or after @{Mora(Jennifer)|thaco} —it's similar to the dexmissile variable you see in the Crossbow macro. Also, If you do not have these dex or str bonuses, simply remove those lines. Not sure that they work properly otherwise!

Great stuff Jennifer, thanks!

Yesterday I asked if it was possible to save a variable (that the user entered into a prompt) and re-use it twice through the same macro. Yes, that is possible It turns out, if you use the exact same wording for the variable name, the macro will only ask you for the value once and will use it in both locations. Example /me attacks /roll d20 ?{Additional attack roll modifier} vs AC (Additional modifier gives ?{Additional attack roll modifier} ) This macro will prompt you for a value "Additional attack roll modifier". Lets say you enter +2. This results in: Sandoval attacks Rolling d20 +2 vs AC (13)+2 = 15 (Additional modifier gives +2 ) It used the value "+2" that was entered earlier again on the last line. Exactly what I needed!

Mora A little something that you might like for your thief macros. /me slides a lockpick into the mechanism /r d100<[[@{Mora(Jennifer)|olb}@{Mora(Jennifer)|olr}@{Mora(Jennifer)|old}@{Mora(Jennifer)|ola}@{Mora(Jennifer)|oll}]] You might like what you have better, but this will output the "number of successes" (in case you roll multiple d100's it makes more sense) based on the formula. In this case, whether the d100 ended up lower than your lockpick chance of success. I'm still looking into conditional parts of the macro based on the amount of successes. That way you could just say "SUCCEEDED" or "FAILED" based on the results. Pretty sure this is technically possible, just need to work it out.

Other than the "Number of Successesssessssesssss", I think the work on your Macros is looking good! I have a preference against "Number of successes" showing.  I remember telling Jennifer about that on her first day in the campaign. As you discovered, Hans, it currently outputs "1 Successes" (which is bad English, improper pluralization), or "0 Successes" (also an awkward phrase).  It does not say Succeed / Fail. As far as I know that grammar is not currently customizable. It's hard-coded in the dice engine. It's designed for pool-of-dice games (maybe like d6 Star Wars?) where you roll something like 30d6 and you want to know how many were 1's and 2's, so it looks ok for those games reporting things like "5 Successes" and rarely says 1 or 0. More importantly for me as DM though --- the macro output must not declare the DM's job. Rolls like Perception are not a firm target, there can be hidden modifiers to be interpreted by the DM. Player give DM the rolls and roll results (and feel free to let your Macro tell me the "target" number such as your Perception score), and I will say if it's a success or fail.  Macro shouldn't say the result, only report the relevant roll number and stat number.  I do lots of funny things like Rolling 1, or Rolling exactly on your Perception score is the best, rolling 20 or 1 above your perception score is the worst .  Sometimes I change it up to make the formulas non-obvious or to evade patterns, or to adjust for hidden difficulties in the scenario. Fun Little Example Dialog: PLAYER:  I will do a running jump and leap across the Grand Canyon!  DM: You know that is a 500 yard jump and would be very dangerous? PLAYER: Yes I have the jumping proficiency so I do it! DM: Ok, roll a d20 against your DEX. Try to roll low. PLAYER: I rolled a 5 and my DEX is 18, my macro says I succeed with 1 Successessss and jump across the Grand Canyon! DM: No. You still failed at jumping 500 yards. You succeed in grabbing a tree branch rather than plummeting to your doom.

So your point is not to rely on macros to jump across the Grand Canyon, right? ;)

But seriously, I don't like the 's succeeded' either. I'll adapt Mora's thief skills format for my skill checks.