Character Vault
Any Concept / Any System
Compendium
Your System Come To Life
Roll20 for Android
Streamlined for your Tablet
Roll20 for iPad
Streamlined for your Tablet

Personal tools

Difference between revisions of "Hidden Rolls"

From Roll20 Wiki

Jump to: navigation, search
(Created page with "{{revdate}} Roll20 doesn't a straightforward way to create '''hidden/blind rolls''', where the player wouldn't see the result, only the GM. There are still a few methods ...")
 
m
Line 3: Line 3:
 
Roll20 doesn't a straightforward way to create '''hidden/blind rolls''', where the player wouldn't see the result, only the [[GM]]. There are still a few methods to work around it.
 
Roll20 doesn't a straightforward way to create '''hidden/blind rolls''', where the player wouldn't see the result, only the [[GM]]. There are still a few methods to work around it.
  
 +
=Alternatives=
 +
__TOC__
 
==Blind Rolls(Stylus)==
 
==Blind Rolls(Stylus)==
 
'''[https://app.roll20.net/forum/permalink/9616944/ Blind Roll (requires Stylus for GM)]''' by [[Oosh]]
 
'''[https://app.roll20.net/forum/permalink/9616944/ Blind Roll (requires Stylus for GM)]''' by [[Oosh]]

Revision as of 16:50, 5 December 2021

Roll20 doesn't a straightforward way to create hidden/blind rolls, where the player wouldn't see the result, only the GM. There are still a few methods to work around it.

Alternatives

Contents

Blind Rolls(Stylus)

Blind Roll (requires Stylus for GM) by Oosh


The nature of the macro makes the tooltip information unavailable and avoids rolling 3D dice (because... obviously). It does show the roll expression for both player and GM, though - so you can see if someone is rolling with advantage or not, or if their bonus doesn't look right, or they suddenly have 200 proficiency bonus. So I've made this macro as simple as possible. The players don't need to do anything. The GM needs to: - install Stylus - create a Style approximately 3 lines long - run the macro

The Stylus style (this one's pretty scary):

#userscript-broll {
    display: inline !important;
}

And the macro, set up for Roll20 5e:

**DM requests a blind roll:** [Roll for ?{Roll|Stealth|Strength|Dexterity|Constitution|Wisdom|Intelligence|Charisma}](`/w gm &{template:default} {{name=?{Roll} Check}} {{@{selected|character_name} rolls...=?{Advantage|Normal,1d20|Advantage,2d20k1|Disadvantage,2d20kl1} + @{selected|?{Roll}_bonus}[Bonus] + @{selected|pb}[Prof]}} {{=[Result = ](#" id="broll" style="display:none)[[[[[?{Advantage}]]d1 + @{selected|?{Roll}_bonus} + @{selected|pb}]]](#" id="broll" style="display:none)}}" style="color:darkred;background-color:white;border:solid 2px darkred;font-size:17px;border-radius: 5px;padding:2px;display:inline-block)

I've kept the Ability list short, I just did the primary Attributes for 5e then threw Stealth in for fun. Most skills are unlikely to see much blind action... I'd assume Stealth is the big one at most tables. To add skills for the 5e by Roll 20 sheet, all you need to change is the very first Roll Query - put in the skills you want, in the order of usefulness you want. This could be as short as ?{Roll|Stealth|Perception}. Be mindful of Animal Handling & Sleight of Hand: you'll need to either have the underscores visible in the drop-down, or use a comma: |Animal Handling,animal_handling|

For other systems, it might need some tweaking. You might need to get rid of the Advantage, or tweak how the Attributes are referenced: it's currently set up for [[5e attributes, which is @{selected|<skillname>_bonus}.

Some other tweaks which would be easy to apply: wrap the button inside a 5e template (npcaction or traits) to prettify it, or chuck a whisper Query in front of it ?{Whisper or public?|Public, |Alice,/w alice |Bob,/w bob |Carly,/w carly }.

Blind-roll-stylus-trick.png

If you haven't popped your head into any of the threads where we've been poking around with nesting entire templates inside API command buttons, you may have noticed a handy little Stupid Trick inside this Stupid Trick - namely, using a Roll Query to fill in an Attribute reference. This is usually a big no-no, but in this case it works. We've escaped the absolute brains out of the Attribute reference, so it's just a jumble of escaped entities and unresolved Roll Queries. But we don't need it to be a working Attribute reference until an entire round of parsing has.... errr.... passed. It's a nifty little trick which does have a big downside - you have to manually click the button after it's created. But I can see it saving a ton of macro code in the right situation.

Anyway, sing out if you need any help adapting this... I know it's hard to read. A tip if you want to make more sense of the macro: paste it into chat, then mouse-over the button it creates. Right click => Copy link location => paste into Notepad. The escaped HTML will all have been parsed into regular macro code, and the button its wrapped in will be gone. Much sanerer!

API