Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Macro Challenge: Can one use the "Reusing Rolls" trick and use a Sheet Style other than default?

This is an extension of  this thread , but I thought maybe it would be better to start a new one. Various people graciously assisted and the macros that we were trying to create in the original thread now work exactly as intended. That's awesome. Here is the follow up question: Is the trick being used " Reusing Rolls "  limited to the Default Template, or is there a way to have it so that it uses the colors/sheet style that come from a specific character sheet? In other words, if the macro produces Result A, is there a way we can use it to use the Style of Result B (which is generated from just clicking on the character sheet built-in roll)? I'm not sure if the Reusing Rolls trick is limited to the default template.  Result A: Result B (Character Sheet uses the "Fabric" Sheet Style): Note that the Macro for "Axe Swing" is as follows: &{template:default} [[ [[1d6]] + [[1d6]] + [[1d6]] ]] {{name=Axe Swing}} {{Attack=$[[0]] + $[[1]] + $[[2]]=$[[3]]}} {?{Hit Location|Torso|Skull|Face|Eyes|Neck|Left Arm|Left Leg|Left Hand|Left Foot|Right Arm|Right Leg|Right Hand|Right Foot|Vitals|Groin} {?{Hit Location Penalty|Torso, 0|Skull, -7|Face, -5|Eyes, -9|Neck, -5|Arm, -2|Leg, -2|Hand, -4|Foot, -4|Vitals, -3|Groin, -3}}} {{Location=?{Hit Location}, ?{Hit Location Penalty}}} {{Deceptive=?{Deceptive Attack Level|0}}} {{Other=?{Other Mods|0}}} {{Base Skill=?{Base Skill|14}}} {{Net Skill=[[?{Base Skill}+(?{Hit Location Penalty})+(?{Other Mods})+(?{Deceptive Attack Level})*2]]}} and the Macro for "Dwarven Axe (swing)" that comes up from the GURPS Sheet is: @{Ulf Sigurdson|roll}&{template:skillRoll} {{sheetStyle=@{Ulf Sigurdson|sheetstyle}}} {{type=Melee Attack}} {{activeDefense=[[0]]}} {{isSkillRoll=[[1]]}} {{showHitLabel=[[1]]}} {{characterName=@{Ulf Sigurdson|character_name}}} {{skillName=Dwarven Axe (swing)}} {{rollResult=[[3d6]]}} {{effectiveSkill=[[14 + @{Ulf Sigurdson|modifier}]]}} {{reach=1}} {{notes=}} {{showNotes=[[1]]}} {{useCriticalPlusTen=[[@{Ulf Sigurdson|use_critical_plus_10}]]}}
1596987979
GiGs
Pro
Sheet Author
API Scripter
There's no reason the reusing rolls trick should be limited to the default template, in principle. But Incorporating it into other rolltemplates will require knowledge of those templates. Any specific rolltemplate may be built in such a way that it cant make use of the trick.  The second bulletpoint above will probably make most sheet templates incompatible with the reusing rolls trick.  The advantage of the default rolltemplate is you can create your own rows, whereas sheet templates usually have a fixed set of rows with expectations of what they contain and that may make using the trick impossible. It would be posible for sheet designers to build their templates with the trick in mind, and no one has because its such a new discovery.  That gurps template layout isnt looking promising. I dont see how you would use it with that.
1596989065
Kraynic
Pro
Sheet Author
I notice it has a "notes" section.  You might try making use of that.  It might accept line breaks so that you could format your info however you want.
1597040996
Oosh
Sheet Author
API Scripter
I'm unfamiliar with the GURPS ruleset, but any roll template which can change the number of dice rolled (so in dnd this could be a crit, advantage/disadvantage, bless/bane etc.) will break the numbering on $[[0]] calls. That doesn't mean you can't make it work - it just makes more complex math very difficult since you can't be sure what order the rolls will be done in. With simple math only a couple of brackets deep, shoving it all at the front of the macro is generally reliable, but not always.