D&D 5e sheet - doubling damage from crits instead of rolling more

So I'm starting in a new campaign, and our DM wants us to double the damage of the initial damage roll instead of rolling extra dice when we crit. Is there a macro to easily do this (preferably with the "auto-roll damage and crit" option), or do I have to do the math myself?

The reason some people run with this house rule is to avoid doing extra math. What is the point in doing this on a VTT?

It kind of sucks too as a 1 on the dice ensures a low damage on your critical hit.  At least with the standard way, rolling two 1's is less likely.

There's no way to do this with the normal sheets. A workaround solution might be to make the crit dice "xdx * 2". It will let you do that. Then when you crit, you just take the crit number and ignore the normal damage dice.

Spren said: There's no way to do this with the normal sheets. A workaround solution might be to make the crit dice "xdx * 2". It will let you do that. Then when you crit, you just take the crit number and ignore the normal damage dice. Don't forget to manually add the modifiers to that field, too. So for a strength based attack it would be (xdx)*2+ @{strength_mod} + <other damage mods as applicable>

Good point Dakota!

A bit late to the party, as I initially couldn't find a way to hide the square brackets in the output, but you can do this: Change the damage field so it's inside [[ ]] brackets, e.g. Damage: [[2d6]] Then change the crit field to the following: }}{{crit1=$[[0]]}} You could just put the $[[0]] in there, but it will output with brackets around the number. Edit - come to think of it, you could just overwrite the standard {{dmg1}} field instead, by putting this in the crit field (adjust the math for the weapon, obviously): 0]]}}{{dmg1=[[2*2d6[CRIT]+@{strength_mod}[STR]]]}}{{crit=}} That will remove the crit damage display and add all the damage together, if that's the preference.

Yeah, as a new user of the app, when I'm running into this home rule, I just solve it mentally instead of trying to find a macro for the app... But then, once I'm used to it, I might as well try.